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 18:38:43 +0200	[thread overview]
Message-ID: <83v9p7xuy4.fsf@gnu.org> (raw)
In-Reply-To: <AyNZiA.sBvWzQCGvkJF.4hYsEuRwuoMEacNHO66I@freemail.hu> (message from ndame on Sun, 19 Jan 2020 15:53:31 +0000 (GMT))

> Date: Sun, 19 Jan 2020 15:53:31 +0000 (GMT)
> From: ndame <emacsuser@freemail.hu>
> Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>,
> 	"stefan@marxist.se" <stefan@marxist.se>
> 
> So if I'm not mistaken when the emacs info files are created, the
> @example tag is dropped completely from the output.

Yes.

> If this is the
> case then it could be better to keep the @example tags in some form in
> the emacs info output too and hide them with a face, for example. 

If this is what you propose, then you should discuss this with the
Texinfo developers, not with Emacs developers.  We don't develop and
don't maintain the tools used to produce the Info manuals from their
Texinfo sources.  We just write the Texinfo sources and then invoke
the Texinfo processors to produce the Info format.



  reply	other threads:[~2020-01-19 16:38 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 [this message]
2020-01-19 18:48               ` ndame
2020-01-19 19:13                 ` Eli Zaretskii
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=83v9p7xuy4.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).