[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: `g' and `G' do not provide current url as the initial minibuffer contents
- From: Filipp Gunbin <fgunbin@xxxxxxxxxxx>
- Date: Mon, 28 Jul 2014 16:50:02 +0400
- X-ml-name: emacs-w3m
- X-mail-count: 12350
- References: <86a97xvd4v.fsf@xxxxxxxxxxxxxxxxxxxx> <878une21jz.fsf@xxxxxx> <b4mzjfu5pzg.fsf@xxxxxxx>
On 28/07/2014 08:41 +0900, Katsumi Yamaoka wrote:
(B> And also `c g C-y' or `u g C-y' would be helpful in that case.
(BNot very convenient, at least for me.
(B> We do a similar operation when we use a generic graphic web browser
(B> like Firefox, don't we?
(BYes, but that's one of the reason I prefer emacs-w3m over graphical web
(Bbrowsers, at least for work :)
(B> In the end of Jun 2013, we decided that a url thing is only a list of
(B> arbitrary letters, not a human readable one, though there would be
(B> exceptions of course.
(BIn case of Java API docs (not JDK API only), the URL _is_
(Bhuman-readable, and that's good.
(B> Yes, it is sometimes inconvenient to me too. Could you try the
(B> following advice and see if it is really useful? I'll try it for
(B> some days, too.
(B> (defadvice w3m-input-url (before provide-initial-contents activate)
(B> "Always provide initial minibuffer contents."
(B> (ad-set-arg 5 nil))
(BYes, it works, thank you. It would be great if something like that was
(Bavailable to other users.