aboutsummaryrefslogtreecommitdiff
path: root/runtime/doc/cmdline.txt
diff options
context:
space:
mode:
authorMichael Reed <m.reed@mykolab.com>2014-11-18 01:44:47 -0500
committerMichael Reed <m.reed@mykolab.com>2014-11-27 23:42:40 -0500
commitba1e2ce287752a1bd30d52f77493a5bb582c2349 (patch)
tree0e9041ec9f2b566d3aed97fa8bf03a43ecd09830 /runtime/doc/cmdline.txt
parent83a4c9d58ce9265fc5b18e1f4e289552a56e9a56 (diff)
downloadrneovim-ba1e2ce287752a1bd30d52f77493a5bb582c2349.tar.gz
rneovim-ba1e2ce287752a1bd30d52f77493a5bb582c2349.tar.bz2
rneovim-ba1e2ce287752a1bd30d52f77493a5bb582c2349.zip
Remove OS/2 references
Paul Slootman was removed from the top of os_unix.c as OS/2 is no longer supported, but is still credited in runtime/doc/intro.txt.
Diffstat (limited to 'runtime/doc/cmdline.txt')
-rw-r--r--runtime/doc/cmdline.txt10
1 files changed, 5 insertions, 5 deletions
diff --git a/runtime/doc/cmdline.txt b/runtime/doc/cmdline.txt
index f58389af8c..2892faa496 100644
--- a/runtime/doc/cmdline.txt
+++ b/runtime/doc/cmdline.txt
@@ -855,7 +855,7 @@ These modifiers can be given, in this order:
separator is removed. Thus ":p:h" on a directory name results
on the directory name itself (without trailing slash).
When the file name is an absolute path (starts with "/" for
- Unix; "x:\" for MS-DOS, WIN32, OS/2; "drive:" for Amiga), that
+ Unix; "x:\" for MS-DOS, WIN32; "drive:" for Amiga), that
part is not removed. When there is no head (path is relative
to current directory) the result is empty.
:t Tail of the file name (last component of the name). Must
@@ -954,10 +954,10 @@ option contains "sh", this is done twice, to avoid the shell trying to expand
the "!".
*filename-backslash*
-For filesystems that use a backslash as directory separator (MS-DOS, Windows,
-OS/2), it's a bit difficult to recognize a backslash that is used to escape
-the special meaning of the next character. The general rule is: If the
-backslash is followed by a normal file name character, it does not have a
+For filesystems that use a backslash as directory separator (MS-DOS and
+Windows), it's a bit difficult to recognize a backslash that is used
+to escape the special meaning of the next character. The general rule is: If
+the backslash is followed by a normal file name character, it does not have a
special meaning. Therefore "\file\foo" is a valid file name, you don't have
to type the backslash twice.