Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: support several useful actions for navigating in "LC Problems" page #82

Merged

Conversation

limoiie
Copy link
Contributor

@limoiie limoiie commented Jan 20, 2021

Support to directly navigate in LC-Problems page by specifying a problem id which is the number in column '#'. These actions can be performed by single-char hotkeys or by calling related interactive functions. Additionally, each action has its own 'current' version that performs on the current problem with no need to specify one manually.

A more complete specification is shown in the table below:

action interactive function hotkey in LC-Problems
show* leetcode-show-current-problem o or RET
show leetcode-show-problem O
show-in-browser* leetcode-show-current-problem-in-browser b
show-in-browser leetcode-show-problem-in-browser B
view* leetcode-view-current-problem v or TAB
view leetcode-view-problem V
start-coding* leetcode-solve-current-problem c
start-coding leetcode-solve-problem C

Note the actions that end with '*' are the 'current' version.

Besides, the action view is similar to the action show, except that view will stay in the LC-Problems buffer after opening the description page. This could be very useful when someone just wants to glance over the problems to find an appropriate one.

Solves issue #66.

@kaiwk kaiwk merged commit 3f0129c into kaiwk:develop Jan 21, 2021
swapnilsm pushed a commit to swapnilsm/leetcode.el that referenced this pull request Nov 13, 2022
…-in-leetcode-buffer

Feature: support several useful actions for navigating in "LC Problems" page
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants