From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 29785@debbugs.gnu.org, larsi@gnus.org
Subject: bug#29785: [PATCH] Implement separate eww history
Date: Wed, 20 Dec 2017 22:14:36 +0200 [thread overview]
Message-ID: <83efnpnolv.fsf@gnu.org> (raw)
In-Reply-To: <87vah1ql4i.fsf@gmail.com> (message from Robert Pluim on Wed, 20 Dec 2017 20:01:33 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: 29785@debbugs.gnu.org, larsi@gnus.org
> Date: Wed, 20 Dec 2017 20:01:33 +0100
>
> >> As currently proposed, no. But if I enabled the separate history
> >> unconditionally then it would.
> >
> > No, it won't. M-p and M-n would still work as they did before.
>
> The history list they would cycle through would be the eww history
> list, not the global minibuffer history list. What am I missing?
You don't miss anything. I'm saying that user-visible behavior won't
change, as users don't care where the history is stored. Therefore, a
defcustom, which is by definition for users and not for developers, is
not needed, at least not IMO.
next prev parent reply other threads:[~2017-12-20 20:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 11:56 bug#29785: [PATCH] Implement separate eww history Robert Pluim
2017-12-20 12:20 ` Lars Ingebrigtsen
2017-12-20 12:23 ` Robert Pluim
2017-12-20 16:02 ` Eli Zaretskii
2017-12-20 16:50 ` Robert Pluim
2017-12-20 18:43 ` Eli Zaretskii
2017-12-20 19:01 ` Robert Pluim
2017-12-20 20:14 ` Eli Zaretskii [this message]
2017-12-21 8:25 ` Robert Pluim
2018-04-12 22:30 ` Lars Ingebrigtsen
2018-04-13 10:21 ` Robert Pluim
2017-12-20 16:17 ` Eli Zaretskii
2017-12-20 16:36 ` Robert Pluim
2017-12-20 16:54 ` Eli Zaretskii
2017-12-20 17:27 ` Robert Pluim
2017-12-20 18:58 ` Lars Ingebrigtsen
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=83efnpnolv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29785@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rpluim@gmail.com \
/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).