GNU bug report logs -
#18550
eww-history-browse may end up calling eww-restore-history in an arbitrary buffer
Previous Next
Reported by: Ivan Shmakov <ivan <at> siamics.net>
Date: Wed, 24 Sep 2014 21:20:04 UTC
Severity: normal
Tags: fixed, patch
Fixed in version 25.1
Done: Lars Magne Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
>>>>> Lars Magne Ingebrigtsen <larsi <at> gnus.org> writes:
>>>>> Lars Magne Ingebrigtsen <larsi <at> gnus.org> writes:
>> So I guess eww should set up the `quit-restore' thing properly.
>> I'll have a peek.
> Actually, that doesn't provide a way to do this (rather obvious)
> thing.
> Shouldn't there be a way to instruct `quit-window' to go to a
> specific buffer (if that buffer is still alive)?
I see no reason to abuse quit-window for what’s essentially
switching to a buffer to edit one. That is: the
eww-restore-history call right after quit-window edits the
/current/ buffer. Thus, it indeed makes sense to explicitly use
set-buffer before that. (Or to wrap the call in
with-current-buffer, anyway.)
Moreover, vc.el already uses a dedicated buffer-local variable
for a similar purpose, and so does rcirc.el, and perhaps a few
more modes out there.
--
FSF associate member #7257 http://boycottsystemd.org/ … 3013 B6A0 230E 334A
This bug report was last modified 10 years and 219 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.