Need help with leetcode.vim?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

ianding1
130 Stars 27 Forks MIT License 117 Commits 19 Opened issues

Description

Solve LeetCode problems in Vim!

Services available

!
?

Need anything else?

Contributors list

leetcode.vim

asciicast

Solve LeetCode problems in Vim!

This Vim plugin is inspired by skygragon/leetcode-cli.

Attention: Recently LeetCode used Google reCAPTCHA to enhance security, prohibiting automatic login through LeetCode API.

The new login procedure needs you to login in your browser first so that leetcode.vim can read the LeetCode session cookie from the browser's cookie storage.

Supported browsers are: Chrome, Firefox. Safari is not supported yet.

The one-time setup:

  1. Install keyring and browser-cookie3:
    shell
    pip3 install keyring browser-cookie3 --user
    
  2. Set
    g:leetcode_browser
    to
    'chrome'
    or
    'firefox'
    .

Thanks @zhuopro (see #25) for his brilliant idea!

Installation

  1. Vim with
    +python3
    feature is required. Install the pynvim package for Neovim:
    sh
    pip3 install pynvim --user
    
  2. Install keyring and browser-cookie3:
    sh
    pip3 install keyring browser-cookie3 --user
    
  3. Install the plugin:
    vim
    Plug 'ianding1/leetcode.vim'
    

Quick Start

  • :LeetCodeList
    : browse the problems.
  • :LeetCodeTest
    : run the code with the default test case.
  • :LeetCodeSubmit
    : submit the code.
  • :LeetCodeSignIn
    : manually sign in.

Key mappings

leetcode.vim doesn't bind any key mappings by default. Put the following lines to your .vimrc to set up the key mappings.

nnoremap ll :LeetCodeList
nnoremap lt :LeetCodeTest
nnoremap ls :LeetCodeSubmit
nnoremap li :LeetCodeSignIn

Customization

g:leetcode_china

When non-zero, use LeetCode China accounts instead.

Default value is

0
.

g:leetcode_solution_filetype

The preferred programming language.

Values:

'cpp'
,
'java'
,
'python'
,
'python3'
,
'csharp'
,
'javascript'
,
'ruby'
,
'swift'
,
'golang'
,
'scala'
,
'kotlin'
,
'rust'
.

Default value is

'cpp'
.

g:leetcode_browser

Set to the browser that stores the LeetCode session cookie.

Values:

'disabled'
,
'chrome'
,
'firefox'

Default value is

'disabled'
.

g:leetcode_hide_paid_only

Hide the paid only problems on the list.

Default value is

0
.

g:leetcode_hide_topics

Hide the topics section.

Default value is

0

g:leetcode_hide_companies

Hide the companies section.

Default value is

0

g:leetcode_problemset

Set the problemset to get from leetcode.

Default value is

all

Updates

  • 2019/12/20: Fix the login issue caused by reCAPTCHA.
  • 2019/08/01: Support custom test input
  • 2019/07/28: Support showing frequencies and sorting by columns
  • 2019/07/27:
    • Support LeetCode China accounts
    • Support refreshing
  • 2019/07/23: Support topics and companies

FAQ

I use Ubuntu and get errors when signing in. How can I fix it?

Ubuntu users might see the error message below when signing in.

text
    raise InitError("Failed to unlock the collection!")
keyring.errors.InitError: Failed to unlock the collection!

It's caused by the misconfiguration of python-keyring. One way to fix it is to create a file

~/.local/share/python_keyring/keyringrc.cfg
with the following content:
[backend]
default-keyring=keyring.backends.Gnome.Keyring

Why can't I test the problem/submit the problem/list the problems?

~~Once you sign in on your browser in LeetCode website, the LeetCode session in Vim get expired immediatelly. Then you need to sign in again in Vim before doing other things.~~ (No longer having this problem)

Why can't I test and submit solutions?

According to issue #5, if the email address is not active, then you can only login and download problems, but cannot test and submit any code.

I got some errors like "ModuleNotFoundError: No module named 'keyring.util.escape'"

This solution worked for me:

shell
pip3 install --upgrade keyrings.alt

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.