unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: 45143@debbugs.gnu.org
Subject: bug#45143: Incorrect markup in some doc/misc manuals
Date: Wed, 24 Feb 2021 17:09:58 +0200	[thread overview]
Message-ID: <83mtvttsc9.fsf@gnu.org> (raw)
In-Reply-To: <E1lEnzF-0003nB-KD@fencepost.gnu.org> (message from Richard Stallman on Wed, 24 Feb 2021 01:49:29 -0500)

> From: Richard Stallman <rms@gnu.org>
> Cc: 45143@debbugs.gnu.org
> Date: Wed, 24 Feb 2021 01:49:29 -0500
> 
>   > I think this is because Org has some problems in supporting some of
>   > the key Texinfo markups, such as @kbd.
> 
> You are surely right that that is why the problem exists,
> but it still needs to be fixed.

Of course, no argument here.  My point is that until the Org's Texinfo
export is fixed so that it produces better Texinfo, these problems
will be inevitable.  The issues described and discussed in that past
thread were not fixed, AFAIK.





  reply	other threads:[~2021-02-24 15:09 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
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 [this message]
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=83mtvttsc9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=45143@debbugs.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).