From: Jelle Licht <jlicht@fsfe.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 29892@debbugs.gnu.org
Subject: bug#29892: dvtm does not properly export terminfo
Date: Thu, 4 Jan 2018 16:20:04 +0100 [thread overview]
Message-ID: <CAPsKtf+mZ4-87AH=6g2p5d3JJBzZP6kSFBZVFRHFK3L5q1gyVA@mail.gmail.com> (raw)
In-Reply-To: <87mv1xzec7.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1475 bytes --]
Hello,
2018-01-01 18:19 GMT+01:00 Ludovic Courtès <ludo@gnu.org>:
> Hi!
>
> Jelle Licht <jlicht@fsfe.org> skribis:
>
> > As far as I can see, the current version of dvtm does not work properly
> > with programs such as htop etc.
> >
> > To reproduce:
> > ```
> > $ guix package -i dvtm
> > $ dvtm
> > $ htop
> > ```
> > It only worked properly once I added something like:
> > `export TERMINFO_DIRS="/home/jelle/.guix-profile/share/terminfo"`.
> >
> > Would a proper fix be to simply add a native-search-path declaration to
> the
> > dvtm package? If so, I can prepare a patch this weekend.
>
> ‘TERMINFO_DIRS’ is a search path of ncurses. However, because search
> paths of dependencies are not honored, it doesn’t get set:
>
> https://bugs.gnu.org/22138
>
> This is what we should fix.
>
Fixing this properly seems like it would take effort indeed.
>
> It would feel wrong to add ‘TERMINFO_DIRS’ as a search path of dvtm and
> everything that depends on ncurses.
>
Am I correct in assuming that as a temporary (personal) workaround, I can
just
install ncurses in my profile as well?
Perhaps guix can warn if you install a package which has a dependency
with a search path like ncurses? Or would this be too much of a hassle
to implement?
It would not solve the issue, but at least prevent people from
not understanding why their packages are not working. WDYT?
>
> Thanks,
> Ludo’.
>
- Jelle
[-- Attachment #2: Type: text/html, Size: 2386 bytes --]
next prev parent reply other threads:[~2018-01-04 15:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 14:05 bug#29892: dvtm does not properly export terminfo Jelle Licht
2018-01-01 17:19 ` Ludovic Courtès
2018-01-04 15:20 ` Jelle Licht [this message]
2018-01-05 17:24 ` Ludovic Courtès
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='CAPsKtf+mZ4-87AH=6g2p5d3JJBzZP6kSFBZVFRHFK3L5q1gyVA@mail.gmail.com' \
--to=jlicht@fsfe.org \
--cc=29892@debbugs.gnu.org \
--cc=ludo@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 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).