From: Stefan Kangas <stefan@marxist.se>
To: Drew Adams <drew.adams@oracle.com>
Cc: Glenn Morris <rgm@gnu.org>,
Richard Stanton <stanton@haas.berkeley.edu>,
11168@debbugs.gnu.org
Subject: bug#11168: All headers but one missing in main *Info* buffer
Date: Thu, 29 Oct 2020 18:06:04 -0700 [thread overview]
Message-ID: <CADwFkmndi30iH8A7cXirQULMVHXPZR1qafzZu3k8NVMRwLxjcQ@mail.gmail.com> (raw)
In-Reply-To: <8b2084db-5465-4d6d-b2ae-6e9c2ac91cc7@default>
Drew Adams <drew.adams@oracle.com> writes:
>> > 2. `Info-streamline-headings' should be a user option, not a defvar.
>>
>> I'm not sure that this is something that people will commonly want to
>> customize.
>
> Why not? (And why must an option be something that's
> _commonly_ modified by users?)
I just don't think it's all that useful.
> In this bug report you have a user asking about the
> format/content of Info, with no way to find out about
> what's happening, without filing a bug.
But that was because there had just been a change, many moons ago.
Right? Or have we seen many questions since?
IMO, Info-streamline-headings is fine for what it's trying to do, which
AFAICT is mainly to consolidate all Emacs stuff under one heading.
But it seems to me that the GNU project/Info or whoever should rather
make sure that the organization of headlines makes sense. It seems
pretty chaotic on my machine, and different projects seem to follow
various different conventions. So I'd personally rather users filed bug
reports to the respective projects, or to makeinfo, or against the GNU
coding standards or something.
next prev parent reply other threads:[~2020-10-30 1:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 7:13 bug#11168: All headers but one missing in main *Info* buffer Richard Stanton
2012-04-04 7:48 ` Glenn Morris
2012-04-04 13:16 ` Drew Adams
2020-10-29 18:47 ` Stefan Kangas
2020-10-29 19:34 ` Drew Adams
2020-10-30 1:06 ` Stefan Kangas [this message]
2020-11-25 10:24 ` Stefan Kangas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmndi30iH8A7cXirQULMVHXPZR1qafzZu3k8NVMRwLxjcQ@mail.gmail.com \
--to=stefan@marxist.se \
--cc=11168@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=rgm@gnu.org \
--cc=stanton@haas.berkeley.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.