From: Michael Cook <michael.cook@cisco.com>
Subject: Re: gnus-article-unsplit-urls
Date: Fri, 04 Jan 2002 12:42:38 -0500 [thread overview]
Message-ID: <g08heq22esx.fsf@zzz.cisco.com> (raw)
In-Reply-To: <ilun0zuqavy.fsf@extundo.com> (Simon Josefsson's message of "Fri, 04 Jan 2002 18:33:21 +0100")
Simon Josefsson <jas@extundo.com> writes:
> http://foo
> bar baz
>
> That is, do not assume the URL is continued if there is more than one
> word on the second line. Perhaps?
i think it's common for long urls to be within a paragraph (that was
the case in the message that got me thinking about this issue). and
so it's common for baz to follow bar on the same line like that.
m.
next prev parent reply other threads:[~2002-01-04 17:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 14:58 gnus-article-unsplit-urls Michael Cook
2002-01-04 15:31 ` gnus-article-unsplit-urls Simon Josefsson
2002-01-04 15:38 ` gnus-article-unsplit-urls Michael Cook
2002-01-04 15:48 ` gnus-article-unsplit-urls Simon Josefsson
2002-01-04 16:37 ` gnus-article-unsplit-urls Lars Magne Ingebrigtsen
2002-01-04 17:27 ` gnus-article-unsplit-urls Simon Josefsson
2002-01-04 17:42 ` gnus-article-unsplit-urls Lars Magne Ingebrigtsen
2002-01-04 18:06 ` gnus-article-unsplit-urls Simon Josefsson
2002-01-04 15:44 ` gnus-article-unsplit-urls Simon Josefsson
2002-01-04 16:38 ` gnus-article-unsplit-urls Lars Magne Ingebrigtsen
2002-01-04 17:08 ` gnus-article-unsplit-urls Michael Cook
2002-01-04 17:12 ` gnus-article-unsplit-urls Lars Magne Ingebrigtsen
2002-01-04 17:33 ` gnus-article-unsplit-urls Simon Josefsson
2002-01-04 17:42 ` Michael Cook [this message]
2002-02-08 14:19 ` gnus-article-unsplit-urls Michael Cook
2002-02-08 14:33 ` gnus-article-unsplit-urls ShengHuo ZHU
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=g08heq22esx.fsf@zzz.cisco.com \
--to=michael.cook@cisco.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).