From: "Reza Alizadeh Majd" <r.majd@pantherx.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 38926@debbugs.gnu.org
Subject: bug#38926: pcmanfm-qt unable to open files by double click
Date: Tue, 07 Jan 2020 09:53:45 +0330 [thread overview]
Message-ID: <f177a8e8-920a-4f4c-92aa-73a8ecb7e768@www.fastmail.com> (raw)
In-Reply-To: <20200106204453.44cc2213@scratchpost.org>
Hi Danny,
> I don't think that will work. According to the glib source code[1], the
> variable is read at runtime of the final program.
oh, your right !!! I incorrectly thought that GIO_LAUNCH_DESKTOP is a
preprocessor macro.
> What you could do is use your wrap-program in pcmanfm-qt, but with
> GIO_LAUNCH_DESKTOP (value like above) instead of PATH. That should fix
> pcmanfm-qt and I don't see any forward incompatibility or side effects
> introduced by it either. Also, glib would be unmodified.
>
> The downside would be that we would have to patch other broken programs
> one by one (after *finding* them).
>
> But I would still be in favor of that fix for now. Could you try it and
> send a patch?
OK, so I fix and test pcmanfm-qt following this approach and submit the
regarding patch.
--
Regards
Reza Alizadeh Majd
PantherX Team
next prev parent reply other threads:[~2020-01-07 6:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 20:24 bug#38926: pcmanfm-qt unable to open files by double click Reza Alizadeh Majd
2020-01-05 9:56 ` Danny Milosavljevic
2020-01-05 13:52 ` Reza Alizadeh Majd
2020-01-05 22:37 ` Danny Milosavljevic
2020-01-05 22:57 ` Danny Milosavljevic
2020-01-06 10:06 ` Danny Milosavljevic
2020-01-06 16:38 ` Danny Milosavljevic
2020-01-06 16:45 ` Reza Alizadeh Majd
2020-01-06 19:44 ` Danny Milosavljevic
2020-01-07 6:23 ` Reza Alizadeh Majd [this message]
2020-01-07 8:03 ` Reza Alizadeh Majd
2020-01-07 11:19 ` Hartmut Goebel
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f177a8e8-920a-4f4c-92aa-73a8ecb7e768@www.fastmail.com \
--to=r.majd@pantherx.org \
--cc=38926@debbugs.gnu.org \
--cc=dannym@scratchpost.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/guix.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).