Spurious buffer saving triggered by M-x compile

Spurious buffer saving triggered by M-x compile

[Geoff Gole]

At the moment, M-x compile and friends will trigger the saving of
every file-backed buffer. When there are unsaved buffers unrelated to
the compilation, this becomes quite annoying.

What does everybody think about adding a way to exclude buffers from
this process? We could allow compilation-ask-about-save to be a
predicate function, or add a variable
compilation-save-buffer-predicate.

Re: Spurious buffer saving triggered by M-x compile

[Wojciech Meyer]

On Wed, Jun 16, 2010 at 3:20 PM, Geoff Gole <geoffgole@gmail.com> wrote:
> At the moment, M-x compile and friends will trigger the saving of
> every file-backed buffer. When there are unsaved buffers unrelated to
> the compilation, this becomes quite annoying.
>
> What does everybody think about adding a way to exclude buffers from
> this process? We could allow compilation-ask-about-save to be a
> predicate function, or add a variable
> compilation-save-buffer-predicate.
>
>

It is annoying for me too, although the source control take care about it..
How about asking for the first time, e.g no yes/no but yes/no/ add to
ignore for unsaved buffers?

Re: Spurious buffer saving triggered by M-x compile

[Geoff Gole]

> There has been talk about a project concept on this list before. One
> simple idea was to search up the directory tree to find a vc directory
> (.bzr, .git), or other filename known to exist in the root directory
> of a project.
>
> If there was a concept of a project, compilation-ask-about-save could
> presumably be told to only ask about files in a subdirectory of the
> current project.

That sounds like a good idea, but it would be nice to also handle the
case where there is no project.

(Was this reply supposed to be off-list? I'm dragging it back on-list
on the assumption it was not.)

Re: Spurious buffer saving triggered by M-x compile

[Juri Linkov]

> At the moment, M-x compile and friends will trigger the saving of
> every file-backed buffer. When there are unsaved buffers unrelated to
> the compilation, this becomes quite annoying.
>
> What does everybody think about adding a way to exclude buffers from
> this process? We could allow compilation-ask-about-save to be a
> predicate function, or add a variable
> compilation-save-buffer-predicate.

`compilation-save-buffers-predicate' is already implemented in compile.el.

-- 
Juri Linkov
http://www.jurta.org/emacs/

Re: Spurious buffer saving triggered by M-x compile

[Geoff Gole]

>
> `compilation-save-buffers-predicate' is already implemented in compile.el.
>

I don't see it. My emacs must be too old.

Re: Spurious buffer saving triggered by M-x compile

[Juri Linkov]

>> `compilation-save-buffers-predicate' is already implemented in compile.el.
>
> I don't see it. My emacs must be too old.

(defcustom compilation-save-buffers-predicate nil
  "The second argument (PRED) passed to `save-some-buffers' before compiling.
E.g., one can set this to
  (lambda ()
    (string-prefix-p my-compilation-root (file-truename (buffer-file-name))))
to limit saving to files located under `my-compilation-root'.
Note, that, in general, `compilation-directory' cannot be used instead
of `my-compilation-root' here."
  :type '(choice
          (const :tag "Default (save all file-visiting buffers)" nil)
          (const :tag "Save all buffers" t)
          function)
  :group 'compilation
  :version "24.1")

-- 
Juri Linkov
http://www.jurta.org/emacs/

Re: Spurious buffer saving triggered by M-x compile

[Geoff Gole]

> :version "24.1"

Right, I'm not that up to date. Thanks.