[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
improvements to the "lossage buffer"
From: |
Emanuel Berg |
Subject: |
improvements to the "lossage buffer" |
Date: |
Wed, 31 Jul 2019 00:56:19 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
`view-lossage' seems to have improved in
a recent Emacs version upgrade, since it now
displays a neat flow of information with one
key (or one key sequence) on each row with,
even more of an improvement, the name of the
command in square brackets following the
key. E.g.,
k [next-line]
i [previous-line]
k [next-line]
RET [buffer-menu-kill-and-open]
C-j e . [anonymous-command]
ESC o [other-window-or-split]
ESC o [other-window-or-split]
ESC o [other-window-or-split]
ESC p [delete-other-windows]
C-o k [end-of-buffer]
C-h l [view-lossage]
This is much better than the old version which
looked like a jungle. Not speaking literally,
that is!
To make it even clearer, why don't you consider
putting the command name in a column of its
own? This would also make the brackets
redundant. Also, isn't, e.g. M-o more used than
"ESC o", both in speech/writing _and_ in code -
and isn't it more intuitive as well? I.e.,
wouldn't this be even better - and improvement
on the improvement, if you will?
k next-line
i previous-line
k next-line
RET buffer-menu-kill-and-open
C-j e . anonymous-command
M-o other-window-or-split
M-o other-window-or-split
M-o other-window-or-split
M-p delete-other-windows
C-o k end-of-buffer
C-h l view-lossage
I think so!
--
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal
- improvements to the "lossage buffer",
Emanuel Berg <=
- Re: improvements to the "lossage buffer", Stefan Monnier, 2019/07/30
- Re: improvements to the "lossage buffer", Emanuel Berg, 2019/07/30
- Re: improvements to the "lossage buffer", Emanuel Berg, 2019/07/30
- Re: improvements to the "lossage buffer", Marcin Borkowski, 2019/07/31
- Re: improvements to the "lossage buffer", Emanuel Berg, 2019/07/31
- Re: improvements to the "lossage buffer", Marcin Borkowski, 2019/07/31
- Re: improvements to the "lossage buffer", Emanuel Berg, 2019/07/31
- Re: improvements to the "lossage buffer", Marcin Borkowski, 2019/07/31
- Re: improvements to the "lossage buffer", Dan Sommers, 2019/07/31
- Re: improvements to the "lossage buffer", Marcin Borkowski, 2019/07/31