From: Juri Linkov <juri@jurta.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: recompile uses wrong buffer
Date: Fri, 04 Jun 2004 04:22:33 +0300 [thread overview]
Message-ID: <87aczkm58w.fsf@mail.jurta.org> (raw)
In-Reply-To: <51914.217.194.34.123.1086244676.squirrel@wwws.franken.de> (Stephan Stahl's message of "Thu, 3 Jun 2004 08:37:56 +0200 (CEST)")
"Stephan Stahl" <stahl@eos.franken.de> writes:
> M-x recompile from cvs emacs only uses *compile*, *grep*, ... buffers.
>
> I often use M-x compile, M-x rename-uniquely, M-x compile, M-x
> rename-uniquely to be able to (re)recompile two things. With cvs emacs
> that does no longer work right. M-x recompile in one of those buffers does
> not recompile in that buffer but creates a new (or reuses) *compile*
> Buffer. For grep it does so with the *grep* buffer. I am not sure what
> other modes are affected too.
>
> This differs from emacs 21.3 behavior and seems wrong too.
I have been using the new behavior for a while, and can confirm that
it is inconvenient. It would be more natural if calling `compile' or
`grep' reused the same buffer where they were called, because when
called on the compile/grep buffer these commands are perceived as
commands which operate on the current buffer rather than as commands
which create a new buffer. And users who want to start compilation
in a new buffer, can do it from any buffer not in compilation mode.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2004-06-04 1:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 6:37 recompile uses wrong buffer Stephan Stahl
2004-06-04 1:22 ` Juri Linkov [this message]
2004-06-04 2:04 ` Richard Stallman
2004-06-04 8:17 ` Stephan Stahl
2004-06-05 13:48 ` Richard Stallman
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=87aczkm58w.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.