From: Stephen Berman <stephen.berman@gmx.net>
To: Jens Lechtenboerger <lechten@wi.uni-muenster.de>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, 25946@debbugs.gnu.org
Subject: bug#25946: 26.0.50; display-buffer ignores ignores reusable-frames in display-buffer-alist
Date: Mon, 06 Mar 2017 12:07:51 +0100 [thread overview]
Message-ID: <8737eqacjc.fsf@rosalinde> (raw)
In-Reply-To: <8737eqoiz4.fsf@wi.uni-muenster.de> (Jens Lechtenboerger's message of "Mon, 06 Mar 2017 10:25:03 +0100")
On Mon, 06 Mar 2017 10:25:03 +0100 Jens Lechtenboerger <lechten@wi.uni-muenster.de> wrote:
> On 2017-03-06, Stephen Berman wrote:
>
>> On Sun, 05 Mar 2017 23:20:21 +0100 Michael Heerdegen
>> <michael_heerdegen@web.de> wrote:
>>
>>> martin rudalics <rudalics@gmx.at> writes:
>>>
>>>> > I pushed it in your name as commit 702aeca.
>>>>
>>>> Wonderful. Thank you very much. Can you please test whether it DTRT?
>>>> Two steps are needed. [...]
>>>
>>> Works as described for me in emacs -Q after rebuilding.
>>
>> Same here (I couldn't test till just now).
>
> And here, many thanks. (I did not rebuild Emacs in my previous
> test.)
>
> However, I'm having problems with LaTeX/AUCTeX [0] output buffers.
> I'm currently using this obsolete (but working) setting:
> (setq special-display-regexps '(".* output"))
>
> Now, when replacing "\\*text\\*" with ".* output" in the above
> recipe, compiling a tex file (C-c C-c), and pressing C-c C-l to
> display the LaTeX output, a new frame gets created but is split in
> half: The lower half showing the tex source (and containing the
> cursor), the upper with output. I expected the output in the entire
> frame.
I think this window-splitting is because TeX-recenter-output-buffer
(bound to `C-c C-l') calls `(TeX-pop-to-buffer buffer t t)', which calls
pop-to-buffer with the ACTION argument set to t, which according to
pop-to-buffer's doc string " means to pop to a window other than the
selected one even if the buffer is already displayed in the selected
window". Maybe AUCTeX should have a user option that can be passed as
the ACTION argument to pop-to-buffer.
Steve Berman
next prev parent reply other threads:[~2017-03-06 11:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 10:01 bug#25946: 26.0.50; display-buffer ignores ignores reusable-frames in display-buffer-alist Jens Lechtenboerger
2017-03-03 10:38 ` martin rudalics
2017-03-03 10:58 ` Jens Lechtenboerger
2017-03-03 14:24 ` martin rudalics
2017-03-03 14:49 ` Jens Lechtenboerger
2017-03-03 18:23 ` martin rudalics
2017-03-03 18:55 ` Drew Adams
[not found] ` <13CD49F822DC4A42AF94C24270D9E5CF9A5D4E36@WIWI-MAIL-1.WIWI.UNI-MUENSTER.DE>
2017-03-04 17:08 ` Jens Lechtenboerger
2017-03-04 17:40 ` martin rudalics
2017-03-05 10:34 ` martin rudalics
2017-03-05 11:27 ` Stephen Berman
2017-03-05 13:28 ` martin rudalics
2017-03-05 22:20 ` Michael Heerdegen
2017-03-06 8:11 ` martin rudalics
2017-03-06 8:57 ` Stephen Berman
2017-03-06 9:25 ` Jens Lechtenboerger
2017-03-06 11:07 ` Stephen Berman [this message]
2017-03-06 17:46 ` martin rudalics
2017-03-06 20:59 ` Stephen Berman
2017-03-07 9:45 ` martin rudalics
2017-03-07 16:51 ` Stephen Berman
2017-03-07 19:00 ` martin rudalics
2017-03-07 19:36 ` Stephen Berman
2017-03-10 15:01 ` Jens Lechtenboerger
2017-03-11 10:20 ` martin rudalics
2017-03-06 17:46 ` martin rudalics
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=8737eqacjc.fsf@rosalinde \
--to=stephen.berman@gmx.net \
--cc=25946@debbugs.gnu.org \
--cc=lechten@wi.uni-muenster.de \
--cc=michael_heerdegen@web.de \
/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).