From: Protesilaos Stavrou <info@protesilaos.com>
To: emacs-devel@gnu.org
Cc: Karl Fogel <kfogel@red-bean.com>
Subject: Re: Improving documentation of Org Mode integration into Emacs.
Date: Mon, 03 Jan 2022 14:06:02 +0200 [thread overview]
Message-ID: <87zgodkor9.fsf@protesilaos.com> (raw)
In-Reply-To: <87fsq5tnni.fsf@red-bean.com>
On 2022-01-02, 23:05 -0600, Karl Fogel <kfogel@red-bean.com> wrote:
> +Each externally maintained package lives in its own subdirectory in
> +the Emacs tree, and that subdirectory should have a "README" file that
> +describes the upstream origin. For example, "lisp/org/README" says
> +where the Org Mode project lives and how it's synchronized into Emacs.
> +
> +Note that not all the independently-maintained packages in Emacs have
> +such a "README" yet. If you know of one that's missing its "README",
> +please send in a patch or just let us know.
The modus-themes are maintained externally. I sync them with emacs.git
every month or so when I release a new version. Their .el files are in
etc/themes/ while the manual is in doc/misc/.
I am happy to provide a README, though neither of those two directories
is specific to the modus-themes.
Maybe I should include the relevant information in the themes' manual
and/or the "Commentary:" of each .el file?
--
Protesilaos Stavrou
https://protesilaos.com
next prev parent reply other threads:[~2022-01-03 12:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 21:14 Improving documentation of Org Mode integration into Emacs Karl Fogel
2021-12-04 21:18 ` Karl Fogel
2021-12-04 22:09 ` [External] : " Drew Adams
2021-12-05 5:16 ` Stefan Monnier
2021-12-05 6:38 ` Eli Zaretskii
2022-01-03 5:05 ` Karl Fogel
2022-01-03 5:44 ` Stefan Monnier
2022-01-05 3:09 ` Karl Fogel
2022-01-05 13:48 ` Eli Zaretskii
2022-01-05 14:17 ` Michael Albinus
2022-01-05 14:26 ` Eli Zaretskii
2022-01-06 12:40 ` Michael Albinus
2022-01-06 13:58 ` Eli Zaretskii
2022-01-07 10:41 ` Protesilaos Stavrou
2022-01-09 22:34 ` Karl Fogel
2022-01-10 8:46 ` Michael Albinus
2022-01-10 9:03 ` Michael Albinus
2022-01-10 9:13 ` Karl Fogel
2022-01-10 9:17 ` Michael Albinus
2022-01-10 11:01 ` Robert Pluim
2022-01-10 16:10 ` Karl Fogel
2022-01-10 9:06 ` Karl Fogel
2022-01-10 9:24 ` Michael Albinus
2022-01-10 16:20 ` Karl Fogel
2022-01-10 18:24 ` Eli Zaretskii
2022-01-11 7:49 ` Michael Albinus
2022-01-10 18:14 ` Eli Zaretskii
2022-01-10 19:08 ` Karl Fogel
2022-01-03 8:52 ` Michael Albinus
2022-01-03 12:06 ` Protesilaos Stavrou [this message]
2022-01-03 13:31 ` Eli Zaretskii
2022-01-03 20:45 ` Rudolf Adamkovič
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=87zgodkor9.fsf@protesilaos.com \
--to=info@protesilaos.com \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.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).