unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo <sdl.web@gmail.com>
To: emacs-pretest-bug@gnu.org
Cc: bug-gnu-emacs@gnu.org
Subject: bug#2623: 23.0.91; File is under version-control; use C-x v v to check in/out
Date: Wed, 11 Mar 2009 16:06:10 +0000	[thread overview]
Message-ID: <xbaiiqmgrqml.fsf@cam.ac.uk> (raw)
In-Reply-To: jwv1vt4p0uu.fsf-monnier+emacsbugreports@gnu.org

On 2009-03-11 14:55 +0000, Stefan Monnier wrote:
>>>> File is under version-control; use C-x v v to check in/out
>>>> This message is misleading if not wrong as most of the version control
>>>> tools do not use read-only to indicate their status.
>>> Check in/out used to be bound to C-x C-q (because back then, most of the
>>> version control tools did use read-only to indicate their status), so
>>> the above message is there to remind people who have C-x C-q hardcoded
>>> in their fingers that maybe they really meant to type C-x v v.
>> Should this be changed in 21st?
>
> I do not understand what "21st" is referring to.

I mean '21st century'.

>>> BTW, why did you type C-x C-q?  Is the file read-only?
>> Sometimes I turn the file into read-only before showing to other people
>> in case they accidentally type something into it.
>
> I see, so in this case we could probably avoid the message by being
> a bit more clever (e.g. don't show the message if it's not the first
> time C-x C-q is used in this buffer).

There is difference between turning the buffer into read-only and the
file on disk being read-only. VC backends depend on the latter for their
status based on my experience with RCS. So showing such a message does
not make sense when pressing C-x C-q. It might make sense when opening a
read-only file that is also under version control. But even this point
is mostly irrelevant since 75% of the vc-handled-backends, which
hopefully represent 99.9% users, need not such message.

I just recalled when I was beginning with vc. I did once foolishly
follow that message and wasted myself a few unhappy hours fixing the
consequences.

Just some thoughts.

>         Stefan

-- 
.:  Leo  :.  [ sdl.web AT gmail.com ]  .: I use Emacs :.

               www.git-scm.com
    git - the one true version control system







  reply	other threads:[~2009-03-11 16:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <xbaiy6vdsmeg.fsf@cam.ac.uk>
2009-03-10 16:08 ` bug#2623: 23.0.91; File is under version-control; use C-x v v to check in/out Stefan Monnier
2009-03-11 12:04   ` Leo
2009-03-11 14:55     ` Stefan Monnier
2009-03-11 16:06       ` Leo [this message]
2009-03-12  0:39         ` Stefan Monnier
2009-03-12 18:08           ` Leo
2011-07-11 13:57             ` Lars Magne Ingebrigtsen
2011-07-11 14:33               ` Dan Nicolaescu
2011-07-11 14:40                 ` Lars Magne Ingebrigtsen
2011-07-11 15:53                   ` Dan Nicolaescu

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=xbaiiqmgrqml.fsf@cam.ac.uk \
    --to=sdl.web@gmail.com \
    --cc=2623@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=emacs-pretest-bug@gnu.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).