From: Eli Zaretskii <eliz@gnu.org>
To: Dan Nicolaescu <dann@gnu.org>
Cc: 6028@debbugs.gnu.org
Subject: bug#6028: 24.0.50; HELLO wants "C-x v v"
Date: Sat, 24 Apr 2010 23:40:51 +0300 [thread overview]
Message-ID: <834oj01t4c.fsf@gnu.org> (raw)
In-Reply-To: <yxq7hnw63yt.fsf@fencepost.gnu.org>
> Cc: 6028@debbugs.gnu.org
> From: Dan Nicolaescu <dann@gnu.org>
> Date: Sat, 24 Apr 2010 15:32:58 -0400
>
> If this is in an uninstalled tree, then C-h H opens the HELLO file that is managed by bzr.
Yes.
> The message that you see is what VC says when you try to make writable a file managed by VC.
> Is that the issue here?
The issue here is that the message is bogus. The VCS that is used
does not require "C-x v v" to make the file writable, because the file
is already writable under bzr. The _buffer_ is made read-only by
"C-h H", but the file is not. Perhaps VC sees that the file is under
VCS control and the buffer is read-only, and erroneously deduces that
the VC backend is some VCS of the locking variety. But that is false.
I think VC should not display this message if the backend is not a
locking VCS.
next prev parent reply other threads:[~2010-04-24 20:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-24 12:42 bug#6028: 24.0.50; HELLO wants "C-x v v" Eli Zaretskii
2010-04-24 19:32 ` Dan Nicolaescu
2010-04-24 20:40 ` Eli Zaretskii [this message]
2010-04-25 3:05 ` Dan Nicolaescu
2010-04-25 13:19 ` Stefan Monnier
2010-04-25 19:20 ` Dan Nicolaescu
2010-04-25 19:40 ` Eli Zaretskii
2010-04-26 14:25 ` Stefan Monnier
2010-04-25 13:45 ` Eli Zaretskii
2011-07-13 18:08 ` Lars Magne Ingebrigtsen
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=834oj01t4c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=6028@debbugs.gnu.org \
--cc=dann@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).