From: Drew Adams <drew.adams@oracle.com>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: Indentation conventions for Info manuals; recognizing code
Date: Mon, 8 Mar 2021 15:33:32 +0000 [thread overview]
Message-ID: <SA2PR10MB4474BCF14C2B9C237211ECBCF3939@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <CAP_d_8XWS=0=9RcN2kf=-eupxccyo7OzUZtZhOBJOXJC7Z-O3Q@mail.gmail.com>
> > Too bad the translation has to be lossy. The
> > effect of showing <code>-like stuff is helpful
> > (and is common in technical doc).
> >
> > And something will be needed if we ever hope to
> > allow for variable-pitch text for most regular
> > text while using fixed-pitch for places it makes
> > sense (e.g. code).
>
> You *want* nice variable-pitch text in Info, so you *ask for* a way to
> distinguish code from body text in the Info output format, but what
> you really *need* is the HTML output and a convenient browser for
> that.
Actually, I do *want* (in addition to Info in Emacs)
HTML manuals - and we already have that.
We *need*, I think, an ability to (optionally) use
variable-pitch for most text in Info (in Emacs) and
fixed-pitch for some text, such as code, examples
of user input/output, shell use, ASCII art etc.
All that I find (so far) missing for this is an
ability to recognize the latter, apart from `...',
<...>, function/macro/etc. header lines, etc.
next prev parent reply other threads:[~2021-03-08 15:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 1:58 Indentation conventions for Info manuals; recognizing code Drew Adams
2021-03-07 6:33 ` Eli Zaretskii
2021-03-08 3:47 ` [External] : " Drew Adams
2021-03-08 5:49 ` Yuri Khan
2021-03-08 14:07 ` Eli Zaretskii
2021-03-08 15:33 ` Drew Adams [this message]
2021-03-08 5:37 ` Richard Stallman
2021-03-08 13:57 ` Eli Zaretskii
2021-03-08 15:33 ` [External] : " Drew Adams
-- strict thread matches above, loose matches on Subject: below --
2021-03-08 9:51 tydrdn
2021-03-08 15:33 ` [External] : " Drew Adams
2021-03-26 5:12 ` scame
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=SA2PR10MB4474BCF14C2B9C237211ECBCF3939@SA2PR10MB4474.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=yuri.v.khan@gmail.com \
/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).