unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Jacobson <jidanni@dman.ddts.net>
Subject: Re: user has no business toggling overwrite-mode in read-only buffers
Date: Mon, 21 Apr 2003 09:32:45 +0800	[thread overview]
Message-ID: <87u1cs1vpe.fsf@jidanni.org> (raw)
In-Reply-To: a2ut7b.p7.ln@acm.acm

A> 1. You have a source-file which is RO due to some version control system,
A> but you want to make a private (changed) copy on your own hard disk.  You
A> C-x C-q it, make the changes, then store it where you want with C-x C-w.

You do C-x C-q first.  So it isn't a read-only buffer anymore. I.e.,
um, "like, read the Subject line, Holmes."  Sorry about that.

A> 2. Something (something like dired, perhaps?), makes a listing of files
A> in a buffer, but leaves the buffer RO because "the user has no reason to
A> edit it".

You got me all wrong.  overwrite-mode is that little thing activated
by your pinky when it misses the DEL key and hits the INS key.  It is
good for changing xxxxxxxxxxxx to xxxxxyyyxxxx without hitting
DEL... maybe it should have been called overprint or overstrike mode.

I was just saying the user should have to do vc-toggle-read-only
(^X^Q) before doing (<insert>) overwrite-mode.
-- 
http://jidanni.org/ Taiwan(04)25854780

  reply	other threads:[~2003-04-21  1:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.4954.1050790959.21513.bug-gnu-emacs@gnu.org>
2003-04-19 22:39 ` user has no business toggling overwrite-mode in read-only buffers David Kastrup
2003-04-20 16:57 ` Alan Mackenzie
2003-04-21  1:32   ` Dan Jacobson [this message]
     [not found] ` <mailman.4999.1050904302.21513.bug-gnu-emacs@gnu.org>
2003-04-21 20:12   ` Alan Mackenzie
2003-04-21 20:42   ` Kevin Rodgers
2003-04-21 20:34 ` Kevin Rodgers
2003-04-19 19:47 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=87u1cs1vpe.fsf@jidanni.org \
    --to=jidanni@dman.ddts.net \
    /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).