From: Maxime Devos <maximedevos@telenet.be>
To: florhizome <florhizome@posteo.net>, 53257@debbugs.gnu.org
Subject: [bug#53257] [PATCH] gnu: foot: expose terminfo dirs via native-search-paths
Date: Fri, 14 Jan 2022 19:02:52 +0000 [thread overview]
Message-ID: <070637a9bb8fc9a51bd39b0a2666ede537bdc949.camel@telenet.be> (raw)
In-Reply-To: <811cc55626870dbf37af3418e8effe191948541a.1642168254.git.florhizome@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]
florhizome schreef op vr 14-01-2022 om 14:02 [+0000]:
> Hi all,
> I noticed foot did not behave normally whenever content would overflow it's current dimensions.
> when I installed alacritty in the same profile, this was fixed. Turned out, alacritty's
> declaration has a native-search-path field entry that fixed foot! Why not just search-paths,
> I can't tell. This might apply to further terminal emulators (kitty had problems starting emacs
> in some contexts for me but I would need to test that more), but for now, just foot!
>
Canonically, search path are set in ‘consumers’, not ‘producers’
(though setting it in ‘producers’ sometimes works). Here,
‘consumer’ = ncurses, maybe screen (why doesn't screen have a native-
search-paths? An oversight?), and ‘producer’ = some terminal emulator.
What application were you running in foot that leaded to an overrun?
Maybe we should add TERMINFO_DIRS to the native-search-paths of the
application. Basically all applications using ncurses need it, I
think?
The following seems relevant:
<https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22138>
though personally that doesn't seem a bug to me.
Were you running emacs in the terminal? If so, maybe TERMINFO_DIRS
need to be added to 'emacs'?
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-14 19:04 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 [this message]
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
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=070637a9bb8fc9a51bd39b0a2666ede537bdc949.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.