From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: strange highlightings
Date: Tue, 25 Apr 2000 22:16:53 +0200 [thread overview]
Message-ID: <200004252016.WAA28924@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Felix Lee's message of "Tue, 25 Apr 2000 12:24:56 -0700"
Felix Lee <flee@teleport.com> writes:
> Finding the end of a URL is a little tricky.. haven't
> thought of a good way of doing that yet.
I think the old buttonizing code did a very good job at this.
kai
--
Beware of flying birch trees.
next prev parent reply other threads:[~2000-04-25 20:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-24 16:38 Vladimir Volovich
2000-04-24 18:47 ` Kai Großjohann
2000-04-24 19:40 ` Vladimir Volovich
2000-04-25 11:06 ` Kai Großjohann
2000-04-25 11:54 ` Daniel Pittman
2000-04-25 12:09 ` Vladimir Volovich
2000-04-25 13:36 ` Per Abrahamsen
2000-04-25 14:18 ` Kai Großjohann
2000-04-25 14:31 ` Per Abrahamsen
2000-04-25 19:24 ` Felix Lee
2000-04-25 20:16 ` Kai Großjohann [this message]
2000-04-27 18:30 ` wrapped URLs (was: strange highlightings) Jussi Yli-Urpo
2000-04-28 11:39 ` Bill White
2000-04-26 19:37 ` strange highlightings Karl EICHWALDER
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=200004252016.WAA28924@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.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).