From: Dave Love <d.love@dl.ac.uk>
Subject: Re: Cool bug in URL parsing
Date: Fri, 05 Jun 1998 18:42:29 GMT [thread overview]
Message-ID: <rzqvhqflmge.fsf@djlvig.dl.ac.uk> (raw)
In-Reply-To: <kigogwam223.fsf@jagor.srce.hr>
Is it really necessary to do (more-or-less slow) buttonizing
etc. automatically for the whole of a big message rather than
restricting it to sensible-sized regions at the top and bottom where
the relevant stuff is likely to be?
.
next prev parent reply other threads:[~1998-06-05 18:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-07 15:15 Karl Kleinpaste
1998-05-07 15:25 ` Hrvoje Niksic
1998-05-07 16:03 ` Per Abrahamsen
1998-05-07 16:09 ` Hrvoje Niksic
1998-06-01 3:15 ` Lars Magne Ingebrigtsen
1998-06-02 6:27 ` Hrvoje Niksic
1998-06-03 3:08 ` Lars Magne Ingebrigtsen
1998-06-03 11:35 ` Hrvoje Niksic
1998-06-04 0:09 ` Lars Magne Ingebrigtsen
1998-06-04 0:40 ` Hrvoje Niksic
1998-06-05 18:42 ` Dave Love [this message]
1998-06-05 19:36 ` Hrvoje Niksic
1998-06-08 9:28 ` Jan Vroonhof
1998-06-08 12:01 ` Hrvoje Niksic
1998-06-08 19:03 ` Jan Vroonhof
1998-06-08 21:32 ` Hrvoje Niksic
1998-06-08 12:52 ` Jari Aalto+list.ding
1998-06-11 17:34 ` Dave Love
1998-06-11 21:53 ` Hrvoje Niksic
1998-05-08 5:03 ` Russ Allbery
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=rzqvhqflmge.fsf@djlvig.dl.ac.uk \
--to=d.love@dl.ac.uk \
/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).