From: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Morgan Smith <Morgan.J.Smith@outlook.com>
Cc: 75143@debbugs.gnu.org
Subject: bug#75143: debbugs info manual name
Date: Fri, 27 Dec 2024 18:10:16 +0100 [thread overview]
Message-ID: <87cyhd6ohz.fsf@gmx.de> (raw)
In-Reply-To: <CH3PR84MB3424068D214C8E11FA0D2A6FC50E2@CH3PR84MB3424.NAMPRD84.PROD.OUTLOOK.COM> (Morgan Smith's message of "Fri, 27 Dec 2024 10:16:48 -0500")
Morgan Smith <Morgan.J.Smith@outlook.com> writes:
> Hello!
Hi Morgan,
> I wanted to make a quick suggestion on the debbugs info manuals names.
> I think we should name the user manual "debbugs" and the programmer
> manual "debbugs-programmer-manual" (NOT "debbugs-pm").
>
> Currently the info manual is called: debbugs-ug.info
> The programmer info manual is called: debbugs.info
>
> This means people typing "info debbugs" will get the programmer info
> manual, not the user info manual.
>
> When I was first starting to use debbugs I skimmed the programmer info
> manual accidentally and got quite confused trying to find the
> information I wanted. I ran "info debbugs" and opened the section
> "searching bugs" hoping to find the user commands, not elisp ones.
>
> The programmer manual does mention the user manual but as I was skimming
> for something specific, not reading it carefully, I missed that.
Although I understand your reasons, I'm not convinced that this is worth
the trouble. The manuals exist for 13 years (debbugs.texi) and 10 years
(debbugs-ug.texi). It night confuse prople, if we rename them.
Furthermore, there are references to both manuals from outside. Those
references would be broken.
> Thanks,
>
> Morgan
Best regards, Michael.
next prev parent reply other threads:[~2024-12-27 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-27 15:16 bug#75143: debbugs info manual name Morgan Smith
2024-12-27 17:10 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-12-27 17:56 ` Morgan Smith
2024-12-28 11:32 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87cyhd6ohz.fsf@gmx.de \
--to=bug-gnu-emacs@gnu.org \
--cc=75143@debbugs.gnu.org \
--cc=Morgan.J.Smith@outlook.com \
--cc=michael.albinus@gmx.de \
/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.