GNU bug report logs - #7368
display-buffer may not respect pop-up-frames value

Previous Next

Full log

Message #25 received at 7368 <at> debbugs.gnu.org (full text, mbox):

From: Андрей Парамонов
	<cmr.pent <at> gmail.com>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: martin rudalics <rudalics <at> gmx.at>, 7368 <at> debbugs.gnu.org
Subject: Re: bug#7368: Testcase
Date: Tue, 16 Nov 2010 23:19:50 +0300

2010/11/16 Stefan Monnier <monnier <at> iro.umontreal.ca>:
> It's actually soft-dedicated (i.e. dedicated but switch-to-buffer can
> override it).

After another debug session I see that there are 2 types of special windows:

1) A "softly dedicated" window is a window with 2 properties:
  a) it is tied to a certain buffer, and when that buffer is destroyed
the window is destroyed too;
  b) it cannot be target of display-buffer.

2) A "truly dedicated" window is a window with 3 properties:
  a) it is tied to a certain buffer, and when that buffer is destroyed
the window is destroyed too;
  b) it cannot be target of display-buffer;
  c) it cannot be target of switch-to-buffer.

Wouldn't it be more logical to have the following?

1) A "softly dedicated" window is a window tied to a certain buffer,
and when that buffer is destroyed the window is destroyed too.

2) A "truly dedicated" window is a "softly dedicated" window which
cannot be target of neither display-buffer nor switch-to-buffer.

That would solve the problem, but I'm beginning to doubt if it's worth
it to solve the problem generally...

Best wishes,
Andrey Paramonov

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.