unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Jan <tona_kosmicznego_smiecia@interia.pl>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 39989@debbugs.gnu.org
Subject: [bug#39989] [PATCH] gnu: thunar: Wrap with glib:bin to fix launching programs.
Date: Mon, 9 Mar 2020 21:08:04 +0100	[thread overview]
Message-ID: <20200309210804.47a9aa11@kompiuter> (raw)
In-Reply-To: <20200309181108.1650204a@scratchpost.org>

On Mon, 9 Mar 2020 18:11:08 +0100
Danny Milosavljevic <dannym@scratchpost.org> wrote:

> Hi,
> 
> I'm all for fixing this problem, but it would be great to add a
> comment on which executables thunar tries to find in glib:bin.
Should I close the issue, add a commit and reopen the issue, or is
there a more clever way of doing so?

> I've checked glib:bin and it has:
> 
> gapplication
> gdbus
> gdbus-codegen
> gio
> gio-querymodules
> glib-compile-resources
> glib-compile-schemas
> glib-genmarshal
> glib-gettextize
> glib-mkenums
> gobject-query
> gresource
> gsettings
> gtester
> gtester-report
> 
> A lot of those make no sense for thunar to use anyway.

AFAIK it only needs gio-launch-desktop, and seems there's no way to
pick just one binary, is it?
Would changing this:
`("PATH" ":" prefix (,(string-append glib-bin
			"/bin")))))
to
`("PATH" ":" prefix (,(string-append glib-bin
			"/bin/gio-launch-desktop")))))
do the job? 

The macro (or whatever it is) was undocumented in the manual and
explanation in the source code was low level so it is possible I
misunderstood how it works.
I'll try the former.


Jan Wielkiewicz

  reply	other threads:[~2020-03-09 20:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-08 22:12 [bug#39989] [PATCH 0/0] Thunar: fix launching applications Jan Wielkiewicz
2020-03-08 22:23 ` [bug#39989] [PATCH] gnu: thunar: Wrap with glib:bin to fix launching programs Jan Wielkiewicz
2020-03-09 17:11   ` Danny Milosavljevic
2020-03-09 20:08     ` Jan [this message]
2020-03-09 21:43       ` Diego Nicola Barbato
2020-03-09 22:36         ` Jan
2020-03-09 22:43 ` bug#39989: Closing the issue Jan

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=20200309210804.47a9aa11@kompiuter \
    --to=tona_kosmicznego_smiecia@interia.pl \
    --cc=39989@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).