Re: Mapping control-minus and control-pipe

er those keys, and map those instead. For example, when I go to insert mode and type CTRL-V to insert the next character literally, then I type CTRL--, I see "^_" which means I should probably map rather than . However, I normally get | by pressing SHIFT-\, and CTRL-SHIFT-\ gives me

Mapping control-minus and control-pipe

Dear list, I am happy tmux and vim user, but to reduce the mistakes caused by muscle memory I would like to setup similar keybindings to the two. In tmux I use Ctrl-| to split the screen vertically and Ctrl-Minus to split horizontally. In vimrc I wrote: nnoremap v nnoremap n But it does not

Re: Key mapping not working in Insert mode of vim

sert mode. > > Think about how you would do this from normal mode and you get your answer. > > !python % in normal mode won't do what you want (if it does anything). > > But, pressing ':' first will do what you want. > > The following mapping should work: >

Re: Key mapping not working in Insert mode of vim

inoremap !python %' and attempt to use it nothing > > seems to happen. in insert mode will execute one NORMAL MODE command, then return you to insert mode. Think about how you would do this from normal mode and you get your answer. !python % in normal mode won't do what you want

Re: Key mapping not working in Insert mode of vim

On Wed, Jun 18, 2014 at 2:31 PM, Arup Rakshit wrote: > On Wednesday, June 18, 2014 03:23:01 PM David Stanek wrote: >> I haven't tried it, but this may work: >> :imap :w:!ruby %a > > This is deadly. :) *insert* to *insert*. Not showing any output :) According to the following vim.wikia post you

Re: Key mapping not working in Insert mode of vim

On Wednesday, June 18, 2014 03:23:01 PM David Stanek wrote: > I haven't tried it, but this may work: > :imap :w:!ruby %a This is deadly. :) *insert* to *insert*. Not showing any output :) -- Regards, Arup Rakshit Debugging is twice as hard as writing the code

Re: Key mapping not working in Insert mode of vim

gt; > > > The above 2 are coming when I pressed *F6* in *insert* mode. > > > > Try changing your mapping to: > > :imap :w:!ruby % > > > > This is take you out of insert mode before saving your file and running > it > > through ruby. > > Hum. It

Re: Key mapping not working in Insert mode of vim

On Wednesday, June 18, 2014 01:17:38 PM David Stanek wrote: > On Wed, Jun 18, 2014 at 11:40 AM, Arup Rakshit > > > > The above 2 are coming when I pressed *F6* in *insert* mode. > > Try changing your mapping to: > :imap :w:!ruby % > > This is take you out of

Re: Key mapping not working in Insert mode of vim

On Wed, Jun 18, 2014 at 11:40 AM, Arup Rakshit wrote: > Hi, > > I put the below key mappings in my ~/.vimrc file > > :nmap :w:!ruby % > :imap :w:!ruby % > > The mapping is working in *normal* mode, but not in *insert* mode. Can any > one > help me to fix it. When

Key mapping not working in Insert mode of vim

Hi, I put the below key mappings in my ~/.vimrc file :nmap :w:!ruby % :imap :w:!ruby % The mapping is working in *normal* mode, but not in *insert* mode. Can any one help me to fix it. When I am pressing *F6* in *insert* mode, it is printing the command itself in my program file as below

Re: mapping M-right/left to switch tabs

On Tuesday, June 17, 2014 7:08:40 AM UTC-5, Maciej Dziardziel wrote: > On Tuesday, June 17, 2014 12:36:38 PM UTC+1, Ben Fritz wrote: > > Thanks. That works, but now I realized that perhaps problem is deeper then I > thought. So now I can switch tabs regardless of the mode, > but mode seems to be

Re: mapping M-right/left to switch tabs

On Tuesday, June 17, 2014 12:36:38 PM UTC+1, Ben Fritz wrote: Thanks. That works, but now I realized that perhaps problem is deeper then I thought. So now I can switch tabs regardless of the mode, but mode seems to be global. Setting it in one tab sets it to every tab. Can it be tab-dependent? -

Re: mapping M-right/left to switch tabs

On Tuesday, June 17, 2014 6:23:26 AM UTC-5, Maciej Dziardziel wrote: > I would like to use M-right/left to move between tabs > - without leaving the mode I have set in the tab. > > :map :tabnext > > works in normal mode. For insert mode I could use > > :imap :tabnext > > but then when I'll co

mapping M-right/left to switch tabs

I would like to use M-right/left to move between tabs - without leaving the mode I have set in the tab. :map :tabnext works in normal mode. For insert mode I could use :imap :tabnext but then when I'll come back to the tab I was, I have to set insert mode again. Is there a way to keep mode i

Re: Mapping the NERDTree command

. >>> >>> Second, your syntax inside the brackets is wrong. For MacVim, you would use >>> >>> map :NERDTreeToggle >> >> Apologies, Eric, and thanks. I should've said i was using MacVim. However, >> that mapping is not working. &

Re: Mapping the NERDTree command

cVim, you would use > > > >map :NERDTreeToggle > > Apologies, Eric, and thanks. I should've said i was using MacVim. However, > that mapping is not working. Does it do anything? Even make a sound? It worked for me. -- -- You received this message from the "vim_

Re: Mapping the NERDTree command

se >> >> map :NERDTreeToggle > > Apologies, Eric, and thanks. I should've said i was using MacVim. However, > that mapping is not working. I gave up and mapped it to 'n'. -- E

Re: Mapping the NERDTree command

e said i was using MacVim. However, that mapping is not working. -- Eric Weir Decatur, GA USA eew...@bellsouth.net "Our world is a human world." - Hilary Putnam -- -- You received this mess

Re: Mapping the NERDTree command

only work if you're in the MacVim GUI. There's no way for Vim to recognize Cmd in the terminal. However, at least with iTerm2, it would be possible to configure the terminal to send a specific character sequence when you hit that combination of keys; then you could use that character sequenc

Mapping the NERDTree command

I want to map the NERDTree command to the option-command-n key combination on a Mac keyboard. I have this in my .vimrc: map :NERDTreeToggle It's not working. What am I doing wrong? Thanks, -- Eric Weir De

Re: Mapping only in specific buffer

Hi Gary, In fact I have in mind the mapping known on Windows OS used to search forward or backward in registry or in visual studio environnment. I would like to used only this keystroke to search previous or next occurence: 1/ in a diff buffer : a difference 2/ in a normal buffer : the last

Re: Mapping only in specific buffer

: norm ]c > In fact I would like to get two specific meaning on the same F2 > key as I am reading a diff buffer or a normal buffer. In that case, this in your ~/.vimrc might do what you want. nnoremap &diff ? "]c" : ":echo 'hello'" where I just mad

Re: Mapping only in specific buffer

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Why are you using :norm here? Your mapping is incorrect: 1. You do not need :norm. Just using "]c" should be enough in this circumstances. 2. You do not need :map without n. Your mapping is not going to work in visual mode (as long

Re: Mapping only in specific buffer

On 2014-06-12, Ni Va wrote: > Hi, > > > I would like to map ]c diff jump only in a vim buffer. > > I have done this for the moment but would like to make conditional > test on &diff var : > map : norm ]c If you're mapping a key to be pressed in normal m

Re: Mapping only in specific buffer

In fact I would like to get two specific meaning on the same F2 key as I am reading a diff buffer or a normal buffer. Thank you very much On Thursday, June 12, 2014 5:55:53 PM UTC+2, Ni Va wrote: > Hi, > > > I would like to map ]c diff jump only in a vim buffer. > > I have done this for the m

Mapping only in specific buffer

Hi, I would like to map ]c diff jump only in a vim buffer. I have done this for the moment but would like to make conditional test on &diff var : map : norm ]c Thank you -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you

Re: puzzling mapping behavior

first "`" mark, i.e., where i > want it. adding 'k' to the mapping has no effect I suspect you want to add the "e" flag after your "g" because the search fails. You may want to read at :help map_return " particularly the "when an error is encount

puzzling mapping behavior

this mapping: nmap 0i``:%s/\s\*\n\s\*\n\s\*\n/\r\r/g/^`` produces what seems to me an incorrect behavior. if the %s doesn't find anything, the cursor ends up on the line after the "``" mark. until recently it would land on the first "`" mark, i.e., where i w

Making the Mapping overview into a concise overview. [Was: What does ! do to map?]

On 09.05.14 10:50, ZyX wrote: Erik wrote: > > FWIW, I think that it would be possible to respect the holy 80 column > > limit, yet present one table providing a complete Overview at > > *map-overview*, not just the present partial thing, if the "modes:" > > headings were changed to "I C L N V S O

Re: Mapping a key as a switch button ?

Ooops I've missed that one, sorry. Great, it's exactely what I was looking for. Thanks -- -- You received this message from the "vim_use" 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 receive

Re: Mapping a key as a switch button ?

Am 2014-02-24 11:43, schrieb Lucas Sanner: Yes I did but I didn't see anything to fit my purpose. Any idea ? If we are talking about the same plugin, then there is a :BuffergatorToggle command, which you could simply map. Best, Christian -- -- You received this message from the "vim_use" ma

Re: Mapping a key as a switch button ?

Yes I did but I didn't see anything to fit my purpose. Any idea ? -- -- You received this message from the "vim_use" 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

Re: Mapping a key as a switch button ?

On Mi, 19 Feb 2014, Lucas Sanner wrote: > Hi, > > In my vimrc I've mapped 2 keys in order to open/close the Buffergator plugin: > > map :BuffergatorOpen > map :BuffergatorClose > > It works fine but it would be even better if it could be done with just one > key (just like a switch button).

Mapping a key as a switch button ?

Hi, In my vimrc I've mapped 2 keys in order to open/close the Buffergator plugin: map :BuffergatorOpen map :BuffergatorClose It works fine but it would be even better if it could be done with just one key (just like a switch button). Is there anyway to do that ? Thanks -- -- You receive

Re: Filetype dependent mapping when moving between splits

at a Perl file, between methods in C when > > in > > > a C source file, between keywords CREATE when in SQL, etc. I can do it on > > > BufEnter / BufWinEnter, but these don't happen when switching between > > (already > > > open) splits. >

Re: Filetype dependent mapping when moving between splits

I can do it on > BufEnter / BufWinEnter, but these don't happen when switching between (already > open) splits. Put the key mapping for each filetype in your after/ftplugin file for each filetype: ~/.vim/after/ftplugin/perl.vim ~/.vim/after/ftplugin/c.vim ~/.vim/after/ftplugin/sql

Re: Filetype dependent mapping when moving between splits

E when in SQL, etc. I can do it on > BufEnter / BufWinEnter, but these don't happen when switching between > (already open) splits. > > > > Suggestions welcome. > > First, BufEnter ought to fire when switching between splits. If not, WinEnter will. However,

Filetype dependent mapping when moving between splits

Hi all, I can't seem to figure out how to map the same key (let's say ) to jump between subs in Perl when looking at a Perl file, between methods in C when in a C source file, between keywords CREATE when in SQL, etc. I can do it on BufEnter / BufWinEnter, but these don't happen when switching bet

RE: Where does mapping come from on Windows?

Christian Brabandt wrote: >> And where is this mapping actually defined? And why only on >> Windows? > > That is hardcoded in the Vim source. It can't be true! Yet... gvim -u NONE -i NONE :map :imap gives v "*d v "*d v

Re: Where does mapping come from on Windows?

On Mon, September 9, 2013 16:33, Ben Fritz wrote: > While looking into a different issue, I found that my Windows gvim has a > mapping defined for pasting with , but not my Solaris gvim. > > I did ":verbose map " and got: > > v "-d"*P > n &quo

Where does mapping come from on Windows?

While looking into a different issue, I found that my Windows gvim has a mapping defined for pasting with , but not my Solaris gvim. I did ":verbose map " and got: v "-d"*P n "*P To my surprise, there is NO "Last set from..." message telling m

Re: Mapping <*-CR>

On Tuesday, August 27, 2013 8:21:06 AM UTC-4, Michael Henry wrote: > On 08/25/2013 05:00 PM, Thomas E. Dickey wrote: konsole's keyboard hasn't changed in a while (2008 is the most recent): http://invisible-island.net/ncurses/terminfo.ti.html#toc-_K_D_E There are a couple of general comments abo

Re: Mapping <*-CR>

On 08/25/2013 05:00 PM, Thomas E. Dickey wrote: > On Sunday, August 25, 2013 4:10:44 PM UTC-4, Michael Henry wrote: >> You may find, however, that some things don't work quite right >> now that Konsole sends xterm-compatible keycodes. The "konsole" > > Testing konsole 2.10.5 on Fedora19, I see tha

Re: Mapping <*-CR>

On 08/26/2013 05:31 AM, John Little wrote: > On Monday, August 26, 2013 8:10:44 AM UTC+12, Michael Henry wrote: >> Enter insert mode via "i", then press CTRL-v to insert the >> keycode literally, then press Shift-F1. You should see the same >> escape sequence in both Konsole and Xterm, matching th

Re: Mapping <*-CR>

On Monday, August 26, 2013 8:10:44 AM UTC+12, Michael Henry wrote: > Enter insert mode via "i", then press CTRL-v to insert the > keycode literally, then press Shift-F1. You should see the same > escape sequence in both Konsole and Xterm, matching the terminfo > entry for xterm: Er, in my Raring

Re: Mapping <*-CR>

On 25/08/13 23:40, Nikolay Pavlov wrote: >> I know about xterm. About konsole: I checked true color support by using >> screenshots and it works as expected. I doubt there may be colors >> 00, 01 and 02 in palette (except for the first one, of >> course). Konsole version is 4.10.

Re: Mapping <*-CR>

On Sunday, August 25, 2013 5:49:34 PM UTC-4, ZyX wrote: > On Aug 26, 2013 1:40 AM, "Thomas E. Dickey" wrote: > > > > > > On Sunday, August 25, 2013 5:29:10 PM UTC-4, ZyX wrote: > > > > On Aug 26, 2013 1:21 AM, "Thomas E. Dickey" wrote: > > > > > > > > > On Sunday, August 25, 2013 5:15:28 PM

Re: Mapping <*-CR>

On Aug 26, 2013 1:40 AM, "Thomas E. Dickey" wrote: > > On Sunday, August 25, 2013 5:29:10 PM UTC-4, ZyX wrote: > > On Aug 26, 2013 1:21 AM, "Thomas E. Dickey" wrote: > > > > > On Sunday, August 25, 2013 5:15:28 PM UTC-4, ZyX wrote: > > > > > > Konsole version is 4.10.4. > > > > > There are two "a

Re: Mapping <*-CR>

On Sunday, August 25, 2013 5:29:10 PM UTC-4, ZyX wrote: > On Aug 26, 2013 1:21 AM, "Thomas E. Dickey" wrote: > > > On Sunday, August 25, 2013 5:15:28 PM UTC-4, ZyX wrote: > > > > Konsole version is 4.10.4. > > > There are two "about" buttons.  The About KDE" in Fedora 19 report 4.10.5. > > I'm

Re: Mapping <*-CR>

On Aug 26, 2013 1:35 AM, "Tony Mechelynck" wrote: > > On 25/08/13 23:15, Nikolay Pavlov wrote: >> >> >> On Aug 26, 2013 1:00 AM, "Thomas E. Dickey" > > wrote: >> > >> > On Sunday, August 25, 2013 4:10:44 PM UTC-4, Michael Henry wrote: >> > > On 08/25/2013 02:16 PM, Nikola

Re: Mapping <*-CR>

On 25/08/13 23:15, Nikolay Pavlov wrote: On Aug 26, 2013 1:00 AM, "Thomas E. Dickey" mailto:dic...@his.com>> wrote: > > On Sunday, August 25, 2013 4:10:44 PM UTC-4, Michael Henry wrote: > > On 08/25/2013 02:16 PM, Nikolay Pavlov wrote: > > > > > TERM=konsole and TERM=konsole-256color are co

Re: Mapping <*-CR>

On Aug 26, 2013 1:21 AM, "Thomas E. Dickey" wrote: > > On Sunday, August 25, 2013 5:15:28 PM UTC-4, ZyX wrote: > > > Konsole version is 4.10.4. > > There are two "about" buttons. The About KDE" in Fedora 19 report 4.10.5. > I'm talking about the one for konsole (2.10.5). I do not use "about" but

Re: Mapping <*-CR>

On Sunday, August 25, 2013 5:15:28 PM UTC-4, ZyX wrote: > Konsole version is 4.10.4. There are two "about" buttons. The About KDE" in Fedora 19 report 4.10.5. I'm talking about the one for konsole (2.10.5). -- -- You received this message from the "vim_use" maillist. Do not top-post! Type you

Re: Mapping <*-CR>

On Aug 26, 2013 1:00 AM, "Thomas E. Dickey" wrote: > > On Sunday, August 25, 2013 4:10:44 PM UTC-4, Michael Henry wrote: > > On 08/25/2013 02:16 PM, Nikolay Pavlov wrote: > > > > > TERM=konsole and TERM=konsole-256color are contained in my > > > terminfo database, seem to work fine with konsole an

Re: Mapping <*-CR>

On Sunday, August 25, 2013 4:10:44 PM UTC-4, Michael Henry wrote: > On 08/25/2013 02:16 PM, Nikolay Pavlov wrote: > > > TERM=konsole and TERM=konsole-256color are contained in my > > terminfo database, seem to work fine with konsole and can be > > configured in profiles/environment variables. To m

Re: Mapping <*-CR>

On 08/25/2013 02:16 PM, Nikolay Pavlov wrote: > TERM=konsole and TERM=konsole-256color are contained in my > terminfo database, seem to work fine with konsole and can be > configured in profiles/environment variables. To my surprise, > files in /usr/share/terminfo regarding konsole were installed >

Re: Mapping <*-CR>

On Aug 25, 2013 7:57 PM, "Tony Mechelynck" wrote: > GPM can only work on a pure-text console which is not an > emulator but the hardware of your monitor and video in text > mode. As such, it has no connection to X and therefore > should NEVER have $TERM set to "xterm". Mainly I was trying to give

Re: Mapping <*-CR>

On 25/08/13 20:16, Nikolay Pavlov wrote: [...] Note that konsole is the only terminal I know that supports true color. Using non-standard $TERM makes me able to recognize konsole and enable true color support in some applications (i.e. vim, there is a patch for this lying somewhere, search for 'g

Re: Mapping <*-CR>

On Aug 25, 2013 7:57 PM, "Tony Mechelynck" wrote: > > On 25/08/13 16:04, Michael Henry wrote: >> >> On 08/20/2013 05:38 AM, John Little wrote: >>> >>> Documentation can be confusing and can conflict with empirically determined behavior. >>> >>> >>> A plug for xterm. >>> >>> xterm is well

Re: Mapping <*-CR>

On 25/08/13 16:04, Michael Henry wrote: On 08/20/2013 05:38 AM, John Little wrote: Documentation can be confusing and can conflict with empirically determined behavior. A plug for xterm. xterm is well maintained by Thomas Dickey, who has been seen on vim_dev. If you have a problem with its

Re: Mapping <*-CR>

On 08/20/2013 05:38 AM, John Little wrote: > >> Documentation can be confusing and can conflict with empirically >> determined behavior. > > A plug for xterm. > > xterm is well maintained by Thomas Dickey, who has been seen > on vim_dev. If you have a problem with its documentation, I > think he'd

Re: Mapping <*-CR>

On Tuesday, August 20, 2013 9:14:56 AM UTC+12, Gautier DI FOLCO wrote: >I should mention that terminals are strange beasts. >Documentation can be confusing and can conflict with empirically >determined behavior. A plug for xterm. xterm is well maintained by Thomas Dickey, who has been seen on vi

Re: Mapping <*-CR>

2013/8/18 Michael Henry > On 08/17/2013 02:35 PM, Gautier DI FOLCO wrote: > > 2013/8/16 Ben Fritz > > > You can try using whatever you get by actually typing > > > as the left side of a mapping. E.g. so you > > > mapping looks like: > > > > &

Re: Mapping <*-CR>

... > Yes, in theory. I'm not exactly sure how to get any of those problematic >> ones working in the terminal. >> >> You can try using whatever you get by actually typing as the >> left side of a mapping. E.g. so you mapping looks like: >> >> map

Re: Mapping <*-CR>

On 08/17/2013 02:35 PM, Gautier DI FOLCO wrote: > 2013/8/16 Ben Fritz > > You can try using whatever you get by actually typing > > as the left side of a mapping. E.g. so you > > mapping looks like: > > > map ^[0^M A > > Thanks, It works but I feel dirty :/ I

Re: Mapping <*-CR>

I'm not exactly sure how to get any of those problematic > ones working in the terminal. > > You can try using whatever you get by actually typing as the > left side of a mapping. E.g. so you mapping looks like: > > map ^[0^M A > > But that's not very pretty...I t

Re: Mapping <*-CR>

matic ones working in the terminal. You can try using whatever you get by actually typing as the left side of a mapping. E.g. so you mapping looks like: map ^[0^M A But that's not very pretty...I think there's a way to actually fix it. I mostly use GUI Vim, so most mappings I tr

Re: Mapping <*-CR>

2013/8/16 Ben Fritz > On Friday, August 16, 2013 9:55:56 AM UTC-5, Gautier DI FOLCO wrote: > > Hi all, > > > > I'm using ViM 7.3 on FreeBSD 9.1 and I have some troubles with mapping > and : > > > > map A > > map A > > > > > >

Re: Mapping <*-CR>

On Friday, August 16, 2013 9:55:56 AM UTC-5, Gautier DI FOLCO wrote: > Hi all, > > I'm using ViM 7.3 on FreeBSD 9.1 and I have some troubles with mapping > and : > > map A > map A > > > It doesn't work, have you the same issue or an idea of a s

Mapping <*-CR>

Hi all, I'm using ViM 7.3 on FreeBSD 9.1 and I have some troubles with mapping and : map A map A It doesn't work, have you the same issue or an idea of a solution? For your help, Thanks by advance. -- -- You received this message from the "vim_use" maillist. Do not

Re: Mapping Macro using smartindent

Hello Ben, sry for stealing your time. :/ I'm an jackass. Actually the whole thing works - better than me. Because: I tried to do the following while testing: __for(;;) __{ __} Cindent/Smarindent catches that there is no need to start at column 2 because there is no embedding block around. I

Re: Mapping Macro using smartindent

On Monday, July 29, 2013 12:45:09 AM UTC-5, SVN77KMF wrote: > > It looks like indentation wouldn't work in mappings, right? > > Actually, yes it does. In fact, your mapping works just fine for me, launching gvim with gvim -N -u NONE -i NONE, setting your mapping, setti

Re: Mapping Macro using smartindent

ings. > > > > > > Smartindent > > > is on, but doesn't > > > work appropriatly. > > > > > > > > > > >

Re: Mapping Macro using smartindent

ings. > > > > > > Smartindent > > > is on, but doesn't > > > work appropriatly. > > > > > > > > > > >

Re: Mapping Macro using smartindent

work appropriatly. > > > > Example: > > > > Assume the following mapping: > > > > imap { > {}iko > I suggest using cindent i

Mapping Macro using smartindent

Hello, Itry to speed up writing using mappings. Smartindent is on, but doesn't work appropriatly. Example: Assume the following mapping: imap { {}iko Typing "{" (Quotes for clarification) results in " { _ } " (where "_" is the cursor position) -> Perfect

Re: Mapping meta key within tmux

On 2013–07–14 Gary Johnson wrote: > I didn't have much time for experimentation when I first replied. > Now that I have a little more time, mapping the sequence for > proved more difficult than I expected. I think the secret is to put > this in your ~/.tmux.conf: > >

Re: Mapping meta key within tmux

:kf6=\e[17~:kf7=\e[18~:kf8=\e[19~" > > I can't figure out the correct command line. The terminfo man page > is a terrible read. > > > Yet another way is to redefine those keys in your ~/.vimrc as I did > > originally fix the same problem. > >

Re: Mapping meta key within tmux

of the terminals exactly (line-drawing, color, function keys all have issues). tmux does not appear to implement this mapping (If tmux adopted that feature, it would be an improvement). -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the

Re: Mapping meta key within tmux

terminal-overrides > "*:kf1=\e[11~:kf2=\e[12~:kf3=\e[13~:kf4=\e[14~:kf5=\e[15~:kf6=\e[17~:kf7=\e[18~:kf8=\e[19~" I can't figure out the correct command line. The terminfo man page is a terrible read. > Yet another way is to redefine those keys in your ~/.vimrc as I did > or

Re: Mapping meta key within tmux

On 2013-07-12, Marco wrote: > Hi, > > I have mappings in my .vimrc that map the Meta-arrow keys > > noremap + > noremap - > > This works fine in console vim, but it fails when vim is used within > tmux. Then I get sequences like: > > [1;3Aá] > [1;3Bá] > > When I call cat -v from th

Mapping meta key within tmux

Hi, I have mappings in my .vimrc that map the Meta-arrow keys noremap + noremap - This works fine in console vim, but it fails when vim is used within tmux. Then I get sequences like: [1;3Aá] [1;3Bá] When I call cat -v from the console (TERM=rxvt-unicode-256color) and press M- M- I

UltiSnips in macro/mapping leaves me in Insert mode

inert mode here I see this same problem invoking a snippet from a mapping. Adding more s doesn't help. How can I complete the mapping or register execution back in normal mode? Thanks, Steve -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your

Re: insert mode mapping to move to a column

you use this move *REALLY* often, consider using a mapping > > like : > > > > inoremap w kwji > > > > And then you're done. :) > > > > regards, > > > > Willy Hi Willy, am i missing something, just a plain kwj doesn't

Re: insert mode mapping to move to a column

if you'd typed four keys: <, U, p and >. You'd have to > actually do something like :normal (that's hitting a > control-V to get a literal character and then hitting UP to actually > have it insert the character code for the up key). > > Your best bet

Re: insert mode mapping to move to a column

On Mon, Jun 3, 2013 at 10:38 AM, Ben Fritz wrote: > > On Monday, June 3, 2013 1:31:08 AM UTC-5, sinbad wrote: > > On Thursday, May 30, 2013 10:59:52 AM UTC+5:30, sinbad wrote: > > > > set ve=all is little annoying to be set > > all the time, at least i'm not use to it. > > how can i temporarily se

Re: insert mode mapping to move to a column

On Monday, June 3, 2013 1:31:08 AM UTC-5, sinbad wrote: > On Thursday, May 30, 2013 10:59:52 AM UTC+5:30, sinbad wrote: > > On Wednesday, May 29, 2013 8:31:09 PM UTC+5:30, Ben Fritz wrote: > > > I think (if as Christian suggests you have 'virtualedit' set to "all") > > > this will work: > > > >

Re: insert mode mapping to move to a column

On Thursday, May 30, 2013 10:59:52 AM UTC+5:30, sinbad wrote: > On Wednesday, May 29, 2013 8:31:09 PM UTC+5:30, Ben Fritz wrote: > > I think (if as Christian suggests you have 'virtualedit' set to "all") this > > will work: > > This works, thanks Ben and toothpik. set ve=all is little annoying

Re: insert mode mapping to move to a column

On Wednesday, May 29, 2013 8:31:09 PM UTC+5:30, Ben Fritz wrote: > I think (if as Christian suggests you have 'virtualedit' set to "all") this > will work: This works, thanks Ben and toothpik. -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below

Re: insert mode mapping to move to a column

On Wednesday, May 29, 2013 6:20:36 AM UTC-5, sinbad wrote: > > I believe you are looking for CTRL-Right (the right cursor arrow > > no this isn't working. "This isn't working" to me could mean that you tried it and it went to the next word in the CURRENT line, which is what the command SHOULD do

Re: insert mode mapping to move to a column

> I believe you are looking for CTRL-Right (the right cursor arrow no this isn't working. -- -- You received this message from the "vim_use" 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 rece

Re: insert mode mapping to move to a column

> Then you can type from insert mode 6| > and continue inserting in column 6 except that i'll have to count the column number everytime. i want to be able to do this automatically. -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text y

Re: insert mode mapping to move to a column

On Wed, May 29, 2013 at 02:15:40AM -0700, sinbad wrote: > how to move to a column in the current line, > to the column same as the next word from > the current position in the above line. > This is the best i could explain. > example. > 123456789 > move to here > i* > * - do something here such

Re: insert mode mapping to move to a column

On Wed, May 29, 2013 11:15, sinbad wrote: > how to move to a column in the current line, > to the column same as the next word from > the current position in the above line. > This is the best i could explain. > > example. > > 123456789 > move to here > i* > > * - do something here such that i > au

insert mode mapping to move to a column

how to move to a column in the current line, to the column same as the next word from the current position in the above line. This is the best i could explain. example. 123456789 move to here i* * - do something here such that i automatically go to column 6, which is the next starting word from

Re: Is there already a solution for mapping in Terminal (urxvt)?

thanks Tony, thanks LCD 47 I just did some test again, didn't find solution... :( I think the mapping works here. my problem is the keycode timeout.. Normal mode mapping I have no problem, but Insert mode let's say, I tried followings: inoremap ^[j :m-2==gi(c-v then

Re: Is there already a solution for mapping in Terminal (urxvt)?

On 03/04/13 09:49, LCD 47 wrote: On 2 April 2013, Kent wrote: [...] What I want to map is simple, move current line up/down. [...] The keyboard bindings for in urxvt depend on the URxvt.meta8 resource. If URxvt.meta8 is false (which is the default), sends and thus you need to write

Re: Is there already a solution for mapping in Terminal (urxvt)?

On 2 April 2013, Kent wrote: [...] > What I want to map is simple, move current line up/down. [...] The keyboard bindings for in urxvt depend on the URxvt.meta8 resource. If URxvt.meta8 is false (which is the default), sends and thus you need to write your maps for mumble: nnoremap j

Re: Is there already a solution for mapping in Terminal (urxvt)?

, and found my very old commented out codes: "mapping in unxvt doesn't work, gave up!! about 3,4 years have past, I did some tests just now, it still didn't work. What I want to map is simple, move current line up/down. The mapping is easy. point is how to make work. what

Re: Is there already a solution for mapping in Terminal (urxvt)?

On 02/04/13 22:47, Kent wrote: Hi everybody, I knew this is not a new topic. I had that problem years ago, tried a lot and finally gave up. Recently, I went through my vimrc, and found my very old commented out codes: "mapping in unxvt doesn't work, gave up!! about 3,4 years

<    1   2   3   4   5   6   7   8   >