Re: sometimes I want to compile and not save files nor be asked

Re: sometimes I want to compile and not save files nor be asked

[Kevin Rodgers]

Dan Jacobson wrote:
 > Compile's docstring should mention compilation-ask-about-save.

I'm not sure about that: there are 7 compilation- user options, of which
only compilation-read-command is mentioned in compile's doc string.

 > Documentation:
 > *Non-nil means C-x c asks which buffers to save before compiling.
 > Otherwise, it saves all modified buffers without asking.
 >
 > Well gosh, how about what if we just plain don't want to be asked
 > about saving, and don't want gratuitous saving?
 >
 > I suppose that 3rd possibility will not fit into the nil/non-nil
 > paradigm mapped out above, that leaves no room for adding more
 > possibilities later.

Good idea:

*** emacs-21.3/lisp/progmodes/compile.el~	Fri Jan 17 06:45:11 2003
--- emacs-21.3/lisp/progmodes/compile.el	Wed Jul 28 11:15:00 2004
***************
*** 449,458 ****
     :group 'compilation)

   ;;;###autoload
! (defcustom compilation-ask-about-save t
!   "*Non-nil means \\[compile] asks which buffers to save before compiling.
! Otherwise, it saves all modified buffers without asking."
!   :type 'boolean
     :group 'compilation)

   ;; Note: the character class after the optional drive letter does not
--- 449,461 ----
     :group 'compilation)

   ;;;###autoload
! (defcustom compilation-save-buffers 'ask
!   "*Non-nil means \\[compile] saves modified buffers before compiling.
! If t, it does so without asking; for other values, it queries the user
! about each file."
!   :type '(choice (const :tag "Save" t)
! 		 (other :tag "Ask" ask)
! 		 (const :tag "Don't save" nil)))
     :group 'compilation)

   ;; Note: the character class after the optional drive letter does not
***************
*** 588,594 ****
        (list (eval compile-command))))
     (unless (equal command (eval compile-command))
       (setq compile-command command))
!   (save-some-buffers (not compilation-ask-about-save) nil)
     (compile-internal command "No more errors"))

   ;; run compile with the default command line
--- 591,598 ----
        (list (eval compile-command))))
     (unless (equal command (eval compile-command))
       (setq compile-command command))
!   (cond ((eq compilation-save-buffers t) (save-some-buffers t))
!         (compilation-save-buffers (save-some-buffers nil)))
     (compile-internal command "No more errors"))

   ;; run compile with the default command line
***************
*** 595,601 ****
   (defun recompile ()
     "Re-compile the program including the current buffer."
     (interactive)
!   (save-some-buffers (not compilation-ask-about-save) nil)
     (compile-internal (eval compile-command) "No more errors"))

   (defun grep-process-setup ()
--- 599,606 ----
   (defun recompile ()
     "Re-compile the program including the current buffer."
     (interactive)
!   (cond ((eq compilation-save-buffers t) (save-some-buffers t))
!         (compilation-save-buffers (save-some-buffers nil)))
     (compile-internal (eval compile-command) "No more errors"))

   (defun grep-process-setup ()

-- 
Kevin Rodgers

Re: sometimes I want to compile and not save files nor be asked

[Richard Stallman]

We could use your changes if you could get the necessary legal papers
to cover them.  However, we don't have them, and the result is that we
cannot implement changes the way you have written them.  It actually
makes our work harder when you post changes, because then we would
have to make sure not to implement the change the way you wrote it.

Re: sometimes I want to compile and not save files nor be asked

[Dan Jacobson]

>>>>> "j" == jay  <jay@_HOSTNAME_> emails me:

j> * Dan Jacobson <jidanni@jidanni.org> at 2004-07-15 01:50+0800
j> | Well gosh, how about what if we just plain don't want to be asked
j> | about saving, and don't want gratuitous saving?

j>  Well, I guess this is more about feature request rather than bug report.
j>  Anyway, I'm using the following simple advice to do the job:

Well OK, but my postings here are mainly for "permanent changes to
emacs for the benefit of future generations", not for advice stuff for
little old me's ~/.emacs.

j>    (setq compilation-read-command      t
j>          compilation-ask-about-save    nil)
j>    (defmacro do-without-save-buffers (command)
j>      `(defadvice ,command (around dont-ask-dont-save-buffers activate)
j>         (flet ((save-some-buffers (&rest args) nil))
j>           ad-do-it)))
j>    (do-without-save-buffers compile)
j>    (do-without-save-buffers recompile)

sometimes I want to compile and not save files nor be asked

[Dan Jacobson]

Compile's docstring should mention compilation-ask-about-save.

Documentation:
*Non-nil means C-x c asks which buffers to save before compiling.
Otherwise, it saves all modified buffers without asking.

Well gosh, how about what if we just plain don't want to be asked
about saving, and don't want gratuitous saving?

I suppose that 3rd possibility will not fit into the nil/non-nil
paradigm mapped out above, that leaves no room for adding more
possibilities later.