Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: Improved (non-annoying) underlining
Date: 17 May 2000 08:29:01 -0400	[thread overview]
Message-ID: <vxkvh0ds6lu.fsf@mesquite.charcoal.com> (raw)
In-Reply-To: Per Abrahamsen's message of "17 May 2000 14:09:29 +0200"

Bill White <billw@wolfram.com> writes:
>> I think whitespace
>> within text (not at the beginning of a line) should still be
>> underlined.

Per Abrahamsen <abraham@dina.kvl.dk> writes:
> Agreed.

Well, if you really want that, then changing the regexp to
        "^[ \t]+\\|[ \t]*\n"
(which just adds `^' to the beginning) should take care of it.

That said, I really quite prefer it the way it is right now: When I
write (by hand) something which needs to be underlined, I don't
blindly write a single, long underline under the whole text; I
underline the individual words, which is the behavior the now-current
regexp induces.

I think the reason this is especially odd for Bill is that he has
customized the font sense of "underline" to something very very
different, which is not actually "underlining" at all, but is instead
a color shift, both foreground and background.

In any event, since we have yet another case of personal preference,
would it make sense to create (yet another) customizable regexp?  Call
it, say, gnus-article-emphasize-whitespace-regexp?

>> And speaking of improving underlining, punctuation in underlined text
>> disables underlining. Is there a way to fix that? (I haven't trawled
>> through the source).

> You can customize `gnus-emphasis-alist'.  The tricky part is avoiding
> false positives.

Yeah, that sort of thing has bothered me mildly for much too long.
I'll take a look at that alist today.

But Hrovje is right, we really do beat on regexps too much...

--karl



  parent reply	other threads:[~2000-05-17 12:29 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 [this message]
2000-05-17 12:39       ` Hrvoje Niksic
2000-05-17 12:58         ` Karl Kleinpaste
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=vxkvh0ds6lu.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).