From: Luis Felipe <sirgazil@zoho.com>
To: Daniel Hatton <dan.hatton@btinternet.com>,
Guix help list <help-guix@gnu.org>
Subject: Re: Gnome default web browser
Date: Sun, 1 Dec 2024 19:19:58 +0000 [thread overview]
Message-ID: <830ebeb3-afe6-4dbc-a445-796dfa084219@zoho.com> (raw)
In-Reply-To: <cfdc1dc6-34a2-485e-9216-f4b69ba9b5d9@btinternet.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1124 bytes --]
Hi Daniel,
On 20/11/24 18:07, Daniel Hatton wrote:
> On 20/11/2024 14:18, Felix Lechner wrote:
>
>> I think you may want to modify the *.desktop file (or install your own).
>
> I think it just became a Guix-specific question, because I have a
> whole bunch of different
> $HOME/.local/share/applications/userapp-IceCat-*.desktop files; it
> looks like the guix package manager is generating a new one every time
> there's a version upgrade of IceCat. So, there's a now an issue of
> how I make sure any changes I make to the desktop file survive future
> version upgrades.
For what it's worth, I use Guix System with GNOME, and I also use
IceCat, but I don't have any desktop file related to IceCat in that
location. There were some desktop files starting with "userapp-" but all
were obsolete (programs I no longer use). I don't know why they were
there nor what created them. But some of them did point to binaries in
the /gnu/store and had a comment in my system language that indicates
that they were autogenerated (e.g. «Comment=Definición personalizada
para Evolution»).
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2881 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2024-12-01 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 13:15 Gnome default web browser Daniel Hatton
2024-11-20 14:18 ` Felix Lechner via
2024-11-20 18:07 ` Daniel Hatton
2024-12-01 19:19 ` Luis Felipe [this message]
2024-12-01 17:44 ` Daniel Hatton
2024-12-01 19:46 ` Luis Felipe
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=830ebeb3-afe6-4dbc-a445-796dfa084219@zoho.com \
--to=sirgazil@zoho.com \
--cc=dan.hatton@btinternet.com \
--cc=help-guix@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.