From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Org links and Flatpak firefox
Date: Tue, 5 Jul 2022 22:16:04 +0700 [thread overview]
Message-ID: <ta1kjl$4rn$1@ciao.gmane.io> (raw)
In-Reply-To: <87iloexr88.fsf@t480.home>
On 03/07/2022 20:25, Ken Mankoff wrote:
> Emacs opens URLs in the last-active (from the UI perspective) firefox,
> even if there is a firefox on the current virtual desktop.
Is it Emacs of Firefox behavior? However it is not trivial to choose
which window should be used to open a new URL if a couple of monitors,
virtual desktops, and contextual identities are involved.
> I had "browse-url-generic-program" set to a script that used xdotool to
> find if there was a firefox on this desktop, and then sent the URL
> there. xdotool doesn't play nice withe flatpak, and that was the problem.
I am not an X11 expert but it sounds strange. The protocol is designed
to work across network, so it should not matter whether some application
is running from flatpak. May it happen that after upgrade Wayland
session is used instead of X11? Though in such case I would expect that
xdotool should be rather broken due to stricter security model.
Out of curiosity, what is the reason why you are avoiding firefox as a
snap package? It should be tested better on Ubuntu. I do not like it
because instead of decentralized apt mirrors it forces to use fixed
source of packages, upgrade policy is not clear to me as well. My
impression is that priorities related to application isolation is not
consistent with my expectations. I understand reasons behind decision of
Canonical to drop .deb package, but I still do not like them: browser
packages are too expensive to build, not to mention long time support
promise conflict with desire of developers to use modern tools.
next prev parent reply other threads:[~2022-07-05 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 16:03 Org links and Flatpak firefox Ken Mankoff
2022-07-02 23:10 ` Tim Cross
2022-07-03 3:46 ` Max Nikulin
2022-07-03 13:25 ` Ken Mankoff
2022-07-05 15:16 ` Max Nikulin [this message]
2022-07-28 23:41 ` Ken Mankoff
2022-07-30 3:49 ` Tim Cross
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ta1kjl$4rn$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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/org-mode.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).