From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16243@debbugs.gnu.org
Subject: bug#16243: 24.3.50; shr-visit-file doesn't set the buffer's default-directory
Date: Tue, 24 Dec 2013 21:14:58 +0100 [thread overview]
Message-ID: <8761qeroot.fsf@building.gnus.org> (raw)
In-Reply-To: <83bo066ts6.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 24 Dec 2013 19:30:33 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> Why is this a problem? Because shr.el binds keys to commands that
> expect the buffer's directory to be set correctly. For example, RET
> is bound to shr-browse-url, which (at least on Windows) needs to
> expand the linked file name relative to the directory of the file that
> is displayed in the buffer.
`shr-visit-file' was a half-assed command I added before I did eww, and
it should probably be removed. It's not very useful any more.
But if we keep the command, then it should be altered to pass the
directory in as the HTTP base URL, which would make the URLs point to
the right thing without altering default-directory.
But setting default-directory might also be nice -- do "special mode"
buffers usually do so or not?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2013-12-24 20:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 17:30 bug#16243: 24.3.50; shr-visit-file doesn't set the buffer's default-directory Eli Zaretskii
2013-12-24 20:14 ` Lars Ingebrigtsen [this message]
2013-12-24 20:56 ` Eli Zaretskii
2013-12-24 21:02 ` Lars Ingebrigtsen
2013-12-25 3:48 ` Eli Zaretskii
2013-12-25 8:19 ` Lars Ingebrigtsen
2013-12-25 17:40 ` Eli Zaretskii
2013-12-25 17:42 ` Lars Ingebrigtsen
2013-12-25 19:39 ` Eli Zaretskii
2013-12-25 19:38 ` Lars Ingebrigtsen
2013-12-25 17:45 ` Lars Ingebrigtsen
2013-12-25 19:40 ` Eli Zaretskii
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=8761qeroot.fsf@building.gnus.org \
--to=larsi@gnus.org \
--cc=16243@debbugs.gnu.org \
--cc=eliz@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.