From: Andreas Schwab <schwab@linux-m68k.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: 9323@debbugs.gnu.org
Subject: bug#9323: Non-recursive make build systems and M-x compile
Date: Fri, 19 Aug 2011 21:46:52 +0200 [thread overview]
Message-ID: <m24o1db2vn.fsf@igel.home> (raw)
In-Reply-To: <CAOnWdoh_Wr=DQWgWdWyePb=naRvbEybFh5zf6WvzNZmYZ+nNcw@mail.gmail.com> (Reuben Thomas's message of "Fri, 19 Aug 2011 18:22:06 +0100")
Reuben Thomas <rrt@sc3d.org> writes:
> On 19 August 2011 14:41, Andreas Schwab <schwab@linux-m68k.org> wrote:
>> Reuben Thomas <rrt@sc3d.org> writes:
>>
>>> That's great, but it's not documented for users (it's mentioned in
>>> comments in lisp.el). How about adding something to compile's
>>> docstring along the lines of:
>>>
>>> To launch a compilation in a directory other than that of the buffer,
>>> prefix the compilation command with `cd ..;' or similar; compile will
>>> parse this to set the default directory of the compile buffer.
>>
>> ??? That's exactly what "make -C ..." accomplishes.
>
> That's right, but compile.el does not parse the directory out of a
> "make -C .." command,
Yes, it does. The directory is displayed by the entering message.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2011-08-19 19:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 18:37 bug#9323: Non-recursive make build systems and M-x compile Reuben Thomas
2011-08-18 21:48 ` Andreas Schwab
2011-08-18 22:43 ` Reuben Thomas
2011-08-19 1:28 ` grischka
2011-08-19 3:23 ` Stefan Monnier
2011-08-19 12:17 ` Reuben Thomas
2011-08-19 13:41 ` Andreas Schwab
2011-08-19 17:22 ` Reuben Thomas
2011-08-19 19:46 ` Andreas Schwab [this message]
2011-08-19 19:55 ` Reuben Thomas
2011-08-19 23:30 ` Andreas Schwab
2011-08-20 5:20 ` Reuben Thomas
2011-08-20 12:57 ` Andreas Schwab
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=m24o1db2vn.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=9323@debbugs.gnu.org \
--cc=rrt@sc3d.org \
/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).