unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: 60930@debbugs.gnu.org
Subject: bug#60930: 30.0.50; 24.3 Choosing File Modes section of Emacs manual does not explain dealing with backup files
Date: Fri, 20 Jan 2023 15:50:46 +0200	[thread overview]
Message-ID: <83v8l1mi15.fsf@gnu.org> (raw)
In-Reply-To: <87zgadqqq7.fsf@localhost> (message from Ihor Radchenko on Fri, 20 Jan 2023 13:29:20 +0000)

> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: 60930@debbugs.gnu.org
> Date: Fri, 20 Jan 2023 13:29:20 +0000
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > P.S.  I'm not sure index entries will help discoverability (you need
> > to know what you are looking for to type an index entry), but adding
> > indexing can never do any harm.
> 
> I just need keywords. Most often, I invoke helm-info and search by index
> (`Info-index-nodes'). Word ordering in the index does not matter for me
> because of how helm matches candidates.

We cannot possibly write index entries on the assumption that they
will only be used through helm.  The main client of index entries is
info.el.





  reply	other threads:[~2023-01-20 13:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 10:58 bug#60930: 30.0.50; 24.3 Choosing File Modes section of Emacs manual does not explain dealing with backup files Ihor Radchenko
2023-01-18 14:06 ` Eli Zaretskii
2023-01-19 11:36   ` Ihor Radchenko
2023-01-19 13:28     ` Eli Zaretskii
2023-01-19 13:35       ` Ihor Radchenko
2023-01-19 14:17         ` Eli Zaretskii
2023-01-20 13:29           ` Ihor Radchenko
2023-01-20 13:50             ` Eli Zaretskii [this message]
2023-01-21  9:39               ` Ihor Radchenko
2023-01-21  9:55                 ` Eli Zaretskii
2023-01-21 10:08                   ` Ihor Radchenko
2023-01-21 11:36                     ` Eli Zaretskii
2023-01-21 13:34                       ` Ihor Radchenko

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=83v8l1mi15.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=60930@debbugs.gnu.org \
    --cc=yantar92@posteo.net \
    /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).