unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: "T.V Raman" <raman@google.com>
Cc: Robert Pluim <rpluim@gmail.com>,  emacs-devel@gnu.org
Subject: Re: describe-repeat-maps: Possible print bug:
Date: Thu, 17 Nov 2022 19:55:10 +0200	[thread overview]
Message-ID: <8635ahwjnl.fsf@mail.linkov.net> (raw)
In-Reply-To: <p91fsehbnl7.fsf@google.com> (T. V. Raman's message of "Thu, 17 Nov 2022 07:35:48 -0800")

> One more nit:
>
> If you have a repeat command with many entry points, the help buffer
> displays them all on one line-- see pathological example below:
>
> Entered with: ‘emacspeak-media-mp3’, ‘emacspeak-media-38-dc-books’,
> ‘emacspeak-m-player-loop’, ‘emacspeak-media-brain-sync’,
> ‘emacspeak-multimedia’, ‘emacspeak-m-player-youtube-live’,
> ‘emacspeak-media-devotional’, ‘emacspeak-media-classical’,
> ‘emacspeak-m-player-shuffle’, ‘emacspeak-eww-play-media-at-point’,
> ‘emacspeak-media-pop’, ‘emacspeak-media-indian’,
> ‘emacspeak-m-player-using-openal’

Thanks for noticing this, I haven't tested with so long lines.
Now fixed by filling lines as a paragraph.



  reply	other threads:[~2022-11-17 17:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28  2:36 describe-repeat-maps: Possible print bug: T.V Raman
2022-09-28 17:55 ` Juri Linkov
2022-09-29  2:14   ` T.V Raman
2022-09-29  6:47     ` Juri Linkov
2022-09-29 14:00       ` T.V Raman
2022-11-15 18:41       ` Juri Linkov
2022-11-16 23:15         ` T.V Raman
2022-11-17  7:31           ` Juri Linkov
2022-11-17 15:19             ` T.V Raman
2022-11-17 15:35               ` T.V Raman
2022-11-17 17:55                 ` Juri Linkov [this message]
2022-11-17 18:26                   ` T.V Raman
2022-11-17 18:49                     ` Juri Linkov
2022-11-17 20:52           ` T.V Raman
2022-11-18  7:20             ` Juri Linkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8635ahwjnl.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=emacs-devel@gnu.org \
    --cc=raman@google.com \
    --cc=rpluim@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).