bug-auctex
[Top][All Lists]
Advanced

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

Re: [Bug-AUCTeX] Interactive mode is not really interactive


From: David Kastrup
Subject: Re: [Bug-AUCTeX] Interactive mode is not really interactive
Date: Thu, 06 Apr 2006 09:21:38 +0200
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux)

Konrad Podczeck <address@hidden> writes:

> When, auctex's "Run interactive" is on, the window showing the
> tex-compiler output does not become active, i.e. does not get
> focus. So this window is not ready to receive keyboard input. This
> is counter to the very meaning of "interactive."

Uh, no it isn't.  It is TeX which is started interactively.  The
semantics of AUCTeX are not changed.

> When Emacs is customized so that the tex-compiler output appears in
> its own frame

How do you customize Emacs in that manner?  Are you sure you are not
describing an Aquamacs-only problem?

> and "Run interactive" is on, then the first tex run makes this frame
> active, but from the second run on, the frame showing the
> tex-compiler output does also not become active anymore.

The semantics are not making anything active at all.  You can press
C-c C-l to show the compiler output, but that would not change focus
usually.

> However, with the customization of having the tex-compiler output
> appearing in its own frame,

Again: what did you do for customizing this?

> this misbehavior is only since Emacs CVS from about middle of
> February; before the tex-compiler output frame always became active.
>
> The following solution for the problem is due to David Reitter,
> maintainer of the Aquamacs Emacs distribution.

Are you or are you not using Aquamacs?  Could you use

M-x TeX-submit-bug-report RET

for generating a bug report including some basics of your configuration?

How did you come by this solution?  Is it part of Aquamacs?  We can
only use code in AUCTeX which has had its copyright assigned to the
FSF.  David Reitter only has an assignment in place just for Emacs,
not AUCTeX.  I don't think he would mind signing the same for AUCTeX,
but of course that would only cover code he explicitly contributed
himself, not code which he talked about with someone else.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum




reply via email to

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