unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: larsi@gnus.org, rgm@gnu.org, p.stephani2@gmail.com,
	53316@debbugs.gnu.org
Subject: bug#53316: 28.0.91; Missing Transient manual in Emacs
Date: Fri, 25 Feb 2022 00:00:44 -0500	[thread overview]
Message-ID: <E1nNSii-0006Tr-4Q@fencepost.gnu.org> (raw)
In-Reply-To: <875yp5epy2.fsf@bernoul.li> (message from Jonas Bernoulli on Wed,  23 Feb 2022 13:18:45 +0100)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > The exporter currently can do this and similar:
  >   =code=    =>    @code{code}
  > once I am done it will be able to optionally do this and similar:
  >   $var$     =>    @var{var}

That syntax is convenient to use, but hard to extend to cover all the
Texinfo markup facilities.  There are LOTS of them.

  > Being asked for a spec is annoying, and so is the assumption that I
  > won't do the work.

Please don't take it personally.  It's not about you.  Designing the
interface is the hardest part of this, and other efforts have ended
up in a dead end.

What's hard is finding syntax for so many markup constructs.
I don't think the simple approach with one punctuation character
can handle it.  Also, Texinfo markup constructs nest.

I have seen systems inspired by markdown that were meant to be used
for manuals.  Each one handled only a subset of the jobs that Texinfo
markup constructs do.  The markup approach is so limiting that it
doesn't offer much room for syntax for a greater number of constructs.

I've found that people tend to implement a subset, and it is easy to
find usable syntax for a small number of constructs.  But there is no
natural way to extend it to do the whole job.  In effect, doing this
for a subset "first", expecting to add the others later, means a risk
of ending up in a dead end.

I'm sure you will finish this job, if you start with a plan for
handling all the markup constructs.

Have you got a list of Texinfo constructs to support?

If there is no way Org format can handle the repertoire of constructs
that we want for our manuals, we should not use Org format for the
source for a manual.  We should use Texinfo format.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)







  reply	other threads:[~2022-02-25  5:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17 13:07 bug#53316: 28.0.91; Missing Transient manual in Emacs Philipp Stephani
2022-01-21 11:29 ` Lars Ingebrigtsen
2022-01-25 20:30   ` Jonas Bernoulli
2022-01-25 20:41     ` Philipp Stephani
2022-01-25 21:15       ` Jonas Bernoulli
2022-02-15 16:57         ` Jonas Bernoulli
2022-01-26  9:08     ` Michael Albinus
2022-02-15 16:53   ` Jonas Bernoulli
2022-02-15 19:09     ` Eli Zaretskii
2022-02-15 21:39       ` Jonas Bernoulli
2022-02-16  3:25         ` Eli Zaretskii
2022-02-15 20:17     ` Glenn Morris
2022-02-15 21:46       ` Jonas Bernoulli
2022-02-16 21:09         ` Glenn Morris
2022-02-17  6:23           ` Eli Zaretskii
2022-02-19  4:57             ` Richard Stallman
2022-02-19  8:46               ` Eli Zaretskii
2022-02-21  4:34                 ` Richard Stallman
2022-02-21  5:47                   ` Eli Zaretskii
2022-02-23  6:45                     ` Richard Stallman
2022-02-23 12:18                       ` Jonas Bernoulli
2022-02-25  5:00                         ` Richard Stallman [this message]
2022-02-23 12:45                       ` Eli Zaretskii
2022-02-19  9:27               ` Glenn Morris

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=E1nNSii-0006Tr-4Q@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=53316@debbugs.gnu.org \
    --cc=jonas@bernoul.li \
    --cc=larsi@gnus.org \
    --cc=p.stephani2@gmail.com \
    --cc=rgm@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).