Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: "Bruno Hertz" <spammer.go.home@gmail.com>
Subject: Re: gnus-treat-unsplit-urls supposed to act on outgoing posts?
Date: Mon, 11 Apr 2005 17:16:44 +0200	[thread overview]
Message-ID: <m3ekdhtkbn.fsf@caruso.quasi.local> (raw)
In-Reply-To: <v97jj9d84y.fsf@marauder.physik.uni-ulm.de>

Reiner Steib <reiner.steib@physik.uni-ulm.de> writes:

> On Mon, Apr 11 2005, Reiner Steib wrote:
>
>> On Sun, Apr 10 2005, Bruno Hertz wrote:
> [...]
>>> Now I found out it acts on outgoing articles, too. I.e. in my case it
>>> changed the following
>> [...]
>>> Is this the intended behavior?
>>
>> No, let's see...
>>
>> ,----[ C-h v gnus-treat-unsplit-urls RET ]
>> | gnus-treat-unsplit-urls's value is t
>> | 
>> | Remove newlines from within URLs.
>> `----
>>
>> http://www.gnus.orgnot part of the URL.
>   ^^^^^^^^^^^^^^^^^^^^^^
>
> As you can see, it happens in the *display* of the Gcc-ed article
> which is also used to get the cited text.  This also happens for other
> treat functions.  I'd recommend not to set `gnus-treat-unsplit-urls'
> to t; better use `W u' interactively *only* when needed.
>
>> In `mml-preview', the URL in fact is unsplit, but I don't think it
>> happens in the outgoing or Gcc-ed message.
>
> I doesn't unfold in outgoing or Gcc:
>
> ,----
> | $ grep -A1 http://www /var/spool/news/out.going/8970-1113207545-1
> | http://www.gnus.org
> | not part of the URL.
> `----

Dear me, thanks Reiner for your reply. Really stupid, I could have
just checked myself by displaying the raw article. At times, the
obvious seems too close to just see it. The old 'you got what you
asked for' theme ...

Regards, Bruno.


      reply	other threads:[~2005-04-11 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-10 20:01 Bruno Hertz
2005-04-11  8:19 ` Reiner Steib
2005-04-11  8:34   ` Reiner Steib
2005-04-11 15:16     ` Bruno Hertz [this message]

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=m3ekdhtkbn.fsf@caruso.quasi.local \
    --to=spammer.go.home@gmail.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).