From: Lars Ingebrigtsen <larsi@gnus.org>
To: "B. L." <mrbean336@gmail.com>
Cc: 17444@debbugs.gnu.org
Subject: bug#17444: closed (Re: bug#17444: 24.3; cannot C-u M-x recompile (interactively) from outside *compilation* buffer.)
Date: Fri, 25 Sep 2020 16:27:03 +0200 [thread overview]
Message-ID: <87a6xend8o.fsf@gnus.org> (raw)
In-Reply-To: <CAKTB7NcV4aDBkuCaeYXRafo0MB-CrX91Ed1KWHo9sBk2rCXbpQ@mail.gmail.com> (B. L.'s message of "Fri, 9 May 2014 09:55:08 -0500")
"B. L." <mrbean336@gmail.com> writes:
> Hi, thanks for the quick reply. It could be that I am
> misunderstanding the 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. So in short the
> only way I can get comint mode to stay enabled during M-x recompile is
> to perform it in the *compilation* buffer only. Is this correct
> functionality?
This was six years ago...
But looking at the code here, I think this is working as designed,
really -- M-x recompile isn't really designed for doing this, and the
prefix command is already taken. So I don't think this is something
that sounds like we should be fixing, and I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2020-09-25 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 4:39 bug#17444: 24.3; cannot C-u M-x recompile (interactively) from outside *compilation* buffer B. L.
2014-05-09 6:46 ` Glenn Morris
[not found] ` <handler.17444.D17444.139961798613902.notifdone@debbugs.gnu.org>
2014-05-09 14:55 ` bug#17444: closed (Re: bug#17444: 24.3; cannot C-u M-x recompile (interactively) from outside *compilation* buffer.) B. L.
2014-05-09 16:11 ` Glenn Morris
2014-05-09 16:45 ` B. L.
2014-05-09 19:45 ` Glenn Morris
2020-09-25 14:27 ` Lars Ingebrigtsen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a6xend8o.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=17444@debbugs.gnu.org \
--cc=mrbean336@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.