Re: compile: don't ask over and over about saving unrelated files

Re: compile: don't ask over and over about saving unrelated files

[Kevin Rodgers]

Dan Jacobson wrote:

> How about when you do M-x compile and there's some unrelated files you
> are not ready to save, and you wish compile wouldn't keep asking you
> about them each compile.
> 
> Sure we can hit y y y q each time, but sooner or later you end up
> saving them one by one from typing errant y's.
> 
> I'm not sure how to solve this.


Perhaps we could make compile (actually save-some-buffers, which compile
calls for this purpose) distinguish Y from y and N from n, for the
purpose of remembering which files should be saved or not in the future
without asking.

-- 
<a href="mailto:&lt;kevin.rodgers&#64;ihs.com&gt;">Kevin Rodgers</a>

Re: compile: don't ask over and over about saving unrelated files

[Richard Stallman]

    Perhaps we could make compile (actually save-some-buffers, which compile
    calls for this purpose) distinguish Y from y and N from n, for the
    purpose of remembering which files should be saved or not in the future
    without asking.

I really dislike the idea of saving certain files without asking;
however, the feature of making some files as "don't ask" for M-x
compile seems useful.  If you'd like to add that, please do.

One complication is that compile just calls save-some-buffers.
So this feature has to be in save-some-buffers, but only when it
is being done on behalf of compile, not all the time.

Re: compile: don't ask over and over about saving unrelated files

[David Kastrup]

Richard Stallman <rms@gnu.org> writes:

>     Perhaps we could make compile (actually save-some-buffers, which
>     compile calls for this purpose) distinguish Y from y and N from
>     n, for the purpose of remembering which files should be saved or
>     not in the future without asking.
> 
> I really dislike the idea of saving certain files without asking;
> however, the feature of making some files as "don't ask" for M-x
> compile seems useful.  If you'd like to add that, please do.
> 
> One complication is that compile just calls save-some-buffers.  So
> this feature has to be in save-some-buffers, but only when it is
> being done on behalf of compile, not all the time.

And the list of files to ignore should probably be in a buffer-local
variable, shouldn't it?  Since for different compilations, different
files might not warrant saving.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

Re: compile: don't ask over and over about saving unrelated files

[Richard Stallman]

    And the list of files to ignore should probably be in a buffer-local
    variable, shouldn't it?  Since for different compilations, different
    files might not warrant saving.

This would only work the way you intend if you switch to the
compilation buffer before doing M-x compile.  But it is normal
to do M-x compile from other buffers, and in that mode of use,
the local variable won't do the job.

compile: don't ask over and over about saving unrelated files

[Dan Jacobson]

How about when you do M-x compile and there's some unrelated files you
are not ready to save, and you wish compile wouldn't keep asking you
about them each compile.

Sure we can hit y y y q each time, but sooner or later you end up
saving them one by one from typing errant y's.

I'm not sure how to solve this.