[Top][All Lists]

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

bug#17444: 24.3; cannot C-u M-x recompile (interactively) from outside *

From: B. L.
Subject: bug#17444: 24.3; cannot C-u M-x recompile (interactively) from outside *compilation* buffer.)
Date: Fri, 9 May 2014 11:45:35 -0500

Hi Glenn,

I've attached a couple screenshots showing the issue.  The compile_comint attachment is after a C-u M-x compile performed in my source code buffer.  It's in interactive comint mode and I can interact with the console of the tool I am using.  When I M-x recompile from the original source code buffer I lose interactive comint functionality and can no longer interact with the console.  The buffer is then read-only and I manually have to kill the process/*compilation* buffer.  Which is a minor inconvenience.  I was hoping for M-x recompile to simply recompile using the original compile command in the original directory in any buffer of my choosing.  It seems I'm restricted to only performing this action with the cursor in the *compilation* buffer only.  And with the point/cursor in any other buffer it will recompile but I lose comint functionality.  Hope this clears things up!  Thanks.

On Fri, May 9, 2014 at 11:11 AM, Glenn Morris <address@hidden> wrote:
"B. L." wrote:

> use of recompile, but I have a quick follow-up question.  I have noticed
> that if I compile interactively (through C-u M-x compile), I receive an
> interactive *compilation* buffer that is in comint mode.  If I perform M-x
> recompile in the original source buffer, where I performed the compile, the
> code is recompiled but the *compilation* buffer is no longer in comint
> mode.

I can't reproduce that. My compilation buffers are always in

Attachment: compile_comint.png
Description: PNG image

Attachment: recompile_no_comint.png
Description: PNG image

reply via email to

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