Vim cannot tell apart Ctrl-n and Ctrl-shift-n, they both resolve to
ASCII 0x0E. If I were you I would stick with F5.
Best regards,
Tony.
--
Ever notice that even the busiest people are never too busy to tell you
just how busy they are.
CTRL-N and CTRL-n both send the same ASCII code, which is what Vim
uses to determine what key is pressed. So no, Vim cannot tell the
difference.
ALT-N and ALT-n send different codes however, so you could use <m-N>
or <a-N> as the mapping's LHS. If you use alt mappings with gvim, you
may need to mess with the winaltkeys option.
Note that <F5> and <S-F5> are also distinguishable by Vim if you want
to go that route.
Ctrl-N is shown as <C-N> in mappings. In Normal mode it is an alias for
j so you can afford to remap it, but in Insert mode it is used for
"Next" in Insert-mode completion.
Similarly you can use <S-F5> for shift-F5, <M-C-End> for Ctrl-Alt-End
(where M- means "meta" and is equivalent to A-) etc.
See ":help keycodes", near the end of the list.
AFAIK, gvim cannot be made aware of the difference between Ctrl-N and
Ctrl-Shift-N: it's part of the ASCII representation of control
characters, where "Ctrl+lowercase letter" and "Ctrl+uppercase letter"
both map to "letter code AND 0x1F", obliterating the 0x20 case difference.
Best regards,
Tony.
--
If you wish to live wisely, ignore sayings -- including this one.
For the OP:
And the reason for the limitation is that Vim is designed to operate on an amazingly
large number of different systems. Only a small number of systems provide a way for
an app to learn the difference between Ctrl-N and Ctrl-Shift-N.
John