unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: ndame <emacsuser@freemail.hu>
Cc: stefan@marxist.se, emacs-devel@gnu.org
Subject: Re: Nicer looking Info - html manual +css
Date: Sun, 19 Jan 2020 21:13:52 +0200	[thread overview]
Message-ID: <83iml7xnrj.fsf@gnu.org> (raw)
In-Reply-To: <AyNa0g.nfTFIFx1KYld.rrKQT8vbeZ3DtNA4FzSg@freemail.hu> (message from ndame on Sun, 19 Jan 2020 18:48:34 +0000 (GMT))

> Date: Sun, 19 Jan 2020 18:48:34 +0000 (GMT)
> From: ndame <emacsuser@freemail.hu>
> Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>,
> 	"stefan@marxist.se" <stefan@marxist.se>
> 
> Thinking about this it occurred to me there is a simple heuristic
> solution without involving the Texinfo folks.
> 
> Apparently @example is rendered after an empty line with a 5 spaces
> indent. So it is easy to detect code sections, by looking for empty
> lines followed by +5 spaces indented lines. The code section starts at
> the empty line and ends when the indent is 5 spaces less again.

That won't work in general, because there are other kinds of markup
that end up indented like @example.

And even @example is not always indented exactly 5 spaces, because the
surrounding markup can affect that.  E.g., look at the code fragment
around line 127 of the "Time Conversion" node in the ELisp manual.

We cannot build a feature on such shaky foundations.  When 'makeinfo'
produces the Info output, the markup information is all but lost, and
nothing can bring it back.



  reply	other threads:[~2020-01-19 19:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 15:51 Nicer looking Info - Re: html manual +css ndame
2020-01-18  1:04 ` Jean-Christophe Helary
2020-01-18 17:32   ` Nicer looking Info - " ndame
2020-01-18 19:18     ` Stefan Kangas
2020-01-19  6:04       ` ndame
2020-01-19 15:15         ` Eli Zaretskii
2020-01-19 15:53           ` ndame
2020-01-19 16:38             ` Eli Zaretskii
2020-01-19 18:48               ` ndame
2020-01-19 19:13                 ` Eli Zaretskii [this message]
2020-01-19 17:27             ` Yuan Fu
2020-01-19 17:39               ` Eli Zaretskii

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=83iml7xnrj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacsuser@freemail.hu \
    --cc=stefan@marxist.se \
    /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).