nano-devel
[Top][All Lists]
Advanced

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

[Nano-devel] Re: bug in indent/unindent


From: David Lawrence Ramsey
Subject: [Nano-devel] Re: bug in indent/unindent
Date: Sun, 30 Apr 2006 22:40:18 -0400
User-agent: Thunderbird 1.5 (X11/20051201)

Benno Schulenberg wrote:

<snip>

>>  > At the moment, in CVS, M-[ indents and M-] unindents; to me the
>>  > other way around would seem more logical.
>>
>> I have a good reason for the current order.  See below.
>
> Below I haven't seen an explanation for this, or it should be that
> users are more likely to unindent than indent, and for this reason the
> unindent key is the undelayed one?

Sorry, I misread this.  I was thinking that you said putting e.g. M-{
first and M-[ second wasn't logical, for some reason.  As for why M-{ is
first, it's because of the delay associated with M-[.  I've reversed
them per your actual suggestion, in any case, since the keys are right
next to each other.

<snip>

> It happens no more.  Looks like it's fixed.

Oh good.

<snip>

> Weird. In my opinion this delay makes M-[ into an unusable key. > Having to wait for it to take effect, without any indication that one
> has to wait...  Better use the ticks then: M-` and M-'.

I'd prefer to keep them the way they are, for the above reason.  In the
meantime, you can always use the shift key to get Meta-{...

By the way, about what you were saying about M-_: M-- works in
rxvt-unicode as well as the console, but nowhere else I've tested.  I've
also checked the control key input mode, and it isn't there either.  On
the other hand, I didn't know that ^/ was equivalent to ^_, so it's now
handled in the control key input mode.  Displaying it differently in the
help text (as you suggested before) and everywhere else would be another
ugly hack, though.





reply via email to

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