From: Protesilaos Stavrou <info@protesilaos.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rgm@gnu.org, 45143@debbugs.gnu.org, rms@gnu.org
Subject: bug#45143: Incorrect markup in some doc/misc manuals
Date: Thu, 25 Feb 2021 08:04:23 +0200 [thread overview]
Message-ID: <87mtvsn0ns.fsf@protesilaos.com> (raw)
In-Reply-To: <83lfbdts6y.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 24 Feb 2021 17:13:09 +0200")
On 2021-02-24, 17:13 +0200, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Protesilaos Stavrou <info@protesilaos.com>
>> Date: Wed, 24 Feb 2021 09:38:23 +0200
>> Cc: rgm@gnu.org, 45143@debbugs.gnu.org, Richard Stallman <rms@gnu.org>
>>
>> After reading through the discussion[1] on using Org for Emacs manuals,
>> I have managed to make some changes to the modus-themes.org file which
>> generates modus-themes.texi.
>>
>> You can inspect the source code with:
>>
>> git clone https://gitlab.com/protesilaos/modus-themes.git
>>
>> Documentation is stored in the repo's "doc" directory.
>>
>> The changes pertain to the appropriate use of Texinfo markup such as
>> 'kbd', 'code', and 'file'. Furthermore, the modus-themes.texi file is
>> now distributed as part of the source code, whereas before I was only
>> sharing the modus-themes.org and its derived modus-themes.info.
>>
>> Those improvements will be made available for the forthcoming version
>> 1.2.0 of the Modus themes (expected within the next few days). Core
>> Emacs currently ships with the themes' 0.13.0 version, which will soon
>> be three releases behind.
>
> Thanks, but please also submit those improvements to Org's Texinfo
> export to the Org developers, so that other manuals written in org
> could also benefit from this improved Texinfo support.
Yes, sure! I will go through the Org manual and check what can be done.
Though I think Richard's and Glenn's original point was that the Org
project uses the ".org" file as its original source in its own git
repository ("org-manual.org"), whereas it distributes ".texi" with
emacs.git ("org.texi")---so what is in core Emacs is technically not the
original source.
That was the issue with my themes and is why I am now sharing the
".texi" in addition to the ".org". If I notice any further
inconsistencies, I will address them.
--
Protesilaos Stavrou
protesilaos.com
next prev parent reply other threads:[~2021-02-25 6:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 17:41 bug#45143: Missing source for some doc/misc manuals? Glenn Morris
2020-12-15 18:17 ` Glenn Morris
2021-01-31 21:47 ` Glenn Morris
2021-02-17 5:40 ` bug#45143: Missing source for some doc/misc manuals (moral-issue) Glenn Morris
2021-02-17 8:45 ` Robert Pluim
2021-02-17 14:27 ` Basil L. Contovounesios
2021-02-17 14:41 ` Robert Pluim
2021-02-17 16:09 ` Eli Zaretskii
2021-02-17 16:15 ` Robert Pluim
2021-02-17 17:28 ` Eli Zaretskii
2021-02-19 5:34 ` Richard Stallman
2021-02-19 5:57 ` Glenn Morris
2021-02-21 6:15 ` Richard Stallman
2021-02-21 6:15 ` bug#45143: Incorrect markup in some doc/misc manuals Richard Stallman
2021-02-21 11:01 ` Protesilaos Stavrou
2021-02-22 6:22 ` Richard Stallman
2021-02-22 16:38 ` Protesilaos Stavrou
2021-02-24 7:38 ` Protesilaos Stavrou
2021-02-24 15:13 ` Eli Zaretskii
2021-02-25 6:04 ` Protesilaos Stavrou [this message]
2021-02-25 14:40 ` Eli Zaretskii
2021-02-27 3:49 ` Glenn Morris
2021-02-27 3:55 ` Glenn Morris
2021-02-27 6:29 ` Protesilaos Stavrou
2021-02-21 20:11 ` Eli Zaretskii
2021-02-24 6:49 ` Richard Stallman
2021-02-24 15:09 ` Eli Zaretskii
2021-02-26 6:32 ` Richard Stallman
2021-02-26 7:45 ` Eli Zaretskii
2021-02-27 16:14 ` Richard Stallman
2021-02-27 18:20 ` Eli Zaretskii
2021-03-01 5:18 ` 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=87mtvsn0ns.fsf@protesilaos.com \
--to=info@protesilaos.com \
--cc=45143@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rgm@gnu.org \
--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).