unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 50467@debbugs.gnu.org
Subject: bug#50467: Could :properties have index entries in the elisp manual?
Date: Wed, 08 Sep 2021 09:31:53 +0300	[thread overview]
Message-ID: <83k0jro9wm.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkkta5ZD6wxUu3EhVmko2KakYwW_n7qA8jqRAYv_NqF+w@mail.gmail.com> (message from Stefan Kangas on Wed, 8 Sep 2021 03:52:34 +0200)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Wed, 8 Sep 2021 03:52:34 +0200
> 
> 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.

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

One problem here is that use of the colon character in index entries
should be avoided, as some Info readers could get confused by that
(the colon is a special character in Info file format).

Also, most of the keywords are, or should be, found by using their
"family name".  For example, for faces we have "face attributes" in
the index.

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

Thanks.





  parent reply	other threads:[~2021-09-08  6:31 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 [this message]
2021-09-08 15:55   ` bug#50467: [External] : " Drew Adams
2021-09-10  6:54   ` Stefan Kangas
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=83k0jro9wm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=50467@debbugs.gnu.org \
    --cc=stefan@marxist.se \
    /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).