From: Ken Mankoff <mankoff@gmail.com>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org links and Flatpak firefox
Date: Thu, 28 Jul 2022 16:41:26 -0700 [thread overview]
Message-ID: <87a68s2474.fsf@t480.home> (raw)
In-Reply-To: <ta1kjl$4rn$1@ciao.gmane.io>
Hi Max,
Sorry for the delayed reply.
On 2022-07-05 at 08:16 -07, Max Nikulin <manikulin@gmail.com> wrote:
> On 03/07/2022 20:25, Ken Mankoff wrote:
>> 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.
As you suggested, the problem was not xdotool or X11. It was simply that instead of calling
firefox "${1}" &
to open the URL, I needed to call
flatpak run org.mozilla.firefox "${1}" &
> Out of curiosity, what is the reason why you are avoiding firefox as a
> snap package?
I'm not 100 % sure why but I don't like snap. Maybe because it pollutes the home folder. I read up on snap vs flatpak vs AppImage and flatpak seemed to get the best reviews, so I've gone with that one.
-k.
next prev parent reply other threads:[~2022-07-28 23:44 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
2022-07-28 23:41 ` Ken Mankoff [this message]
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=87a68s2474.fsf@t480.home \
--to=mankoff@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.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 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).