>In Vim, I have set the timeout to 200 milliseconds rather than the
>default 1000 (one whole second).
>
>This amounts to a typing speed of c. 5 characters per second or 60 wpm,
>a reasonable goal for the average typist.
ditto. about half the default is much better.
--
Roger
http://rogerx.freesh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/23/12 2:50 AM, Dan Douglas wrote:
> Hello, In the case of exported functions, Bash interprets a copy descriptor
> followed by an expansion as the >& synonym for &>, resulting in the output
> going to a file named as the value of the FD it's give
On Mon, Jan 23, 2012 at 07:38:52PM EST, Chet Ramey wrote:
> On 1/23/12 8:52 AM, Roger wrote:
>
> > A little more indepth examination, and I can see VIM's wait is
> > approximately double of what the readline patch's wait time is.
> > However, I think the shorter wait time is more functional as whe
[re-adding the list - also, please don't top-post on technical lists]
On 01/24/2012 06:53 PM, Jim Avera wrote:
> Thanks for the quick reply. I read the referenced article and don't
> think it says that at all.
> (http://austingroupbugs.net/view.php?id=52). In fact it seems to imply
> that -e *s
On 1/23/12 5:42 AM, Andreas Schwab wrote:
>> you might want to report a bug to suse, here i get:
>
> It's a bug in --enable-separate-helpfiles: the generated file contains
> only one help string for echo, which happens to be the one for !V9_ECHO.
It seems like the only way to solve this reliably
On 1/23/12 8:22 PM, Roger wrote:
>> Patch seems to work great and I can now type 'exit' without command mode
>> being spawned when typing the 'i'.
>>
>> It's behaviour is almost identical to VIM's.
>
> Found a bug.
That's not really related to the timing issue, since the `i' is dropped
completel
