Skip to content

Commit ef59344

Browse files
committed
doc: update
1 parent 4a2818b commit ef59344

File tree

3 files changed

+26
-28
lines changed

3 files changed

+26
-28
lines changed

README.md

+26-28
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,32 @@
33

44
LeetCode brings you offer, and now Emacs brings you LeetCode!
55

6+
# Usage
7+
8+
![screencast](images/screencast.gif)
9+
10+
1. Execute `leetcode` command, and in problem list buffer:
11+
12+
| keymap | command |
13+
|--------|----------------------------------------|
14+
| n | cursor move down |
15+
| p | cursor move up |
16+
| s | filter problems by regex |
17+
| t | filter problems by tag |
18+
| d | filter problems by difficulty |
19+
| / | clear filters |
20+
| g | refresh without fetching from LeetCode |
21+
| G | refresh all data |
22+
| RET | show current problem description |
23+
24+
2. Press `<RET>`, show problem description, move cursor to "solve it", press
25+
`<RET>` again, start coding!
26+
27+
3. After finishing your code, you can edit testcase and execute `leetcode-try`
28+
or execute `leetcode-submit`.
29+
30+
![leetcode-submit](images/leetcode-submit.png)
31+
632
# Installation
733

834
- Vanilla Emacs: `package-install` it from melpa directly
@@ -41,34 +67,6 @@ You can save solution by setting `leetcode-save-solutions`:
4167
(setq leetcode-directory "~/leetcode")
4268
```
4369

44-
# Usage
45-
46-
1. Execute `leetcode` command.
47-
48-
![leetcode](images/leetcode.png)
49-
50-
In leetcode problems list buffer:
51-
52-
| keymap | command |
53-
|--------|----------------------------------------|
54-
| n | cursor move down |
55-
| p | cursor move up |
56-
| s | filter problems by regex |
57-
| t | filter problems by tag |
58-
| d | filter problems by difficulty |
59-
| / | clear filters |
60-
| g | refresh without fetching from LeetCode |
61-
| G | refresh all data |
62-
| RET | show current problem description |
63-
64-
2. Press `<RET>`, show problem description, move cursor to "solve it", press
65-
`<RET>` again, start coding!
66-
67-
3. After finishing your code, you can edit testcase and execute `leetcode-try`
68-
or execute `leetcode-submit`.
69-
70-
![leetcode-submit](images/leetcode-submit.png)
71-
7270
# Debug
7371

7472
Call `leetcode-toggle-debug`, log will output in `*leetcode-log*` buffer.

images/leetcode.png

-388 KB
Binary file not shown.

images/screencast.gif

1.02 MB
Loading

0 commit comments

Comments
 (0)