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

> From: Max Nikulin <manikulin@gmail.com>
> Date: Mon, 2 Dec 2024 10:00:56 +0700
> 
> Those who read .info documents may recommend e.g. pinfo. From my point 
> of view, tkinfo is usually better than "info".

Are they being developed?  ISTR that someone said they were no longer
updated.



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

Thread overview: 22+ 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             ` Texinfo reputation (was: Re: [External] : Re: Proposal: Include C Manual from RMS in Emacs git, and/or release) Max Nikulin
2024-12-02 12:47               ` Eli Zaretskii [this message]
2024-12-01  9:53         ` Proposal: Include C Manual from RMS in Emacs git, and/or release 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
2024-12-02 12:57     ` Eli Zaretskii

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=86frn645fn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=manikulin@gmail.com \
    /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).