From: Dmitry Gutov <dgutov@yandex.ru>
To: 15775@debbugs.gnu.org
Subject: bug#15775: 24.3.50; "WARNING: terminal is not fully functional" in Comint and Eshell
Date: Fri, 01 Nov 2013 05:58:15 +0400 [thread overview]
Message-ID: <87sivgq3wo.fsf@yandex.ru> (raw)
It has been a somewhat common problem with calling external processes
from Emacs. Some references:
http://david.rothlis.net/emacs/customize_general.html#shell
https://github.com/nonsequitur/inf-ruby/issues/33
https://github.com/dgutov/robe/issues/9
The common recommendation is to change the PAGER environment var, and it
works, but why isn't Emacs doing it by default (like with TERM, for
example)?
Can packages just go ahead and set it, without having to leave it to
users? Should they limit the change only to buffers they work with? I
looked at how that could be done with Comint (and a mode deriving from
it), but `make-comint' creates a new buffer, so it's not like I can
change the local value of `process-environment' before the external
process is launched.
In GNU Emacs 24.3.50.3 (x86_64-unknown-linux-gnu, GTK+ Version 3.6.4)
of 2013-10-30 on axl
Bzr revision: 114852 monnier@iro.umontreal.ca-20131030012836-rxvpx3me7vn7gnkw
Windowing system distributor `The X.Org Foundation', version 11.0.11303000
System Description: Ubuntu 13.04
next reply other threads:[~2013-11-01 1:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 1:58 Dmitry Gutov [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-30 23:50 bug#4359: 23.1.50; ^G in M-x grep mode with git grep Ulrich Neumerkel
2011-07-01 0:01 ` Lars Magne Ingebrigtsen
2011-07-01 6:58 ` Jan Djärv
2011-07-01 10:13 ` Lars Magne Ingebrigtsen
2011-07-01 16:48 ` Dan Nicolaescu
2011-07-02 12:35 ` Lars Magne Ingebrigtsen
2022-05-05 12:42 ` bug#4359: bug#15775: 24.3.50; "WARNING: terminal is not fully functional" in Comint and Eshell Lars Ingebrigtsen
2022-06-02 13:07 ` Lars Ingebrigtsen
2022-06-04 17:37 ` Dmitry Gutov
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sivgq3wo.fsf@yandex.ru \
--to=dgutov@yandex.ru \
--cc=15775@debbugs.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/emacs.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).