From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: Improved (non-annoying) underlining
Date: 17 May 2000 08:58:13 -0400 [thread overview]
Message-ID: <vxkitwds596.fsf@mesquite.charcoal.com> (raw)
In-Reply-To: Hrvoje Niksic's message of "17 May 2000 14:39:04 +0200"
Hrvoje Niksic <hniksic@iskon.hr> writes:
> As Jargon says:
> ...
> Unless I'm missing something, your change makes the two kinds of
> emphasis indistinguishable.
(To discuss this, folks will have to `C-u g' a lot, to see what's
underlying things here.)
In both the old case and the new, *these words* and *these* *words*
have undistinguished emphasization, as Gnus displays them. Similarly,
there is no difference between /these words/ and /these/ /words/,
because neither boldface nor italicization has any representation in
whitespace. It is only in _these words_ /vs/ _these_ _words_ that the
effect can have any distinguishing characteristic at all, because
underlining can affect whitespace, if one lets it.
This is to say that I think the Jargon reference is just plain wrong.
Using "*emphasis like this*" and "*emphasis* *like* *this*" makes no
difference, as displayed by any font-aware reader like Gnus.
Again, it comes down to a personal preference, so I think a
customizable doodad is in order. I'll work up a new patch shortly.
next prev parent reply other threads:[~2000-05-17 12:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-16 21:19 Karl Kleinpaste
2000-05-16 22:03 ` Shenghuo ZHU
2000-05-17 11:41 ` Bill White
2000-05-17 12:09 ` Per Abrahamsen
2000-05-17 12:26 ` Hrvoje Niksic
2000-05-17 15:37 ` Steinar Bang
2000-05-17 12:29 ` Karl Kleinpaste
2000-05-17 12:39 ` Hrvoje Niksic
2000-05-17 12:58 ` Karl Kleinpaste [this message]
2000-05-17 13:35 ` François Pinard
2000-05-17 13:55 ` Kai Großjohann
2000-05-17 14:03 ` Karl Kleinpaste
2000-05-17 14:27 ` Alan Shutko
2000-05-17 14:40 ` Kai Großjohann
2000-05-17 14:42 ` Karl Kleinpaste
2000-05-17 16:00 ` Yair Friedman (Jerusalem)
2000-05-17 14:08 ` Karl Kleinpaste
2000-05-17 14:32 ` Shenghuo ZHU
2000-05-17 14:29 ` Toby Speight
2000-05-17 15:22 ` Yair Friedman (Jerusalem)
2000-05-19 0:22 ` Russ Allbery
2000-05-19 1:41 ` Karl Kleinpaste
2000-05-19 2:09 ` Dan McGuirk
2000-05-19 4:56 ` Russ Allbery
2000-05-17 13:30 ` François Pinard
2000-05-17 14:28 ` Bill White
2000-05-17 14:33 ` Bill White
2000-05-17 14:34 ` Karl Kleinpaste
2000-05-17 18:05 ` Per Abrahamsen
2000-05-17 15:36 ` Indicating hidden threads (Was: Improved (non-annoying) ...) Steinar Bang
2000-05-17 16:07 ` Bill White
2000-05-17 20:13 ` Steinar Bang
2000-05-20 9:26 ` Rade Markovic
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=vxkitwds596.fsf@mesquite.charcoal.com \
--to=karl@charcoal.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.
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).