From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Sam Steingold <sds@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r99848: (compilation-save-buffers-predicate):
Date: Fri, 09 Apr 2010 21:04:37 -0400 [thread overview]
Message-ID: <jwvwrwg5dik.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <4BBF536E.4090702@gnu.org> (Sam Steingold's message of "Fri, 09 Apr 2010 12:18:54 -0400")
>>>> - I like where this is going, but I'm not sure this is enough.
>>>> Could you explain how you see it being used?
>>> if you edit a huge file which is expensive to save, you do not want it
>>> to be saved whenever you start a compilation elsewhere.
>> ;-) that part I understand of course.
>> But I mean what value do you expect users to use it with?
>> Would they globally set it to save one particular directory of theirs?
>> What if they have more than one project?
> this is problematic because compile does not announce what it's working
> directory is.
Any reason why we can't fix that?
> I can add a variable compile-default-directory which will be nil globally
> and bound to default-directory in compile and recompile; then the users will
> be able to set compilation-save-buffers-predicate to
> (lambda ()
> (string-prefix-p
> (locate-dominating-file compile-default-directory "foo")
> (file-truename (buffer-file-name))))
> so that only files located in the currently compiled project are saved.
> here "foo" should identify the project root, it can be, e.g., "configure" or
> "COPYING" or "README" or "OMakeroot" or "ANNOUNCE".
> we can also use "bzr root"/"hg root" instead of locate-dominating-file.
> this, however, becomes more and more expensive.
How 'bout this:
- we provide some way for the user to explain to compile.el how to find
her projects's root directories (e.g. a list of tell-tale file names).
- then we provide an option to "save only files in the current project".
- and we can also provide an option to "cd to project's root before
running the command".
How does that sound?
Stefan
next prev parent reply other threads:[~2010-04-10 1:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1NzYsW-0004b6-Iu@internal.in.savannah.gnu.org>
2010-04-07 19:00 ` [Emacs-diffs] /srv/bzr/emacs/trunk r99848: (compilation-save-buffers-predicate): New custom variable Stefan Monnier
2010-04-07 20:40 ` Sam Steingold
2010-04-09 3:13 ` [Emacs-diffs] /srv/bzr/emacs/trunk r99848: (compilation-save-buffers-predicate): Stefan Monnier
2010-04-09 16:18 ` Sam Steingold
2010-04-10 1:04 ` Stefan Monnier [this message]
2010-04-11 19:21 ` Sam Steingold
2010-04-11 20:28 ` Stefan Monnier
2010-04-12 20:02 ` Sam Steingold
2010-04-12 21:15 ` Stefan Monnier
2010-04-12 21:47 ` Sam Steingold
2010-04-13 0:04 ` Stefan Monnier
2010-04-13 17:07 ` Tom Tromey
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=jwvwrwg5dik.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=sds@gnu.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 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.