unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Thierry Volpiatto <thievol@posteo.net>
Cc: 75354@debbugs.gnu.org
Subject: bug#75354: (29.4; eww buffer is not displayed correctly when used from bookmark-jump )
Date: Wed, 08 Jan 2025 15:10:10 +0200	[thread overview]
Message-ID: <8634ht4fkd.fsf@gnu.org> (raw)
In-Reply-To: <87h669vjm9.fsf@posteo.net> (message from Thierry Volpiatto on Wed, 08 Jan 2025 07:40:30 +0000)

> From: Thierry Volpiatto <thievol@posteo.net>
> Date: Wed, 08 Jan 2025 07:40:30 +0000
> 
> I could fix the problem by modifying bookmark--jump-via:

Thanks.

This is contrary to what you originally wrote (with which I agree):

> It is not a bug in `bookmark-jump` but in `eww-bookmark-jump` (the eww
> bookmark handler) which uses wrongly the function `eww` which itself uses
> `pop-to-buffer-same-window`.  Probably a lower level function should be
> used (if one?).

By contrast, the change you propose now will affect all the uses of
bookmarks, everywhere, which is riskier, given how many different
variants of bookmark usage are out there.

Why did you change your mind about the preferred way of fixing this?





  reply	other threads:[~2025-01-08 13:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-04 16:20 bug#75354: 29.4; eww buffer is not displayed correctly when used from bookmark-jump Thierry Volpiatto
2025-01-08  7:40 ` bug#75354: (29.4; eww buffer is not displayed correctly when used from bookmark-jump ) Thierry Volpiatto
2025-01-08 13:10   ` Eli Zaretskii [this message]
2025-01-08 13:52     ` Thierry Volpiatto
2025-01-08 14:03       ` Eli Zaretskii
2025-01-08 14:47         ` Thierry Volpiatto
2025-01-10  5:56         ` Thierry Volpiatto
2025-01-16 16:43           ` Eli Zaretskii
2025-01-16 17:20             ` Thierry Volpiatto
2025-01-15  6:43         ` Thierry Volpiatto
2025-01-15 15:01           ` Eli Zaretskii
2025-01-15 16:15             ` Thierry Volpiatto

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=8634ht4fkd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=75354@debbugs.gnu.org \
    --cc=thievol@posteo.net \
    /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).