From: Leo Butler <leo.butler@umanitoba.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: info-emacs-manual?
Date: Fri, 04 Feb 2022 14:36:11 -0600 [thread overview]
Message-ID: <87zgn6tlms.fsf@t14.reltub.ca> (raw)
In-Reply-To: <8735kyh78h.fsf@zoho.eu> (Emanuel Berg via Users list for the's message of "Fri, 4 Feb 2022 18:27:58 +0100")
Emanuel Berg via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org> writes:
> Jean Louis wrote:
>
>>> After an
>>> apt-get update && apt-get dist-upgrade
>>
>> Sounds like Debian GNU/Linux. They have an issue with some
>> information in that manual, if I remember well they did not
>> accept some verbatim opinions in the manual and thus have
>> sorted it under non-free packages.
True, but irrelevant, since I have the manual installed.
>
> You are right:
>
> https://emacs.stackexchange.com/questions/48211/emacs-manuals-are-missing-on-debian-ubuntu
>
> But install from source then and get the opt-in-free manual :)
>
> This I do on Debian 11, to get GNU Emacs 29:
>
> https://dataswamp.org/~incal/conf/.zsh/install-emacs
Interesting, but irrelevant. As I wrote, I can get to the emacs manual
(installed from the debian repo) using
M-x info-emacs-manual RET
Ok, I will file a bug report against the debian package unless someone
tells me otherwise.
Leo
next prev parent reply other threads:[~2022-02-04 20:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 15:43 info-emacs-manual? Leo Butler
2022-02-04 15:57 ` info-emacs-manual? Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-04 16:46 ` info-emacs-manual? Jean Louis
2022-02-04 17:27 ` info-emacs-manual? Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-04 17:48 ` info-emacs-manual? Jean Louis
2022-02-04 20:07 ` info-emacs-manual? Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-04 20:36 ` Leo Butler [this message]
2022-02-05 7:09 ` info-emacs-manual? 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=87zgn6tlms.fsf@t14.reltub.ca \
--to=leo.butler@umanitoba.ca \
--cc=help-gnu-emacs@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.
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).