From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: Richard Stallman <rms@gnu.org>
Cc: eliz@gnu.org, jimjoe@gmx.net, emacs-devel@gnu.org
Subject: Re: Integration of Info manuals in programming modes, Re: Integration of Info manuals in programming modes
Date: Sat, 14 Dec 2024 01:54:22 +0200 [thread overview]
Message-ID: <25509.9579271459$1734134126@news.gmane.org> (raw)
In-Reply-To: <E1tLEOu-0000WZ-6P@fencepost.gnu.org> (Richard Stallman's message of "Tue, 10 Dec 2024 23:32:40 -0500")
Richard Stallman <rms@gnu.org> writes:
> [[[ 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. ]]]
>
> > That's a good idea. I want to add to context that Sphinx plugins can
> > break the Info output entirely.
>
> Could you please say what changes you have in mind for Sphinx?
I'm not entirely sure but from what I have read it does appear like that
plugins can break the output by inserting their generated markup in
between a block which then causes for example syntax errors.
It's kinda like this (pseudo code)
@toc
toc items here
plugin inserts their markup but forgets and @end somewhere.
@end
The result is that the generated Texinfo contains formatting and or
syntax errors.
> I am interested in Sphinx because I think it could be developed into a
> superior replacement for Texinfo, by adding ways to specify the output
> style distinctions that Sphinx currently does not handle. But it
> would take some design work, not just simple programming.
I think both are different types of software one uses reStructuredText
as input format while the other (Texinfo) uses well Texinfo.
I'm not a (La)Tex user outside of writing a few documents here and there
but bringing Texinfo closer to Tex could be a good idea while keeping
the output format the same.
next prev parent reply other threads:[~2024-12-13 23:54 UTC|newest]
Thread overview: 100+ 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-05 4:56 ` Max Nikulin
2024-12-05 7:45 ` Dr. Arne Babenhauserheide
2024-12-06 4:47 ` Richard Stallman
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-05 5:05 ` Making the GNU C Manual easier to find in Info Richard Stallman
2024-12-05 6:30 ` Eli Zaretskii
2024-12-05 7:25 ` Integration of Info manuals in programming modes; was: " Dr. Arne Babenhauserheide
2024-12-05 7:46 ` Integration of Info manuals in programming modes Eli Zaretskii
2024-12-05 8:52 ` Visuwesh
2024-12-05 9:14 ` Eli Zaretskii
2024-12-05 9:49 ` Visuwesh
2024-12-05 11:17 ` Eli Zaretskii
2024-12-05 11:28 ` Visuwesh
2024-12-05 12:01 ` Eli Zaretskii
2024-12-05 12:39 ` Visuwesh
2024-12-05 14:26 ` Eli Zaretskii
2024-12-08 8:13 ` Integration of Info manuals in programming modes, " James Thomas
2024-12-08 8:38 ` James Thomas
2024-12-08 11:34 ` Eli Zaretskii
2024-12-08 20:10 ` Björn Bidar
[not found] ` <86msh5b48w.fsf@gmx.net>
2024-12-10 1:08 ` James Thomas
[not found] ` <87zfl60wbw.fsf@>
2024-12-08 20:46 ` Eli Zaretskii
2024-12-11 4:32 ` Richard Stallman
2024-12-13 23:54 ` Björn Bidar [this message]
2024-12-05 10:06 ` Stephen Berman
2024-12-05 15:07 ` Dr. Arne Babenhauserheide
2024-12-05 16:04 ` Eli Zaretskii
2024-12-09 4:58 ` Integration of Info manuals in programming modes; was: Making the GNU C Manual easier to find in Info Richard Stallman
2024-12-09 22:49 ` Dr. Arne Babenhauserheide
2024-12-11 4:35 ` Richard Stallman
2024-12-02 4:10 ` Proposal: Include C Manual from RMS in Emacs git, and/or release 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
2024-12-04 22:58 ` Jeremy Bryant
2024-12-05 5:45 ` Eli Zaretskii
2024-12-07 13:30 ` Improving info-look.el for (c) -was- " Jeremy Bryant
2024-12-07 15:09 ` Eli Zaretskii
2024-12-05 5:03 ` Max Nikulin
2024-12-05 18:47 ` Philip Kaludercic
2024-12-05 19:04 ` Eli Zaretskii
2024-12-06 10:44 ` Philip Kaludercic
2024-12-06 12:10 ` Eli Zaretskii
2024-12-06 22:40 ` Philip Kaludercic
2024-12-05 19:17 ` Stefan Monnier
2024-12-05 20:35 ` chad
2024-12-06 4:57 ` Visuwesh
2024-12-06 10:42 ` Philip Kaludercic
2024-12-06 14:58 ` Max Nikulin
2024-12-06 16:30 ` Eli Zaretskii
2024-12-08 16:41 ` Max Nikulin
2024-12-08 5:15 ` Richard Stallman
2024-12-08 7:15 ` Xiyue Deng
2024-12-08 16:50 ` Max Nikulin
2024-12-11 4:32 ` Richard Stallman
2024-12-12 3:22 ` Debian package with GNU manuals (was: Re: [ELPA] New package c-intro-and-ref) Max Nikulin
2024-12-04 20:02 ` [ELPA] New package c-intro-and-ref -- was Re: Proposal: Include C Manual from RMS in Emacs git, and/or release Suhail Singh
[not found] ` <87wmgf9h70.fsf@jeremybryant.net>
2024-12-04 23:52 ` Suhail Singh
2024-12-07 13:21 ` Jeremy Bryant
2024-12-08 20:44 ` Suhail Singh
2024-12-07 4:22 ` Richard Stallman
2024-12-07 12:29 ` Jeremy Bryant
2024-12-07 14:55 ` Björn Bidar
[not found] ` <87h67fr18v.fsf@>
2024-12-10 5:38 ` Richard Stallman
2024-12-13 23:44 ` Björn Bidar
2024-12-05 5:05 ` Richard Stallman
2024-12-05 6:27 ` Eli Zaretskii
2024-12-03 20:07 ` Björn Bidar
[not found] ` <87cyi8h6n8.fsf@>
2024-12-07 16:02 ` Björn Bidar
2024-12-08 5:10 ` Richard Stallman
2024-12-08 20:07 ` Björn Bidar
2024-12-09 15:11 ` Improve access to documentation in Info format (was: Proposal: Include C Manual from RMS in Emacs git, and/or release) Suhail Singh
2024-12-11 4:37 ` Richard Stallman
2024-12-11 14:13 ` Improve access to documentation in Info format Suhail Singh
2024-12-13 23:41 ` Björn Bidar
[not found] ` <874j3e2b2i.fsf@>
2024-12-11 4:32 ` Proposal: Include C Manual from RMS in Emacs git, and/or release Richard Stallman
2024-12-08 23:03 ` John ff
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='25509.9579271459$1734134126@news.gmane.org' \
--to=bjorn.bidar@thaodan.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jimjoe@gmx.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).