unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 10419@debbugs.gnu.org
Subject: bug#10419: 23.3; byte-compile-file: Buffer is read-only: #<buffer  *Compiler Input*>
Date: Sun, 08 Jan 2012 15:51:21 +0100	[thread overview]
Message-ID: <8739bq1c46.fsf@web.de> (raw)
In-Reply-To: <mailman.1445.1326016018.15002.bug-gnu-emacs@gnu.org> (Andreas Schwab's message of "Sun, 08 Jan 2012 10:46:48 +0100")

Andreas Schwab <schwab@linux-m68k.org> writes:

> >> I don't know why you don't just make the file read-only on disk.
> >
> > Of course I could do that.  But then I may forget to make it read-only
> > again after editing the file.
>
> Emacs allows you to edit read-only files, making it writable temporarily
> when saving (after confirmation).

Oh yes, right, I forgot.

I guess I chose my solution to get rid of the

  (yes-or-no-p
   (format
    "File %s is write-protected; try to save anyway? "
    (file-name-nondirectory
     buffer-file-name)))

query every time when saving.  With my solution, I have to toggle the
read-only flag only once and avoid the annoying `yes-or-no-p'.


Thanks,

Michael.





      parent reply	other threads:[~2012-01-08 14:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-01 19:48 bug#10419: 23.3; byte-compile-file: Buffer is read-only: #<buffer *Compiler Input*> Michael Heerdegen
2012-01-06  7:39 ` Glenn Morris
     [not found] ` <mailman.1260.1325835572.15002.bug-gnu-emacs@gnu.org>
2012-01-08  8:41   ` Michael Heerdegen
2012-01-08  9:23     ` Eli Zaretskii
2012-01-08  9:46     ` Andreas Schwab
     [not found]     ` <mailman.1445.1326016018.15002.bug-gnu-emacs@gnu.org>
2012-01-08 14:51       ` Michael Heerdegen [this message]

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=8739bq1c46.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=10419@debbugs.gnu.org \
    --cc=schwab@linux-m68k.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).