Hi,

2016/2/18 Thu 4:48:46 UTC+9 Bram Moolenaar wrote:
> > Mac OS has also some default mappings, but it seems that they are not
> > documented.
> > https://github.com/vim/vim/blob/master/src/getchar.c#L5307-L5316
> > Maybe it's better to add them to the documents.
> 
> I hope someone can do that.  I like complete docs.

I have added description for standard mappings on macOS (based on the source
code).
I'm not a macOS user, so review by mac users is welcome.


BTW, on MS-Windows, Shift-Insert is mapped to <C-R><C-O>* in Insert mode:
    https://github.com/vim/vim/blob/a37ffaa/src/getchar.c#L5262

However, on macOS, Command-v is mapped to <C-R>* in Insert mode:
    https://github.com/vim/vim/blob/a37ffaa/src/getchar.c#L5299

Isn't it better to map to <C-R><C-O>* also on macOS?
This breaks backward compatibility though.

Regards,
Ken Takata

-- 
-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.
# HG changeset patch
# Parent  7ba9cf11eef2e88ae555971dbbffef7d4d196658

diff --git a/runtime/doc/os_mac.txt b/runtime/doc/os_mac.txt
--- a/runtime/doc/os_mac.txt
+++ b/runtime/doc/os_mac.txt
@@ -12,11 +12,12 @@ NOTE: This file is a bit outdated.  You 
 	http://macvim.org/
 
 1. Filename Convention		|mac-filename|
-2. .vimrc an .vim files		|mac-vimfile|
-3. FAQ				|mac-faq|
-4. Known Lack			|mac-lack|
-5. Mac Bug Report		|mac-bug|
-6. Compiling Vim		|mac-compile|
+2. .vimrc and .vim files	|mac-vimfile|
+3. Standard mappings		|mac-standard-mappings|
+4. FAQ				|mac-faq|
+5. Known Lack			|mac-lack|
+6. Mac Bug Report		|mac-bug|
+7. Compiling Vim		|mac-compile|
 
 There was a Mac port for version 3.0 of Vim.  Here are the first few lines
 from the old file:
@@ -72,7 +73,18 @@ the |'nocompatible'| option is set, othe
 files.
 
 ==============================================================================
-3. Mac FAQ						*mac-faq*
+3. Standard mappings				*mac-standard-mappings*
+
+The following mappings are available for cut/copy/paste from/to clipboard.
+
+key		Normal	Visual	  Insert	Description ~
+Command-v	"*P	"-d"*P    <C-R>*	paste text       *<D-v>*
+Command-c		"*y			copy Visual text *<D-c>*
+Command-x		"*d			cut Visual text  *<D-x>*
+Backspace		"*d			cut Visual text
+
+==============================================================================
+4. Mac FAQ						*mac-faq*
 
 On the internet:  http://macvim.org/OSX/index.php#FAQ
 
@@ -95,13 +107,13 @@ A: The following trick works with most s
 	let $PATH = matchstr(s:path, 'VIMPATH\zs.\{-}\ze\n')
 
 ==============================================================================
-4. Mac Lack						*mac-lack*
+5. Mac Lack						*mac-lack*
 
 In a terminal CTRL-^ needs to be entered as Shift-Control-6.  CTRL-@ as
 Shift-Control-2.
 
 ==============================================================================
-5. Mac Bug Report					*mac-bug*
+6. Mac Bug Report					*mac-bug*
 
 When reporting any Mac specific bug or feature change, please use the vim-mac
 maillist |vim-mac|.  However, you need to be subscribed.  An alternative is to
@@ -110,7 +122,7 @@ send a message to the current MacVim mai
 	[email protected]
 
 ==============================================================================
-6. Compiling Vim					*mac-compile*
+7. Compiling Vim					*mac-compile*
 
 See the file "src/INSTALLmac.txt" that comes with the source files.
 

Raspunde prin e-mail lui