unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Raghav Gururajan via Guix-patches via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Morgan.J.Smith@outlook.com, 56382@debbugs.gnu.org,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: [bug#56382] [PATCH] gnu: gajim: Use hicolor-icon-theme to avoid crashing on startup
Date: Mon, 18 Jul 2022 11:19:50 -0400	[thread overview]
Message-ID: <cef370c5-5239-2c74-77d5-fde7b085ceef@raghavgururajan.name> (raw)
In-Reply-To: <87tu7hsupr.fsf@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 509 bytes --]

Ludo,

>> Right, so the proposed patch (adding ‘hicolor-icon-theme’ to ‘inputs’,
>> not ‘propagated-inputs’) shouldn’t make any difference I guess?
> 
> I think it works as inputs because of our wrappers (perhaps
> XDG_DATA_DIRS)?  But it's kind at odds with our policy which is to let
> users manage icons themselves.

Yep, adding icons to inputs should work because of the wrappers. But the 
reason Maxim mentioned, is why I haven't added icons to inputs in Gajim.

Regards,
RG.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

      parent reply	other threads:[~2022-07-18 15:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04 13:43 [bug#56382] [PATCH] gnu: gajim: Use hicolor-icon-theme to avoid crashing on startup Morgan.J.Smith
2022-07-12 22:15 ` Ludovic Courtès
2022-07-13  8:54 ` Raghav Gururajan via Guix-patches via
2022-07-13 16:06   ` Raghav Gururajan via Guix-patches via
2022-07-15 13:02   ` Ludovic Courtès
2022-07-16  1:38     ` Maxim Cournoyer
2022-07-18  9:29       ` Ludovic Courtès
2022-07-18 13:33         ` [bug#56382] bug#20255: " bokr
2022-07-18 15:19       ` Raghav Gururajan via Guix-patches via [this message]

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=cef370c5-5239-2c74-77d5-fde7b085ceef@raghavgururajan.name \
    --to=guix-patches@gnu.org \
    --cc=56382@debbugs.gnu.org \
    --cc=Morgan.J.Smith@outlook.com \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=rg@raghavgururajan.name \
    /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).