From: Eli Zaretskii <eliz@gnu.org>
To: Jeremy Bryant <jb@jeremybryant.net>
Cc: rms@gnu.org, emacs-devel@gnu.org, philipk@posteo.net,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: [ELPA] New package c-intro-and-ref -- was Re: Proposal: Include C Manual from RMS in Emacs git, and/or release
Date: Wed, 04 Dec 2024 14:33:29 +0200 [thread overview]
Message-ID: <86a5db1vc6.fsf@gnu.org> (raw)
In-Reply-To: <87bjxsbc8h.fsf@jeremybryant.net> (message from Jeremy Bryant on Tue, 03 Dec 2024 23:03:42 +0000)
> From: Jeremy Bryant <jb@jeremybryant.net>
> Cc: rms@gnu.org, emacs-devel@gnu.org, Philip Kaludercic <philipk@posteo.net>
> Date: Tue, 03 Dec 2024 23:03:42 +0000
>
> I have created a prototype ELPA package, comments welcome?
Are we providing packages that include only Info manuals, which
document stuff that is not specific to Emacs? Because I don't see how
it would be a good idea to have this as an ELPA package.
But if we do accept such packages on ELPA, then I have 2 additional
similar suggestions:
. Git manual in Info format
. Python 3 manual in Info format
> Current Package name, proposed for ELPA: c-intro-and-ref
> This matches the existing manual distribution.
> Perhaps a name such as: gnu-c-manual
That'd be wrong, since this manual doesn't describe GNU C, it
describes the C language in general. (There's a separate GNU C
manual, btw.)
next prev parent reply other threads:[~2024-12-04 12:33 UTC|newest]
Thread overview: 30+ 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
2024-12-03 2:51 ` Texinfo reputation Max Nikulin
2024-12-03 12:38 ` Eli Zaretskii
2024-12-03 18:51 ` Dr. Arne Babenhauserheide
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-12-04 6:09 ` Richard Stallman
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
2024-12-03 23:03 ` [ELPA] New package c-intro-and-ref -- was " Jeremy Bryant
2024-12-04 12:33 ` Eli Zaretskii [this message]
2024-12-04 22:58 ` Jeremy Bryant
2024-12-03 20:07 ` Björn Bidar
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=86a5db1vc6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jb@jeremybryant.net \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
--cc=rms@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).