[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: binding ibuffer to C-x C-b by default
From: |
Sergei Organov |
Subject: |
Re: binding ibuffer to C-x C-b by default |
Date: |
Fri, 08 Oct 2010 15:22:20 +0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) |
"Stephen J. Turnbull" <address@hidden> writes:
> Sergei Organov writes:
>
> > Another annoyance is that pushing <down> at the end of ibuffer wraps
> > around to the beginning of it (and <up> also wraps at the beginning to
> > the end). No other mode of emacs behaves like this, right?
>
> Depends on how close "like" needs to be.
Yeah, I meant I never experienced any other buffer where pressing <down>
at the end of buffer brings me to the beginning of the buffer.
Actually, it's wrapping on "mark" commands that really annoys me.
Probably I should learn something like
`ibuffer-mark-to-the-end-of-buffer', that doesn't seem to exist, but I
used to do it by just holding corresponding key (e.g., 'D'). (Yes, I
know about 'ibuffer-mark-old-buffers').
BTW, there is another inconsistency in ibuffer: C-n and <down> are
bound to different functions that also seems to be unique property of
ibuffer.
> Specifically, isearch wraps if you repeat a search immediately after
> getting a buffer-boundary error. That's not an arrow key, and you do
> have to "insist" to get the wrapping behavior, but for my money that's
> similar behavior.
Yes it's similar, but not similarly annoying, as one pays much more
attention to the screen at every key-press during search compared to
simple <down> in the buffer.
> In the case of search it's very useful.
Exactly. But it's useless and annoying in ibuffer as if I want to get to
the beginning (or end) of the buffer, I always know how to do it, while
'isearch' doesn't have a way to get to the first/last occurrence in the
buffer easily.
> Rings (kill rings, completion history) are another example.
Yes, but they are not buffers either, though 'yank-pop' wrapping is also
annoying, IMHO, and neither *Completions* buffer nor minibuffer history
wraps for me.
--
Sergei.
- Re: binding ibuffer to C-x C-b by default, (continued)
- Re: binding ibuffer to C-x C-b by default, David Kastrup, 2010/10/08
- Re: binding ibuffer to C-x C-b by default, Ted Zlatanov, 2010/10/08
- Re: binding ibuffer to C-x C-b by default, Ted Zlatanov, 2010/10/08
- Re: binding ibuffer to C-x C-b by default, Lars Magne Ingebrigtsen, 2010/10/08
- Re: binding ibuffer to C-x C-b by default, Miles Bader, 2010/10/08
- Re: binding ibuffer to C-x C-b by default, Dan Nicolaescu, 2010/10/08
- Re: binding ibuffer to C-x C-b by default, Sergei Organov, 2010/10/08
- Re: binding ibuffer to C-x C-b by default, Stephen J. Turnbull, 2010/10/08
- Re: binding ibuffer to C-x C-b by default,
Sergei Organov <=
- Re: binding ibuffer to C-x C-b by default, Chong Yidong, 2010/10/09
- Re: binding ibuffer to C-x C-b by default, Dan Nicolaescu, 2010/10/09
- Re: binding ibuffer to C-x C-b by default, Lars Magne Ingebrigtsen, 2010/10/09
- RE: binding ibuffer to C-x C-b by default, Drew Adams, 2010/10/07
- Re: binding ibuffer to C-x C-b by default, Miles Bader, 2010/10/07
- RE: binding ibuffer to C-x C-b by default, Drew Adams, 2010/10/07
- Re: binding ibuffer to C-x C-b by default, Juanma Barranquero, 2010/10/07
- Re: binding ibuffer to C-x C-b by default, Miles Bader, 2010/10/07
- Re: binding ibuffer to C-x C-b by default, Juanma Barranquero, 2010/10/08
- Re: binding ibuffer to C-x C-b by default, Chong Yidong, 2010/10/09