Re: Undead buffer: gets deleted but respawns on session launch

On Tuesday, April 23, 2013 at 8:41:08 AM UTC-7, Sylvia Ganush wrote: > Good day. > > What may cause a deleted buffer to reappear on session launch? > > I once edited a file, a Figlet font. I deleted the buffer, and > then exited Vim as I usually do: > > :mksession! session.vim > :wqa >

A mapping with a manual insert mode in the middle

Greetings! I'd like to create a mapping in my .vimrc that does some manipulation, drops me into insert mode, then picks back up for more manipulation after I hit escape. Is this possible? I guess I just don't know what to search for. Any help would be greatly appreciated. -- -- You

Re: man.vim and ansi escape characters

Den søndag den 15. januar 2017 kl. 22.58.57 UTC+1 skrev Frank Shute: > My guess is that your version of Linux is set up to show colorised man pages > and that is why you're getting those wacky escape sequences. > > Have a look at the manpage for man. It might indicate how to turn that feature >

Re: Having certain lines readonly

неделя, 15 януари 2017 г., 16:10:42 UTC+2, lith написа: > > Thank for your post. I figured out that I can simulate readonly lines by > > keeping metadata about lines and remapping all keys to a function which > > decides upon that metadata whether to put the character in question. > > An

Re: Set cusror position from inside function

Hi, Alessandro, Here is Key_k() function (the other functions are analogous, only l:lineToGo and l:columnToGo are set to different values): function Key_k() > let l:lineToGo = line(".") - 1 > let l:columnToGo = col(".") > let b:noteUnderCursor = GetNoteOnLine(l:lineToGo) > call

Re: Set cusror position from inside function

Hi, Tihomir. Looking at your message I can't see from were the 'a:line' and 'a:column' variables did come from. The way you are calling the set of "Key_*()" functions, you are not passing any information through parameters. So I'm assuming you are discovering these values inside the function.

Re: Vim 8 command line history not working

Oh, thanks very much Christian - I'll add another post to the PCLinuxOS forum and ask for an update to 8.0.172. Cheers G On 16 January 2017 at 12:13, Christian Brabandt wrote: > Hi Grahame! > > On Mo, 16 Jan 2017, Grahame Blackwood wrote: > > > Hi > > > > PCLinuxOS has

Re: Vim 8 command line history not working

Hi Grahame! On Mo, 16 Jan 2017, Grahame Blackwood wrote: > Hi > > PCLinuxOS has just upgraded Vim to version 8.0.163 but since then the command > line history doesn't work for me. The problem is that any command listed by q/ > and selected for action just returns me to the file being edited. >

Vim 8 command line history not working

Hi PCLinuxOS has just upgraded Vim to version 8.0.163 but since then the command line history doesn't work for me. The problem is that any command listed by q/ and selected for action just returns me to the file being edited. I've tried to find out if any of the plugins I use are responsible by

mksession saves closed buffers when it should not

Here is my sessionoptions: sessionoptions=blank,curdir,folds,help,options,tabpages,winsize (removed the 'buffer' defaults) I open 3 tabs with 'vim -p *py'. I close one of those tabs and save session with 'mksession!'. When I 'vim -S session.vim' it still open 3 tabs including the closed