From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: asterisks disappear
Date: Tue, 09 Nov 2004 09:16:35 +0900 [thread overview]
Message-ID: <b9yis8fev18.fsf@jpl.org> (raw)
In-Reply-To: <87oei8kl0m.fsf@tc-1-100.kawasaki.gol.ne.jp>
>>>>> In <87oei8kl0m.fsf@tc-1-100.kawasaki.gol.ne.jp> Miles Bader wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> I still think it is better to show all text by default. It
>> doesn't mean abolishing emphasis but, for example:
>>
>> * scratch * => *<bold>scratch</bold>*
> I understand what you mean. For bold, it's not so bad. But in the case
> of underlining, it's _really_ ugly -- underlined+non-hidden text looks
> _worse_ than simply doing no processing at all.
> [BTW, if you're going to retain the emphasis characters, apply the
> emphasis to them too. <bold>*foo*</bold> looks less weird than
> *<bold>foo</bold>*.]
I agree. I'm going to modify the default behavior of emphasis
bold during this week. In addition to this, I'd like to improve
the customization type for the `gnus-emphasis-alist' variable so
that it may be easier to understand. Probably, to show actual
regexps and `Match group' subsections will be unnecessary.
>> It might look indeed ugly. However, there is likely to be this
>> custom (i.e. hiding asterisks) only in Gnus and others don't
>> seem to do so.
> I don't think it's so important what other clients do, I think it only
> matters that what Gnus does (1) `makes sense', and (2) doesn't screw up.
Indeed. I only felt uneasy since I wrote buffer names in some
articles recently.
> In the case of _underlining_, Gnus' heuristics work very well -- there
> seem to be extremely few false matches -- but for *bold*, Emacs buffer
> names and common-lisp global-variables provide a source of frequent
> false matches.
> Since underlining+non-hidden looks _really_ bad, but bold+non-hidden is
> not that horrible, I think this means that they deserve independent
> defaults.
I agreed with you extensively. Thank you.
next prev parent reply other threads:[~2004-11-09 0:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-05 10:26 Katsumi Yamaoka
2004-11-05 10:53 ` Reiner Steib
2004-11-05 12:03 ` Katsumi Yamaoka
2004-11-05 12:16 ` Katsumi Yamaoka
2004-11-05 13:00 ` Daniel Pittman
2004-11-07 10:58 ` Miles Bader
2004-11-07 14:12 ` Katsumi Yamaoka
2004-11-07 22:33 ` Miles Bader
2004-11-07 23:14 ` Katsumi Yamaoka
2004-11-08 11:03 ` Ted Zlatanov
2004-11-08 11:44 ` Katsumi Yamaoka
2004-11-08 12:39 ` Miles Bader
2004-11-08 15:06 ` Katsumi Yamaoka
2004-11-08 22:56 ` Miles Bader
2004-11-09 0:16 ` Katsumi Yamaoka [this message]
2004-11-10 13:12 ` Romain Francoise
2004-11-10 23:23 ` Katsumi Yamaoka
2004-11-11 14:14 ` Reiner Steib
2004-11-11 15:03 ` Katsumi Yamaoka
2004-11-09 17:10 ` Jesper Harder
2004-11-08 15:08 ` Ted Zlatanov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b9yis8fev18.fsf@jpl.org \
--to=yamaoka@jpl.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.
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 NNTP newsgroup(s).