aboutsummaryrefslogtreecommitdiff
path: root/runtime/doc/usr_21.txt
diff options
context:
space:
mode:
Diffstat (limited to 'runtime/doc/usr_21.txt')
-rw-r--r--runtime/doc/usr_21.txt36
1 files changed, 18 insertions, 18 deletions
diff --git a/runtime/doc/usr_21.txt b/runtime/doc/usr_21.txt
index 8bc208dc30..bdff81ef69 100644
--- a/runtime/doc/usr_21.txt
+++ b/runtime/doc/usr_21.txt
@@ -169,7 +169,7 @@ exiting Vim, there is a slightly more complicated way. You can see a list of
files by typing the command: >
:oldfiles
-< 1: ~/.vimrc ~
+< 1: ~/.config/nvim/init.vim ~
2: ~/text/resume.txt ~
3: /tmp/draft ~
@@ -189,7 +189,7 @@ That #<123 thing is a bit complicated when you just want to edit a file.
Fortunately there is a simpler way: >
:browse oldfiles
-< 1: ~/.vimrc ~
+< 1: ~/.config/nvim/init.vim ~
2: ~/text/resume.txt ~
3: /tmp/draft ~
-- More --
@@ -276,13 +276,13 @@ example, use: >
SESSION HERE, SESSION THERE
The obvious way to use sessions is when working on different projects.
-Suppose you store your session files in the directory "~/.vim". You are
-currently working on the "secret" project and have to switch to the "boring"
-project: >
+Suppose you store your session files in the directory "~/.config/nvim". You
+are currently working on the "secret" project and have to switch to the
+"boring" project: >
:wall
- :mksession! ~/.vim/secret.vim
- :source ~/.vim/boring.vim
+ :mksession! ~/.config/nvim/secret.vim
+ :source ~/.config/nvim/boring.vim
This first uses ":wall" to write all modified files. Then the current session
is saved, using ":mksession!". This overwrites the previous session. The
@@ -292,7 +292,7 @@ point. And finally you load the new "boring" session.
If you open help windows, split and close various windows, and generally mess
up the window layout, you can go back to the last saved session: >
- :source ~/.vim/boring.vim
+ :source ~/.config/nvim/boring.vim
Thus you have complete control over whether you want to continue next time
where you are now, by saving the current setup in a session, or keep the
@@ -330,11 +330,11 @@ More about this in the next chapter.
You can resize the windows a bit to your liking. Then save the session with:
>
- :mksession ~/.vim/mine.vim
+ :mksession ~/.config/nvim/mine.vim
Now you can start Vim with this layout: >
- vim -S ~/.vim/mine.vim
+ vim -S ~/.config/nvim/mine.vim
Hint: To open a file you see listed in the explorer window in the empty
window, move the cursor to the filename and press "O". Double clicking with
@@ -346,8 +346,8 @@ UNIX AND MS-WINDOWS
Some people have to do work on MS-Windows systems one day and on Unix another
day. If you are one of them, consider adding "slash" and "unix" to
'sessionoptions'. The session files will then be written in a format that can
-be used on both systems. This is the command to put in your vimrc file: >
-
+be used on both systems. This is the command to put in your |init.vim| file:
+>
:set sessionoptions+=unix,slash
Vim will use the Unix format then, because the MS-Windows Vim can read and
@@ -368,13 +368,13 @@ another session.
You might prefer to keep the info with the session. You will have to do
this yourself then. Example: >
- :mksession! ~/.vim/secret.vim
- :wshada! ~/.vim/secret.shada
+ :mksession! ~/.config/nvim/secret.vim
+ :wshada! ~/.local/share/nvim/shada/secret.shada
And to restore this again: >
- :source ~/.vim/secret.vim
- :rshada! ~/.vim/secret.shada
+ :source ~/.config/nvim/secret.vim
+ :rshada! ~/.local/share/nvim/shada/secret.shada
==============================================================================
*21.5* Views
@@ -423,11 +423,11 @@ to quickly switch to editing another file, with all its options set as you
saved them.
For example, to save the view of the current file: >
- :mkview ~/.vim/main.vim
+ :mkview ~/.config/nvim/main.vim
You can restore it with: >
- :source ~/.vim/main.vim
+ :source ~/.config/nvim/main.vim
==============================================================================
*21.6* Modelines