all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: file url question
Date: Mon, 13 Apr 2009 13:31:25 +1000	[thread overview]
Message-ID: <87vdp9jkky.fsf@lion.rapttech.com.au> (raw)


Dear all,

just a quick question regarding url formats for a local file. I
encountered problems when using browse-url to view a local file. Looking
into it, it seems that the format of the url being passed to browse-url
may be incorrect and I wanted to see whether others agreed and therefore
if it should be posted to the emacs dev group as a bug. 

Browse url uses the variable browse-url-filename-alist to work out how
to transform certain filenames into a standard url format. In this
alist, the entry for local files is 

("^/+" . "file:/")

This doesn't look right to me. I changed it to be 

 ("^/+" . "file://")

and the problem I was getting with handling local files appears to be
fixed. 

This problem seems to have appeared after a recent upgrade of
w3m-el . I'm running Debian unstable and emacs from cvs (GNU Emacs
23.0.92.1 (i686-pc-linux-gnu, GTK+ Version 2.14.7) of 2009-04-13 on
lion) and the w3m-el-snapshot package (Version: 1.4.344+0.20090405-1). 

My guess is that recent changes in w3m-el have made it a little more
strict on how it handles local file URLs. There is a note that the
function that processes local files has been updated to include files of
the format file://c:/ in addition to file:///c:/. However, this is just
a guess. 

Regardless of this change, it would seem to me that the correct mapping
in browse-url-fl\ilename-alist should be 'file://' rather than
'file:/'. 

Is my reasoning correct or is there something I'm overlooking? Just
wanted to get others opinion prior to logging a bug report. 

Tim


-- 
tcross (at) rapttech dot com dot au


                 reply	other threads:[~2009-04-13  3:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87vdp9jkky.fsf@lion.rapttech.com.au \
    --to=timx@nospam.dev.null \
    --cc=help-gnu-emacs@gnu.org \
    /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.