unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-devel@gnu.org
Subject: Texinfo reputation (was: Re: [External] : Re: Proposal: Include C Manual from RMS in Emacs git, and/or release)
Date: Mon, 2 Dec 2024 10:00:56 +0700	[thread overview]
Message-ID: <vij7tc$115b$1@ciao.gmane.io> (raw)
In-Reply-To: <861pys6i8z.fsf@gnu.org>

On 01/12/2024 13:15, Eli Zaretskii wrote:
> My evidence is that when people report problems with GNU manuals, they
> almost always show a URL of the HTML documentation.

I would include an http(s): link into an issue report to avoid ugly 
multistep style of addressing info nodes as in

> emacs --help
[...]
> Run M-x info RET m emacs RET m emacs invocation RET inside Emacs to
> read the main documentation for these command-line arguments.

and to allow people reading the message from a mobile device to easily 
inspect the actual text. That is why I consider URLs in reports as a 
weak evidence. Side note: likely I would duplicate the reference as 
(info "(emacs) Emacs Invocation").

My impression based on debian-user mailing list messages is that people 
avoid info manuals due to inconvenience of the standalone reader. They 
have some workarounds for cases when length of a man page is excessively 
high for comfortable reading. An example is PDF generated from BASH man 
page despite BASH has the manual in the texinfo format.

Those who read .info documents may recommend e.g. pinfo. From my point 
of view, tkinfo is usually better than "info".

Another issue is that there is no standard way to share a link to a 
specific node of a texinfo document. khelpcenter and yelp use different 
URL schemes for this purpose. It may not be easy to get link to the 
currently displayed node and that style of links would not be helpful 
for Emacs or standalone info browsers.

Debian 12 bookworm: "emacs -f info-standalone" option is not included into

update-alternatives --list infobrowser
/usr/bin/info
/usr/bin/tkinfo

Feel free to forward this message to a texinfo mailing list. Another 
reason why I have decided to post it here is the following message:

On 30/11/2024 21:12, Eli Zaretskii wrote:
> Texinfo comes with info-stnd.info,
> which documents the stand-alone reader, which is part of Texinfo.
> 
> So I don't see how that move could damage the reputation of Texinfo.
> 
> Do you have any information to suggest that many people use the
> stand-alone reader?




  reply	other threads:[~2024-12-02  3:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-30 12:56 Proposal: Include C Manual from RMS in Emacs git, and/or release Jeremy Bryant
2024-11-30 13:25 ` Philip Kaludercic
2024-11-30 13:38 ` Arsen Arsenović
2024-11-30 14:12   ` Eli Zaretskii
2024-11-30 18:08     ` Arsen Arsenović
2024-11-30 20:05       ` Eli Zaretskii
2024-11-30 21:09         ` [External] : " Drew Adams
2024-12-01  6:15           ` Eli Zaretskii
2024-12-02  3:00             ` Max Nikulin [this message]
2024-12-01  9:53         ` Arsen Arsenović
2024-12-01 10:12           ` Eli Zaretskii
2024-12-01 10:54             ` Arsen Arsenović
2024-12-01 13:04         ` Johan Myréen
2024-11-30 13:50 ` Eli Zaretskii
2024-12-01  4:02   ` Sean Whitton
2024-12-01  7:45     ` Eli Zaretskii
2024-12-01  8:36       ` Sean Whitton
2024-12-01 10:01         ` Eli Zaretskii
2024-12-01 11:13           ` Sean Whitton
2024-12-02  4:10   ` Richard Stallman

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='vij7tc$115b$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --cc=emacs-devel@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).