From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: "T.V. Raman" <tv.raman.tv@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: EWW: Fails to update header-line in eww-forward-link and friends
Date: Sun, 01 Dec 2013 14:06:55 +0100 [thread overview]
Message-ID: <m361r87ma8.fsf@stories.gnus.org> (raw)
In-Reply-To: <CADkJX2iQkENxSdniHxJtDRX6MrB2cGYWu=mG2=Svj=u-G-zFYQ@mail.gmail.com> (T. V. Raman's message of "Mon, 25 Nov 2013 17:37:58 -0800")
"T.V. Raman" <tv.raman.tv@gmail.com> writes:
> The history navigation functions in eww.el
>
> eww-forward-link and eww-backward-link fail to update the header
> line to reflect the displayed page.
This is now fixed.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2013-12-01 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 1:37 EWW: Fails to update header-line in eww-forward-link and friends T.V. Raman
2013-12-01 13:06 ` Lars Magne Ingebrigtsen [this message]
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=m361r87ma8.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=tv.raman.tv@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).