From: Maxime Devos <maximedevos@telenet.be>
To: Florian <florhizome@posteo.net>, 53257@debbugs.gnu.org
Subject: [bug#53257] [PATCH] gnu: foot: expose terminfo dirs via native-search-paths
Date: Sat, 15 Jan 2022 16:46:45 +0100 [thread overview]
Message-ID: <f6e522e4a12cb3c512bd0ca8dafdc415cffc89fd.camel@telenet.be> (raw)
In-Reply-To: <87o84dm3fs.fsf@tp-x230-guix.mail-host-address-is-not-set>
[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]
Florian schreef op za 15-01-2022 om 15:19 [+0000]:
> [...]
> As I see major problems f.e. with QT applications, that seem related to
> not setting search paths, a proposal of mine for the future would be to improve/
> actually introduce good documentation to the search-patch
> variables (and their relationship to profiles and propagated inputs)
About documentation, you might be interested in
<https://issues.guix.gnu.org/22138#8>.
> but
> maybe simplify setting a search-path correspanding to a more distinct
> group of programs. I could imagine this as something like a search-path
> "type", working out like this:
> (package
> ...
> (native-search-paths
> (list
> (search-path-specification
> (type terminal-emulator))
> ...)
> )
> at first this would just be the same as the code added to foot, but it
> could be refined (people might be able to see overlaps, and integrate
> some filtering or other optimization for a specific group. Also you could maybe eventually say "install a
> package but without these search-paths"). For groups like qt plugins,
> it could maybe be included in the qt-wrap functionalities to look for
> the paths where plugins are installed and add the corresponding search paths automatically.
Not sure what you mean here, when building a package it is unknown
what plug-ins will be used in advance. The point of search paths is
having some kind of extensibility, setting the search path environment
variables in qt-wrap would undo that.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-01-15 15:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 14:02 [bug#53257] [PATCH] gnu: foot: expose terminfo dirs via native-search-paths florhizome
2022-01-14 19:02 ` Maxime Devos
2022-01-14 22:52 ` Florian
2022-01-15 11:45 ` Maxime Devos
2022-01-15 11:48 ` Maxime Devos
2022-01-15 12:30 ` Maxime Devos
2022-01-15 15:19 ` Florian
2022-01-15 15:38 ` Maxime Devos
2022-01-15 18:46 ` Florian
2022-01-23 21:26 ` Maxime Devos
2022-01-15 15:46 ` Maxime Devos
2022-01-15 15:46 ` Maxime Devos [this message]
2022-01-15 14:24 ` Maxime Devos
2022-01-28 22:34 ` Ludovic Courtès
2022-02-08 12:46 ` Maxime Devos
2022-02-10 20:30 ` Ludovic Courtès
2022-02-10 21:45 ` Maxime Devos
2022-02-12 21:49 ` Ludovic Courtès
2022-02-27 18:34 ` [bug#53257] [PATCH] gnu: foot: Wrap the program to expose TERMINFO_DIRS Kevin Boulain
2022-02-27 18:41 ` Kevin Boulain
2022-02-27 19:22 ` Maxime Devos
2022-02-28 20:29 ` Kevin Boulain
2022-03-01 19:34 ` Kevin Boulain
2022-03-01 19:28 ` Kevin Boulain
2022-06-19 5:27 ` Tom Fitzhenry
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=f6e522e4a12cb3c512bd0ca8dafdc415cffc89fd.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=53257@debbugs.gnu.org \
--cc=florhizome@posteo.net \
/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.