From 39366733c3fe943363566756e2e152c45a1b3cb2 Mon Sep 17 00:00:00 2001 From: Patrick J Volkerding Date: Fri, 25 May 2018 23:29:36 +0000 Subject: Fri May 25 23:29:36 UTC 2018 patches/packages/glibc-zoneinfo-2018e-noarch-2_slack14.2.txz: Rebuilt. Handle removal of US/Pacific-New timezone. If we see that the machine is using this, it will be automatically switched to US/Pacific. --- slackbook/html/vi-saving-files.html | 103 ------------------------------------ 1 file changed, 103 deletions(-) delete mode 100644 slackbook/html/vi-saving-files.html (limited to 'slackbook/html/vi-saving-files.html') diff --git a/slackbook/html/vi-saving-files.html b/slackbook/html/vi-saving-files.html deleted file mode 100644 index 137c46b54..000000000 --- a/slackbook/html/vi-saving-files.html +++ /dev/null @@ -1,103 +0,0 @@ - - - - -Saving Files - - - - - - - - - - - -
-

16.4 Saving -Files

- -

There are several ways to save files in vi. If you want to -save the current buffer to the file randomness, you would -type:

- - - - - -
-
-:w randomness
-
-
- -

Once you've saved the file once, saving it again is as simple as typing :w. Any changes will be written out to the file. After you've saved -the file, you are dumped back into command mode. If you want to save the file and quit -vi (a very common operation), you would type :wq. That tells vi to save the current file -and quit back to the shell.

- -

On occasion, you want to save a file that is marked as read-only. You can do this by -adding an exclamation point after the write command, like so:

- - - - - -
-
-:w!
-
-
- -

However, there will still be instances where you cannot write the file (for example, -you are attempting to edit a file that is owned by another user). When this happens, vi will tell you that it cannot save the file. If you really want to -edit the file, you'll have to come back and edit it as root or -(preferably) the owner of that file.

-
- - - - - -- cgit v1.2.3