From: Glenn Morris <rgm@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 1434@emacsbugs.donarmstrong.com
Subject: bug#1434: Docstring for `toggle-read-only' shouldn't imply the buffer is file-visiting
Date: Wed, 03 Dec 2008 18:58:28 -0500 [thread overview]
Message-ID: <k2ej0o95gb.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <f7ccd24b0811260737j5eea334dpe269cb26c3bb076c@mail.gmail.com> (Juanma Barranquero's message of "Wed, 26 Nov 2008 16:37:31 +0100")
"Juanma Barranquero" wrote:
> `toggle-read-only' is useful for non-visiting buffers too, though
> the docstring seems to imply otherwise.
So let's change it?
*** files.el 3 Dec 2008 03:26:01 -0000 1.1022
--- files.el 3 Dec 2008 23:57:40 -0000
***************
*** 4404,4412 ****
(set-buffer-modified-p arg))
(defun toggle-read-only (&optional arg)
! "Change whether this buffer is visiting its file read-only.
With prefix argument ARG, make the buffer read-only if ARG is
! positive, otherwise make it writable. If visiting file read-only
and `view-read-only' is non-nil, enter view mode."
(interactive "P")
(if (and arg
--- 4404,4412 ----
(set-buffer-modified-p arg))
(defun toggle-read-only (&optional arg)
! "Change whether this buffer is read-only.
With prefix argument ARG, make the buffer read-only if ARG is
! positive, otherwise make it writable. If buffer is read-only
and `view-read-only' is non-nil, enter view mode."
(interactive "P")
(if (and arg
next prev parent reply other threads:[~2008-12-03 23:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 15:37 bug#1434: Docstring for `toggle-read-only' shouldn't imply the buffer is file-visiting Juanma Barranquero
2008-11-26 18:08 ` bug#1434: Docstring for `toggle-read-only' shouldn't imply thebuffer " Drew Adams
2008-12-03 23:58 ` Glenn Morris [this message]
2008-12-04 0:04 ` bug#1434: Docstring for `toggle-read-only' shouldn't imply the buffer " Juanma Barranquero
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=k2ej0o95gb.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=1434@emacsbugs.donarmstrong.com \
--cc=lekktu@gmail.com \
/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).