From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Matthew Leach <matthew@mattleach.net>, 37564@debbugs.gnu.org
Subject: bug#37564: [PATCH] don't export LINES and COLUMNS env vars in term to fix ncurses applications
Date: Thu, 03 Oct 2019 13:51:16 -0400 [thread overview]
Message-ID: <9ipnjdemzv.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83sgob98zk.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 02 Oct 2019 05:28:15 +0300")
I think the point is that no terminal emulator / shell combination
actually exports LINES and COLUMNS as environment variables, except for
Emacs term.el. So no application can be relying on the LINES and COLUMNS
environment variables (since there aren't any applications specifically
for use inside Emacs's term). So term.el should stop setting them, since
it actually causes problems.
next prev parent reply other threads:[~2019-10-03 17:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 19:59 bug#37564: [PATCH] don't export LINES and COLUMNS env vars in term to fix ncurses applications Matthew Leach
2019-10-01 6:01 ` Eli Zaretskii
2019-10-01 15:47 ` Matthew Leach
2019-10-01 16:07 ` Eli Zaretskii
2019-10-01 18:33 ` Matthew Leach
2019-10-01 18:58 ` Eli Zaretskii
2019-10-01 19:14 ` Eli Zaretskii
2019-10-01 19:24 ` Matthew Leach
2019-10-02 2:28 ` Eli Zaretskii
2019-10-03 17:51 ` Glenn Morris [this message]
2019-10-04 18:48 ` Matthew Leach
2020-01-20 19:10 ` Stefan Kangas
2020-01-20 19:30 ` Eli Zaretskii
2020-01-21 0:58 ` Glenn Morris
2020-01-21 17:11 ` Eli Zaretskii
2020-01-21 18:10 ` Matthew Leach
2020-01-22 3:38 ` Glenn Morris
2020-01-22 15:46 ` Eli Zaretskii
2020-06-04 16:01 ` Glenn Morris
2020-08-15 12:37 ` Lars Ingebrigtsen
2020-01-24 18:08 ` Stefan Kangas
2020-01-21 3:04 ` Stefan Kangas
2019-10-04 18:47 ` Matthew Leach
2019-10-07 4:11 ` Lars Ingebrigtsen
2019-10-07 9:16 ` Andreas Schwab
2019-10-08 16:38 ` Lars Ingebrigtsen
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=9ipnjdemzv.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=37564@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=matthew@mattleach.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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.