From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 51716@debbugs.gnu.org
Subject: bug#51716: 29.0.50; [PATCH] Expose xwidget navigation history to Lisp code
Date: Wed, 10 Nov 2021 07:57:26 +0800 [thread overview]
Message-ID: <87pmr8yja1.fsf@yahoo.com> (raw)
In-Reply-To: <83zgqd4dxv.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 09 Nov 2021 16:10:52 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> And we cannot detect those repetitive redirects in Lisp?
Yes, and there are various other shenanigans that vary by system
configuration, WebKit configuration, WebKit version, security policy and
such that are impractical to keep track of. I can't give a concrete
list though.
> So you must rely on WebKit for producing the history?
Yes.
> But once the history is produced/updated, can it be treated as any
> other history variable in Emacs?
Also correct, thanks.
next prev parent reply other threads:[~2021-11-09 23:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <871r3p8r05.fsf.ref@yahoo.com>
2021-11-09 12:15 ` bug#51716: 29.0.50; [PATCH] Expose xwidget navigation history to Lisp code Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-09 13:33 ` Eli Zaretskii
2021-11-09 13:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-09 13:58 ` Eli Zaretskii
2021-11-09 14:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-09 14:10 ` Eli Zaretskii
2021-11-09 23:57 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-11-10 15:25 ` Eli Zaretskii
2021-11-11 1:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-13 15:02 ` Eli Zaretskii
2021-11-14 0:18 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-14 6:53 ` Eli Zaretskii
2021-11-14 6:58 ` Lars Ingebrigtsen
2021-11-14 6:59 ` Lars Ingebrigtsen
2021-11-14 7:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-14 7:18 ` Lars Ingebrigtsen
2021-11-14 7:20 ` Lars Ingebrigtsen
2021-11-14 7:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-14 7:29 ` Eli Zaretskii
2021-11-14 7:33 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-14 8:04 ` Eli Zaretskii
2021-11-14 9:45 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-14 7:20 ` Eli Zaretskii
2021-11-14 13:29 ` Po Lu
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=87pmr8yja1.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=51716@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.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.