From: jdsmith@as.arizona.edu (JD Smith)
Subject: Re: Encoding needed for `browse-url' URLs (IDLWAVE html help)
Date: Fri, 13 Jan 2006 23:50:58 -0700 [thread overview]
Message-ID: <jdsmith-1301062350580001@192.168.1.3> (raw)
In-Reply-To: DB56FDAD-F1BA-424A-B4F7-E8C2A3DA2790@gmail.com
In article <DB56FDAD-F1BA-424A-B4F7-E8C2A3DA2790@gmail.com>, David Reitter
<david.reitter@gmail.com> wrote:
> I got the below bug report and I found that idlwave does not encode
> the URL in `idlwave-help-html-link', i.e. if the path contains a
> space, it is not encoded as "%20".
>
> Are `browse-url' and the function pointed to in `browse-url-browser-
> function' supposed to handle such URLs or not?
> If not, it's a bug in idlwave-mode (but possibly in other places).
>
> (Never mind the reported crash - that was due to an undocumented
> 'feature' in OS X with not-encoded URLs and the patch for browsing
> URLs with the standard browser.)
There is apparently a function `browse-url-file-url' which I overlooked,
which does this for you. Perhaps adding this to the browse-url docstring
would be wise. Even better would be calling it directly on file-based
urls. It does all the encoding necessary. CVS Emacs didn't crash under
OSX when sending file:// urls with unencoded spaces, so that must be an
AquaMacs only thing.
I'll submit this fix along with others in a version of IDLWAVE I'm
preparing for inclusion in Emacs 22 (which does away with the need for
vendor-supplied documentation and scans, among other things).
JD
next prev parent reply other threads:[~2006-01-14 6:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C60E9BBC-342C-4D0C-AA80-794959308B08@umich.edu>
2006-01-12 18:30 ` Encoding needed for `browse-url' URLs (IDLWAVE html help) David Reitter
2006-01-13 16:48 ` Kevin Rodgers
2006-01-14 6:50 ` JD Smith [this message]
2006-01-15 7:49 ` Richard M. Stallman
2006-01-15 10:50 ` David Reitter
[not found] <43CA86B8.4060907@yahoo.de>
2006-01-15 17:42 ` encoding " David Reitter
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=jdsmith-1301062350580001@192.168.1.3 \
--to=jdsmith@as.arizona.edu \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.