From: sigurd@12move.de (Karl Pflästerer)
Subject: Re: gnus-url-mailto broken on foo+bar@somewhere.invalid
Date: Tue, 26 Aug 2003 20:05:41 +0200 [thread overview]
Message-ID: <m3wud0uwkk.fsf@hamster.pflaesterer.de> (raw)
In-Reply-To: <v9oeyce4yn.fsf@marauder.physik.uni-ulm.de>
On 26 Aug 2003, Reiner Steib <- 4.uce.03.r.s@nurfuerspam.de wrote:
> What is the best fix for this? Adding an additional optional
> argument[1], say "allow-plus" to `gnus-url-unhex-string' and call
> (gnus-url-unhex-string url nil t) in `gnus-url-mailto'?
I'm not sure. At first sight it looks ugly. I looked at the function
(here is part of the code):
;; Fixme: Do it like QP.
(defun gnus-url-unhex-string (str &optional allow-newlines)
"Remove %XX, embedded spaces, etc in a url.
If optional second argument ALLOW-NEWLINES is non-nil, then allow the
decoding of carriage returns and line feeds in the string, which is normally
forbidden in URL encoding."
(setq str (or (mm-subst-char-in-string ?+ ? str) "")) ; why `or'?
Two questions?
(a) What's meant with the comment?
(b) What is the substitution good for?
KP
--
Mary had a little lambda,
Its syntax white as snow,
And every program Mary wrote,
She wrote in Lisp, you know.
next prev parent reply other threads:[~2003-08-26 18:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 16:52 Reiner Steib
2003-08-26 18:05 ` Karl Pflästerer [this message]
2003-08-27 13:22 ` Reiner Steib
2003-08-27 14:43 ` Karl Pflästerer
2003-08-26 21:37 ` Jesper Harder
2003-08-27 11:42 ` Benjamin Riefenstahl
2003-08-27 13:57 ` Reiner Steib
2003-08-27 14:53 ` Jesper Harder
2003-08-27 17:37 ` Kai Großjohann
2003-08-27 18:33 ` Jesper Harder
2003-09-04 1:59 ` Jesper Harder
2003-09-04 13:15 ` Reiner Steib
2003-09-04 15:32 ` Jesper Harder
2003-09-04 16:10 ` Simon Josefsson
2003-09-04 16:53 ` Reloading info files (was: gnus-url-mailto broken on foo+bar@somewhere.invalid) Reiner Steib
2003-09-05 21:58 ` Reloading info files Kevin Ryde
2003-09-04 17:43 ` gnus-url-mailto broken on foo+bar@somewhere.invalid Jesper Harder
2003-09-04 22:42 ` Simon Josefsson
2003-09-04 21:46 ` Frank Schmitt
2003-09-05 1:34 ` Jesper Harder
2003-09-05 7:33 ` Frank Schmitt
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=m3wud0uwkk.fsf@hamster.pflaesterer.de \
--to=sigurd@12move.de \
/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).