From: Glenn Morris <rgm@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 8857@debbugs.gnu.org
Subject: bug#8857: display-buffer attempt to pop-up frame in batch mode causes "Unknown terminal type" error
Date: Wed, 15 Jun 2011 03:29:23 -0400 [thread overview]
Message-ID: <9ypqmfy2lo.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <nuei2x9xud.fsf@fencepost.gnu.org>
In addition I still think it might be worth explicitly making
display-buffer a no-op in batch mode, unless someone can think of
something it can actually do in such cases. I think this could only be
by side effect. Eg, can it run hooks, and can those hooks be expected to
do anything when there isn't actually a display?
If not then it seems simpler and more efficient to not even try
displaying buffers in batch mode (and less confusing, since it can give
unclear errors trying to do something that cannot work).
next prev parent reply other threads:[~2011-06-15 7:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 22:21 bug#8857: display-buffer attempt to pop-up frame in batch mode causes "Unknown terminal type" error Glenn Morris
2011-06-13 22:23 ` Glenn Morris
2011-06-14 9:16 ` martin rudalics
2011-06-14 16:19 ` Glenn Morris
2011-06-14 17:14 ` martin rudalics
2011-06-14 17:20 ` Glenn Morris
2011-06-14 17:56 ` martin rudalics
2011-06-14 18:25 ` Glenn Morris
2011-06-14 19:09 ` martin rudalics
2011-06-15 7:29 ` Glenn Morris [this message]
2011-06-15 8:01 ` martin rudalics
2011-06-15 16:17 ` Glenn Morris
2011-06-15 17:01 ` David Engster
2011-06-15 17:45 ` martin rudalics
2011-06-15 18:09 ` Glenn Morris
2011-06-15 18:13 ` David Engster
2011-06-15 19:16 ` Glenn Morris
2011-06-15 18:30 ` David Engster
2011-06-15 19:32 ` martin rudalics
2011-06-15 19:42 ` David Engster
2011-06-16 9:23 ` martin rudalics
2011-06-16 10:04 ` David Engster
2011-06-16 13:01 ` martin rudalics
2011-06-16 13:57 ` David Engster
2011-06-16 15:08 ` martin rudalics
2011-06-17 6:49 ` David Engster
2011-06-16 14:17 ` Stefan Monnier
2011-06-15 14:36 ` Stefan Monnier
2011-06-15 19:40 ` Glenn Morris
2011-06-15 21:02 ` Stefan Monnier
2011-06-15 22:13 ` Glenn Morris
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=9ypqmfy2lo.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=8857@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).