Re: Making vim not spuriously undo lots of changes
- On Friday, September 20, 2013 7:30:49 AM UTC-5, Paul Evans wrote:
> On Thu, 22 Aug 2013 17:24:15 +0100Are you able to do a loop to build up such mappings as strings to :execute? That would be nicer than individually doing 7*60 mappings.
> Paul "LeoNerd" Evans <leonerd@...> wrote:
> > However, I believe we can all agree this is unsustainable, as I don't
> > want to have to store a map and an imap command 7 times for each of
> > the ~60-odd Unicode keys I could type.
> > Instead does anyone have a better idea here?
> Do I take from the relative silence in this thread then that nobody
> actually has a better idea after all?
> I may be forced to consider fixing the source, then.
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 vim_dev+unsubscribe@....
For more options, visit https://groups.google.com/groups/opt_out.
- On Fri, 20 Sep 2013 07:15:35 -0700 (PDT)
Ben Fritz <fritzophrenic@...> wrote:
> Are you able to do a loop to build up such mappings as stringsNot really. I mean, that's what I do right now and it's horrible.
> to :execute? That would be nicer than individually doing 7*60
In practice it might not be quite so bad but that's still a huge number
Plus, these things aren't really static strings; they are encodings.
All these things should mean the same thing
CSI 65 ; 1 u
CSI 000065; 00001 u
CSI 00065;0001;000000;00000235 u
They're a protocol encoding information about a keypress; not simple
static strings. I'd much prefer that vim's input system could
-understand- these as being real CSI sequences and pull them apart
properly, than just store a huge static string database.
Paul "LeoNerd" Evans
ICQ# 4135350 | Registered Linux# 179460