vile
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[vile] vile map behavior change


From: Paul Fox
Subject: [vile] vile map behavior change
Date: Wed, 18 Jan 2012 09:37:47 -0500

hi --

somewhere between 9.7ze and 9.8d, the behavior of the following
map command (in .vilerc) changed:

    map \t f}

this used to map the tab character.  now it maps the literal
two-character sequence "\t".  using the literal character to be mapped
would work for other control chars, but tab of course is whitespace. 
doing this (where the character after the control-V is a tab) works:

    map ^V       f}

i see the new behavior is matched by vim, so presumably this was
a compatibility change.  i also see that vim has some extra map
commands to deal with this, so i guess it's a hard problem.

but the help file still shows this:
   The left hand side of a map[!] definition may contain the usual backslash
   escapes: \n, \r, \t, \b, \f, \a (^G), \e (ESC), \s (SPACE), \xNN
   (hexadecimal), \NNN (octal). The right hand side is taken exactly
   literally, so special characters must be expressed as themselves.

i guess that paragraph should be dropped, and a new one describing
the use of ^V added.  not sure that will work with newline, though.

paul
=---------------------
 paul fox, address@hidden (arlington, ma, where it's 30.6 degrees)



reply via email to

[Prev in Thread] Current Thread [Next in Thread]