unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 50467@debbugs.gnu.org
Subject: bug#50467: Could :properties have index entries in the elisp manual?
Date: Fri, 10 Sep 2021 08:54:34 +0200	[thread overview]
Message-ID: <CADwFkmmGe=NG4Y3jLqyucTLVpe-fVz5g8bytvLTLX6SM+KSx7g@mail.gmail.com> (raw)
In-Reply-To: <83k0jro9wm.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

> > Please consider adding properties to the index of the elisp manual for
> > easy access.
>
> Which ones? all of them?  There are a lot of them, and we sometimes
> have the same keyword used in different contexts to mean different
> things, so we'd need a lot of disambiguation text to make unique
> entries.

As a first approximation, only some of them.

(That's what I meant when I wrote: "Perhaps some properties are more
important to add than others, and perhaps others still would not even
make sense adding.")

> (And you mean keywords that start with a colon, not properties.
> Right?)

Yes, that was a thinko, sorry.

> That said, feel free to suggest additions to the indexing for the
> important keywords, we can always discuss them one by one.

That seems like a good approach here.





  parent reply	other threads:[~2021-09-10  6:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-08  1:52 bug#50467: Could :properties have index entries in the elisp manual? Stefan Kangas
2021-09-08  5:51 ` Lars Ingebrigtsen
2021-09-08  6:31 ` Eli Zaretskii
2021-09-08 15:55   ` bug#50467: [External] : " Drew Adams
2021-09-10  6:54   ` Stefan Kangas [this message]
2021-09-10  7:00   ` Stefan Kangas
2021-09-10  7:14     ` Eli Zaretskii
2022-08-25 14:26       ` Lars Ingebrigtsen

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='CADwFkmmGe=NG4Y3jLqyucTLVpe-fVz5g8bytvLTLX6SM+KSx7g@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=50467@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).