emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-bug-tracker] bug#8857: closed (display-buffer attempt to pop-up f


From: GNU bug Tracking System
Subject: [Emacs-bug-tracker] bug#8857: closed (display-buffer attempt to pop-up frame in batch mode causes "Unknown terminal type" error)
Date: Fri, 17 Jun 2011 06:50:03 +0000

Your message dated Fri, 17 Jun 2011 08:49:36 +0200
with message-id <address@hidden>
and subject line Re: bug#8857: display-buffer attempt to pop-up frame in batch 
mode causes      "Unknown terminal type" error
has caused the GNU bug report #8857,
regarding display-buffer attempt to pop-up frame in batch mode causes "Unknown 
terminal type" error
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
8857: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8857
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: display-buffer attempt to pop-up frame in batch mode causes "Unknown terminal type" error Date: Mon, 13 Jun 2011 18:21:30 -0400 User-agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/)
Package: emacs

With the current trunk:

./src/emacs -Q -batch README INSTALL Makefile
Loading vc-bzr...
Unknown terminal type

(exits with status /= 0)

OK, this is not a very sensible example, but it illustrates the point.
It's caused by display-buffer trying to pop-up a frame in batch-mode and
is very recent.

Emacs 23 does not have this problem by default, but the following shows
the same issue:

emacs-23.3 -Q -batch --eval '(setq pop-up-frames t)' README INSTALL Makefile



--- End Message ---
--- Begin Message --- Subject: Re: bug#8857: display-buffer attempt to pop-up frame in batch mode causes "Unknown terminal type" error Date: Fri, 17 Jun 2011 08:49:36 +0200 User-agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.50 (darwin)
martin rudalics writes:
>> However, this
>> effectively means that there really is no default value for
>> pop-up-frames,
>
> ... well it's 'unset ...

Yes. But I think you understand my problem: 'unset doesn't say whether
you should pop up a new frame by default or not. It's pretty much what
Drew says in #8865, and I tend to agree with him on this issue. I think
this special handling of 'unset is cumbersome, and it should simply be a
boolean variable with a default of nil or t.

Anyway, I don't want to bother you with two threads on the same issue,
and the original problem has been solved, so I'm closing this bug and
will maybe follow-up on #8865, but I think pretty much everything has
been said regarding this issue.

-David


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]