* bug#64496: describe-key vs. view-lossage
@ 2023-07-06 13:54 Dan Jacobson
2023-07-06 14:52 ` Eli Zaretskii
0 siblings, 1 reply; 2+ messages in thread
From: Dan Jacobson @ 2023-07-06 13:54 UTC (permalink / raw)
To: 64496
a ;; self-insert-command
b ;; self-insert-command
c ;; self-insert-command
C-h k ;; describe-key
<up> C-x b ;; switch-to-buffer
<return> ;; minibuffer-complete-and-exit
C-h l ;; view-lossage
Above, the <up> should not be put on the same line. It just doesn't make
sense. If it must be on the same line, put it on the back of the
previous line.
emacs-version "28.2"
^ permalink raw reply [flat|nested] 2+ messages in thread
* bug#64496: describe-key vs. view-lossage
2023-07-06 13:54 bug#64496: describe-key vs. view-lossage Dan Jacobson
@ 2023-07-06 14:52 ` Eli Zaretskii
0 siblings, 0 replies; 2+ messages in thread
From: Eli Zaretskii @ 2023-07-06 14:52 UTC (permalink / raw)
To: Dan Jacobson; +Cc: 64496
tags 64496 wontfix
close 64496
thanks
> From: Dan Jacobson <jidanni@jidanni.org>
> Date: Thu, 06 Jul 2023 08:54:17 -0500
>
> a ;; self-insert-command
> b ;; self-insert-command
> c ;; self-insert-command
> C-h k ;; describe-key
> <up> C-x b ;; switch-to-buffer
> <return> ;; minibuffer-complete-and-exit
> C-h l ;; view-lossage
>
> Above, the <up> should not be put on the same line. It just doesn't make
> sense. If it must be on the same line, put it on the back of the
> previous line.
I see no reason to do anything about this.
Closing.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-07-06 14:52 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-07-06 13:54 bug#64496: describe-key vs. view-lossage Dan Jacobson
2023-07-06 14:52 ` Eli Zaretskii
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).