From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: view-read-only causes read-write
Date: Thu, 17 Apr 2003 11:10:29 -0600 [thread overview]
Message-ID: <3E9EE005.1040408@yahoo.com> (raw)
In-Reply-To: mailman.4772.1050547956.21513.bug-gnu-emacs@gnu.org
Dan Jacobson wrote:
> I did
> $ emacs --no-site-file -q -nw -eval '
> (and(setq view-read-only t) (describe-variable (quote
> view-read-only)))'
>
> Notes:
> 1. Ok, the help buffer says View mode in the modeline, but how about
> turning on the -%%- marker in the modeline?
Setting that variable is not the right way to turn on View mode. Setting
any variable is never the right the right way to turn on a mode. Use the
mode's function.
> 2. Hey, real view-mode doesn't let me eat text with C-k etc, and then
> you can't repair the damage with undo because no undo record is
> kept for that buffer.
If you want the buffer in View mode, run the view-mode function.
> 3. OK, trying again without messing first with view-read-only
> gives what one expects.
>
> Do I smell someone toggling read-only once too much?
No. You don't understand that the variable is read to indicate to the user
that view mode is on, and that the view-mode function is used to invoke the
mode.
> 4. view-read-only's docstring: "*Non-nil means buffers visiting files
> read-only, do it in view mode." (P.S. I assume the "*" means
> "Chef's choice".)
>
> OK, but what about read-only buffers not visiting files? Obviously
> you are over affecting those and at the same time not mentioning them.
M-x pick-nit
> P.S. I am no lisp pro but above I had to use an "(and ...)" or else
> only one sexp was used, without any warning to the user.
Of course. Symbolic expressions are well-defined: (function arg ...).
In order to evaluate multiple sexps in sequence, use (progn ...) or multiple
--eval command line options.
> PSS, while we are here, let's examine this docstring:
> toggle-read-only is an interactive compiled Lisp function in `files'.
> (toggle-read-only &optional ARG)
>
> Change whether this buffer is visiting its file read-only.
> With arg, set read-only iff arg is positive.
>
> Ok, but it doesn't say what will happen if you give it a non positive
> arg. One can't just assume "common sense". E.g. me, any common sense
> and I wouldn't be hanging around this pop stand.
"iff" means "if and only if", which is a well-defined logical operator. It
means that if arg is not positive, unset read-only.
> If visiting file read-only and `view-read-only' is non-nil, enter view mode.
>
> Hold on a second. We came here to toggle-read-only and like wham, we
> are sent into view mode. It's like I do "chmod -w file" and wham, "more
> file" is invoked as a free bonus. What if I am a batch job? Anyway,
> docsting looks bad. Didn't check the code.
Then do (setq read-only t) instead of (toggle-read-only 1) to avoid the side
effects.
--
<a href="mailto:<kevin.rodgers@ihs.com>">Kevin Rodgers</a>
next parent reply other threads:[~2003-04-17 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4772.1050547956.21513.bug-gnu-emacs@gnu.org>
2003-04-17 17:10 ` Kevin Rodgers [this message]
2003-04-21 1:17 ` view-read-only causes read-write Dan Jacobson
[not found] ` <mailman.4998.1050903900.21513.bug-gnu-emacs@gnu.org>
2003-04-21 16:39 ` Kevin Rodgers
2003-04-17 1:59 Dan Jacobson
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=3E9EE005.1040408@yahoo.com \
--to=ihs_4664@yahoo.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).