From: Jim Porter <jporterbugs@gmail.com>
To: "Eli Zaretskii" <eliz@gnu.org>,
"Sebastián Monía" <sebastian@sebasmonia.com>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] EWW - use revert--buffer-function to reload, and allow reload in eww-list-buffer
Date: Sat, 24 Aug 2024 10:27:51 -0700 [thread overview]
Message-ID: <dd4f4efb-bf58-acf1-a0f4-0dc2bf15a0fb@gmail.com> (raw)
In-Reply-To: <86frqunwgu.fsf@gnu.org>
On 8/24/2024 1:42 AM, Eli Zaretskii wrote:
> Jim, would you please review this and provide comments, if any?
Hmm, it seems strange to me that this patch makes 'eww-list-buffers' be
the 'revert-buffer-function'. That function contains some additional
logic that I don't think belongs for reverting the buffer. For example,
if I opened the EWW buffer list and then renamed the buffer, I'd expect
'revert-buffer' to update the contents of that (now-renamed) buffer.
From reading the code, I think what would happen is that it pops to a
*new* buffer with the original "*eww buffers*" name.
So I think we'd want some new function like 'eww--do-list-buffers' that
takes the code from 'eww-list-buffers' that actually writes out the text
(i.e. the 'let' form starting with '(inhibit-read-only t)'). Then have
'eww-list-buffers' call that, and set 'revert-buffer-function' to
'eww--do-list-buffers'. Or something like that anyway...
next prev parent reply other threads:[~2024-08-24 17:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 17:28 [PATCH] EWW - use revert--buffer-function to reload, and allow reload in eww-list-buffer Sebastián Monía
2024-08-16 17:48 ` Eli Zaretskii
2024-08-16 18:55 ` Sebastián Monía
2024-08-17 12:35 ` Sebastián Monía
2024-08-24 8:42 ` Eli Zaretskii
2024-08-24 17:27 ` Jim Porter [this message]
2024-08-30 20:01 ` Sebastián Monía
2024-09-14 7:32 ` Eli Zaretskii
[not found] ` <thqnjzf7s74l.fsf@sebasmonia.com>
2024-09-20 6:18 ` Eli Zaretskii
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=dd4f4efb-bf58-acf1-a0f4-0dc2bf15a0fb@gmail.com \
--to=jporterbugs@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=sebastian@sebasmonia.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.