unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: Cecilio Pardo <cpardo@imayhem.com>
Cc: rms@gnu.org,  arne_bab@web.de,  emacs-devel@gnu.org
Subject: Re: Colorizing source code in Info manuals
Date: Sun, 08 Dec 2024 21:58:34 +0200	[thread overview]
Message-ID: <26292.7856923611$1733687952@news.gmane.org> (raw)
In-Reply-To: <c1af5ac0-e4f6-4424-9113-68c14c4c3678@imayhem.com> (Cecilio Pardo's message of "Sun, 8 Dec 2024 19:08:04 +0100")

Cecilio Pardo <cpardo@imayhem.com> writes:

> On 08/12/2024 6:17, Richard Stallman wrote:
>
>> Info format lacks ways to express many sorts of stype information
>> that would be desirable to have on a graphics display.  I am not sure
>> if it makes sense tp try to extend Info forat, or use HTML instead,
>> or what?
>
> Texinfo's HTML uses CSS, which I think emacs does not support.  Also,
> emacs' Info machinery would need some work to adapt it for HTML.
>
> I think some 'cheap' changes in info, such as the presentation of
> source code and emacs key sequences, in my unqualified opinion, are
> worth the effort at this point.

There are examples to handle color information in this context e.g.
like org-mode to reuse existing styling documentation based on the
property of faces defined for other modes.

Another option would be to do something like the like the minted LaTeX
package. It should be a good example to transform the styling elements
into the right elements for the info readers or HTML.



  reply	other threads:[~2024-12-08 19:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-05 22:06 Colorizing source code in Info manuals Cecilio Pardo
2024-12-05 22:33 ` Dr. Arne Babenhauserheide
2024-12-06  0:31   ` Arsen Arsenović
2024-12-06  8:39   ` Cecilio Pardo
2024-12-08  5:17     ` Richard Stallman
2024-12-08 18:08       ` Cecilio Pardo
2024-12-08 19:58         ` Björn Bidar [this message]
2024-12-11  4:33         ` Richard Stallman
2024-12-11 10:41           ` Cecilio Pardo
2024-12-11 21:04             ` chad
2024-12-11  4:33         ` Richard Stallman
2024-12-11 11:01           ` Cecilio Pardo
2024-12-11 17:14             ` [External] : " Drew Adams
2024-12-06  7:38 ` Eli Zaretskii
2024-12-06  8:52   ` Cecilio Pardo
2024-12-06 11:42     ` Eli Zaretskii
2024-12-09  4:56 ` 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='26292.7856923611$1733687952@news.gmane.org' \
    --to=bjorn.bidar@thaodan.de \
    --cc=arne_bab@web.de \
    --cc=cpardo@imayhem.com \
    --cc=emacs-devel@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).