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 to navigate problems in LC-Problems buffer #79

Conversation

limoiie
Copy link
Contributor

@limoiie limoiie commented Jan 17, 2021

Support to directly navigate in LC-Problems buffer by specifying a problem id (or the current one by default). These actions can also be performed 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 i or RET
show leetcode-show-problem I
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.

Address issue #66.

@limoiie limoiie closed this Jan 17, 2021
@limoiie
Copy link
Contributor Author

limoiie commented Jan 17, 2021

I just found that in the problem object there also is a field named pos which is pretty similar to id. Fetched problems in leetcode--all-problems continue on the field pos but not on the filed id, which means some problems are missing in leetcode--all-problems. This issue may break the way to navigate problems by id. So I will fix this first and then reopen the pr.

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.

1 participant