@@ -15,7 +15,7 @@ CONTENTS *working-set-contents*
15
15
INTRO *working-set-intro*
16
16
17
17
Working Set is an programming editor companion that makes searching, and using
18
- search results for jumping around , super nice.
18
+ search results for navigation , super nice.
19
19
20
20
This is the vim plugin that integrates vim with Working Set. If you're using
21
21
vim 8, then the async features will be used, and the integration is smoother.
@@ -46,15 +46,15 @@ COMMANDS *working-set-commands*
46
46
47
47
All interaction with Working Set can be driven by commands in ex mode.
48
48
49
- WS {term} - does a search in Working Set.
49
+ : WS {term} - does a search in Working Set.
50
50
51
- WSSync - jumps to currently selected location.
51
+ : WSSync - jumps to currently selected location.
52
52
53
- WSSelectNextItem - selects next match in Working Set, then syncs.
53
+ : WSSelectNextItem - selects next match in Working Set, then syncs.
54
54
55
- WSSelectPrevItem - selects previous match in Working Set, then syncs.
55
+ : WSSelectPrevItem - selects previous match in Working Set, then syncs.
56
56
57
- WSSearchCurrentWord - does a word-boundary search on the word under the
57
+ : WSSearchCurrentWord - does a word-boundary search on the word under the
58
58
cursor.
59
59
60
60
Examples:
@@ -81,6 +81,67 @@ commands.
81
81
<Leader>* This does a word match on the word under the cursor in vim (like *)
82
82
followed by :WSSearchCurrentWord.
83
83
84
+ Note: If you don't want the default mappings, you can disable them by setting
85
+ "g:WorkingSetSkipMappings" to any value before loading the plugin.
86
+
87
+ ===============================================================================
88
+ USAGE GUIDE *working-set-usage-guide*
89
+
90
+ Working Set (the standalone program) is intended to run separately, alongside
91
+ your editor. Your editor will communicate with Working Set via a file socket,
92
+ sending and receiving commands. Those commands will run searches, display
93
+ results, facilitate navigation and other operations.
94
+
95
+ Working Set works best running in a terminal window that is tall, and placed
96
+ juxtaposed to the side of your editor. If you use Tmux, this is a perfect time
97
+ to use split panes.
98
+
99
+ For example, on a laptop, I would suggest running your terminal full screen with
100
+ Vim taking most of the space on the left, and Working Set running in a pane that
101
+ takes up a smaller space on the right.
102
+
103
+ Laptop Screen
104
+ +----------------------------+----------+
105
+ | | |
106
+ | | |
107
+ | | |
108
+ | | |
109
+ | | |
110
+ | Vim | Working |
111
+ | | Set |
112
+ | | |
113
+ | | |
114
+ | | |
115
+ | | |
116
+ +----------------------------+----------+
117
+
118
+ On a larger desktop or multi-monitor setup, you could be more creative, running
119
+ Working Set in a separate window, even on a separate monitor.
120
+
121
+ With that in mind, here's the steps:
122
+
123
+ 1) Install Working Set (gem install working_set)
124
+
125
+ 2) Install working-set.vim plugin
126
+ - don't forget to install socat
127
+
128
+ 3) Change to your project's directory and run `working_set`
129
+
130
+ $ working_set [whatever options you want]
131
+
132
+ By default, Working Set will create a hidden socket file in that directory
133
+ that the vim plugin will use for communication.
134
+
135
+ 4) In another terminal, change to your project's directory and open vim.
136
+
137
+ $ vim
138
+
139
+ 5) Use "<leader>*" in normal mode, or the :WS commands to drive searches.
140
+
141
+ Working Set has an ncurses based interface with various keybindings that will
142
+ feel natural to vim users. Checkout Working Set's help to learn more about what
143
+ you can do with it.
144
+
84
145
===============================================================================
85
146
CONTRIBUTING *working-set-contributing*
86
147
@@ -100,5 +161,6 @@ Git repository: https://github.com/coderifous/working-set.vim
100
161
===============================================================================
101
162
CHANGELOG *working-set-changelog*
102
163
103
- 2016/12/25: First Public Release.
164
+ 2020/09/02: Actual first public release.
165
+ 2016/12/25: First public release.
104
166
0 commit comments