unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jose A Ortega Ruiz <jao@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58131@debbugs.gnu.org
Subject: bug#58131: [PATCH] docview: new customization options for imenu
Date: Wed, 28 Sep 2022 16:55:56 +0100	[thread overview]
Message-ID: <874jwr7asz.fsf@mail.jao.io> (raw)
In-Reply-To: <83bkqzijmh.fsf@gnu.org>

On Wed, Sep 28 2022, Eli Zaretskii wrote:

[...]

> Think about the various Help commands, such as 'apropos': they show
> the doc strings or just their first sentence entirely out of any
> context.  Users who invoke such commands should be capable to
> understand at a glance whether the command/variable is something they
> should examine further.  So having important keywords in there helps
> immensely to make such triage steps much faster and more efficient.

Excellent point, thanks.

[...]

>> Any better?
>
> Yes, thanks.  My suggestion is a very minor variation of the latter:
>
>  Format spec for imenu's display of section titles from docview documents.

Looks good to me.  Would you like a patch with the two new strings or is
it quicker if you directly commit a change by yourself?


Cheers,
jao
-- 
All parts should go together without forcing. You must remember that
the parts you are reassembling were disassembled by you. Therefore, if
you can’t get them together again, there must be a reason. By all
means, do not use a hammer. —IBM Manual, 1925





  reply	other threads:[~2022-09-28 15:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28  2:21 bug#58131: [PATCH] docview: new customization options for imenu Jose A Ortega Ruiz
2022-09-28 11:08 ` Lars Ingebrigtsen
2022-09-28 12:34 ` Eli Zaretskii
2022-09-28 14:05   ` Jose A Ortega Ruiz
2022-09-28 14:25     ` Eli Zaretskii
2022-09-28 15:14       ` Jose A Ortega Ruiz
2022-09-28 15:49         ` Eli Zaretskii
2022-09-28 15:55           ` Jose A Ortega Ruiz [this message]
2022-09-28 16:01             ` Eli Zaretskii

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=874jwr7asz.fsf@mail.jao.io \
    --to=jao@gnu.org \
    --cc=58131@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).