unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rgm@gnu.org, 47529@debbugs.gnu.org,
	Stefan Kangas <stefan@marxist.se>,
	laszlomail@protonmail.com
Subject: bug#47529: Make quoted entities stand out more in info
Date: Tue, 28 Jun 2022 15:49:03 +0200	[thread overview]
Message-ID: <87k090oq40.fsf@gnus.org> (raw)
In-Reply-To: <8335w6e2m1.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 04 Apr 2021 14:00:22 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> > I don't even understand what bug#20721 is about anymore (the first
>> > part, regarding using a newer Texinfo, was done long ago).
>> 
>> >From the original bug report:
>> 
>>     Summary: I want the Info buffer to be colorized, so that I have enough
>>     visual clues to skim it quickly.  I find the Emacs provided default VERY
>>     disconcerting.
>
> But the discussion is about something very different.

Re-skimming this bug report, it seems that most of it's about something
else, and the original issue (about changing default faces) I don't
think we actually want to do anything about, so I'm closing this bug
report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-06-28 13:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-31 19:52 bug#47529: Make quoted entities stand out more in info scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-01  6:40 ` Eli Zaretskii
2021-04-01  7:32   ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-01  7:50     ` Eli Zaretskii
2021-04-01  7:54       ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-01  8:08         ` Eli Zaretskii
2021-04-01  8:30           ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-01  8:54             ` Eli Zaretskii
2021-04-01 16:53               ` Glenn Morris
2021-04-01 17:07                 ` bug#47529: [External] : " Drew Adams
2021-04-03 23:58                 ` Stefan Kangas
2021-04-04  7:36                   ` Eli Zaretskii
2021-04-04  8:50                     ` Stefan Kangas
2021-04-04 11:00                       ` Eli Zaretskii
2022-06-28 13:49                         ` Lars Ingebrigtsen [this message]
2021-04-01 18:41               ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-01 18:57                 ` Eli Zaretskii
2021-04-01 18:59                 ` Eli Zaretskii
2021-04-01 19:07                   ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-01 19:11                     ` 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=87k090oq40.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=47529@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=laszlomail@protonmail.com \
    --cc=rgm@gnu.org \
    --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).