From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 29785@debbugs.gnu.org
Subject: bug#29785: [PATCH] Implement separate eww history
Date: Wed, 20 Dec 2017 18:17:02 +0200 [thread overview]
Message-ID: <83mv2dnzlt.fsf@gnu.org> (raw)
In-Reply-To: <87k1xhy5mi.fsf@gmail.com> (message from Robert Pluim on Wed, 20 Dec 2017 12:56:53 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Date: Wed, 20 Dec 2017 12:56:53 +0100
>
> +@vindex eww-separate-history
> +@cindex eww
> + If you want to keep the history of URI's you've opened separate from
> +the default minibuffer history, set @code{eww-separate-history} to
> +@code{t}
Why should EWW usurp the history of URLs? If we are going to provide
a history of URLs, it should be common to EWW and browse-url at least,
I think, and perhaps other commands that prompt for URL, if there are
such commands.
> ++++
> +*** The new user variable 'eww-separate-history' causes eww to use a
> +separate minibuffer history if non-nil
Period at the end of a sentence, and also EWW should be capitalized, I
think.
Btw, I see lately some kind of tendency to write long multi-line
sentences at the beginning of NEWS entries. This is the opposite of
what we should try doing: NEWS is visited in Outline mode, so we
should facilitate that by having short headers, to allow users hide
the text of the entry.
Thanks.
next prev parent reply other threads:[~2017-12-20 16:17 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83mv2dnzlt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29785@debbugs.gnu.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 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.