unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juanma Barranquero'" <lekktu@gmail.com>,
	<1434@emacsbugs.donarmstrong.com>,
	"'Bug-Gnu-Emacs'" <bug-gnu-emacs@gnu.org>
Subject: bug#1434: Docstring for `toggle-read-only' shouldn't imply thebuffer is file-visiting
Date: Wed, 26 Nov 2008 10:08:30 -0800	[thread overview]
Message-ID: <000601c94ff1$fd2f54e0$c2b22382@us.oracle.com> (raw)
In-Reply-To: <f7ccd24b0811260737j5eea334dpe269cb26c3bb076c@mail.gmail.com>

> Most references to readonly-ness in files.el do talk about
> file-visiting buffers, which makes sense. However, `toggle-read-only'
> is useful for non-visiting buffers too, though the docstring seems to
> imply otherwise.
> 
> Docstring for `toggle-read-only' says:
> 
>  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.

FWIW, I agree. When writing mode doc strings that describe some key bindings
using \\[...], for instance, I typically toggle read-only in *Help*, to adjust
line lengths there before correcting the source code.








  reply	other threads:[~2008-11-26 18:08 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 ` Drew Adams [this message]
2008-12-03 23:58 ` Glenn Morris
2008-12-04  0:04   ` 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='000601c94ff1$fd2f54e0$c2b22382@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=1434@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --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).