From: Ivan Shmakov <ivan@siamics.net>
To: 19106@debbugs.gnu.org
Subject: bug#19106: M-x eww: use the current URI as the default; be bound to a key
Date: Wed, 19 Nov 2014 20:40:07 +0000 [thread overview]
Message-ID: <8761ea3owo.fsf@violet.siamics.net> (raw)
In-Reply-To: <m3egszkkbf.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 19 Nov 2014 21:27:16 +0100")
>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>>>>> Ivan Shmakov <ivan@siamics.net> writes:
>> I do not copy. Care to provide an example of such a function?
>> (M-p? Did you, by a chance, mean M-n instead? At the very least,
>> C-x C-f has M-n to get buffer-file-name into the minibuffer. And
>> it’s exactly how either of my patches behave.)
> Er, yes, `M-n'.
> I thought the patch had a "default (...)" thing instead?
The second patch has both.
Specifically, when read-string is passed a (non-empty) list for
its ‘default’ argument, the car of such list is used as the
default value, while all the list elements are available for
M-n, M-p. The patch suggested just tries to make the “default
value” part clear to the user:
+ (prompt (concat "Enter URL or keywords"
+ (if uris (format " (default %s)" (car uris) ""))
+ ": ")))
--
FSF associate member #7257 http://boycottsystemd.org/ … 3013 B6A0 230E 334A
next prev parent reply other threads:[~2014-11-19 20:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 12:01 bug#19106: M-x eww: use the current URI as the default; be bound to a key Ivan Shmakov
2014-11-19 12:17 ` Tassilo Horn
2014-11-19 13:31 ` Ivan Shmakov
2014-11-19 14:37 ` Ivan Shmakov
2014-11-19 17:31 ` Lars Magne Ingebrigtsen
2014-11-19 20:07 ` Ivan Shmakov
2014-11-19 20:27 ` Lars Magne Ingebrigtsen
2014-11-19 20:40 ` Ivan Shmakov [this message]
2014-11-22 19:20 ` bug#19106: M-x eww: provide default URIs; " Ivan Shmakov
2014-11-23 15:55 ` Lars Magne Ingebrigtsen
2014-11-19 17:09 ` bug#19106: M-x eww: use the current URI as the default; " Mark Oteiza
2014-11-20 13:45 ` Ivan Shmakov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8761ea3owo.fsf@violet.siamics.net \
--to=ivan@siamics.net \
--cc=19106@debbugs.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).