From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jonathan Kamens Newsgroups: gmane.emacs.bugs Subject: bug#11490: vc-next-action overwrites changes in non-checked-out RCS file Date: Fri, 18 May 2012 10:38:02 -0400 Message-ID: <4FB65ECA.6000205@kamens.us> References: <4FB40003.3050502@kamens.us> <4FB451AE.60508@kamens.us> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------060300030200010905030508" X-Trace: dough.gmane.org 1337351929 24431 80.91.229.3 (18 May 2012 14:38:49 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 18 May 2012 14:38:49 +0000 (UTC) Cc: 11490@debbugs.gnu.org To: Glenn Morris Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri May 18 16:38:47 2012 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SVOKM-0004Ck-J8 for geb-bug-gnu-emacs@m.gmane.org; Fri, 18 May 2012 16:38:46 +0200 Original-Received: from localhost ([::1]:37204 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SVOKL-0000zp-H9 for geb-bug-gnu-emacs@m.gmane.org; Fri, 18 May 2012 10:38:45 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:33185) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SVOKI-0000zU-Q7 for bug-gnu-emacs@gnu.org; Fri, 18 May 2012 10:38:44 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SVOKH-0002ZH-46 for bug-gnu-emacs@gnu.org; Fri, 18 May 2012 10:38:42 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:51526) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SVOKH-0002Z8-0v for bug-gnu-emacs@gnu.org; Fri, 18 May 2012 10:38:41 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1SVOKb-0003FS-QB for bug-gnu-emacs@gnu.org; Fri, 18 May 2012 10:39:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Jonathan Kamens Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 18 May 2012 14:39:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 11490 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 11490-submit@debbugs.gnu.org id=B11490.133735190912449 (code B ref 11490); Fri, 18 May 2012 14:39:01 +0000 Original-Received: (at 11490) by debbugs.gnu.org; 18 May 2012 14:38:29 +0000 Original-Received: from localhost ([127.0.0.1]:32839 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1SVOK5-0003Ek-FV for submit@debbugs.gnu.org; Fri, 18 May 2012 10:38:29 -0400 Original-Received: from jik3.kamens.brookline.ma.us ([128.177.28.63]:42164) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1SVOK2-0003EX-Ln for 11490@debbugs.gnu.org; Fri, 18 May 2012 10:38:27 -0400 Original-Received: from jik2.kamens.brookline.ma.us (jik2-openvpn [10.100.65.34]) (authenticated bits=0) by jik3.kamens.brookline.ma.us (8.13.8/8.13.8) with ESMTP id q4IEc2bs006328 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 May 2012 10:38:03 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 In-Reply-To: X-Enigmail-Version: 1.4.1 X-Scanned-By: MIMEDefang 2.73 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.13 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:60179 Archived-At: This is a multi-part message in MIME format. --------------060300030200010905030508 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 05/17/2012 08:45 PM, Glenn Morris wrote: > Well, ok, but your initial report began: > > Make an RCS file writable with chmod +w without locking it. > > If I instead use M-x toggle-read-only, make changes, and use C-x v v, > then I see the problem. Yeah, well, you can never trust users to be accurate in bug reports. :-( Sorry about that. Seriously, I've encountered this problem twice on two different computers recently, and the other time it happened might have been under Cygwin on Windows, where permissions are screwy. > OK. It looks like that variable only affects RCS and SCCS? > In which case I am guessing that few people will care if the default > changes, so maybe we should just do that... I'm obviously not in any position of authority here, but as for my personal opinion, I would have no objection whatsoever to making vc-mistrust-permissions default to true for safety's sake. Might also want to put a warning in the documentation of the variable about what might happen if you set it to false and then use vc-next-action on a file with non-checked-out changes. Jon --------------060300030200010905030508 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 05/17/2012 08:45 PM, Glenn Morris wrote: 
Well, ok, but your initial report began:

   Make an RCS file writable with chmod +w without locking it.

If I instead use M-x toggle-read-only, make changes, and use C-x v v,
then I see the problem.
Yeah, well, you can never trust users to be accurate in bug reports. :-( Sorry about that.

Seriously, I've encountered this problem twice on two different computers recently, and the other time it happened might have been under Cygwin on Windows, where permissions are screwy.
OK. It looks like that variable only affects RCS and SCCS?
In which case I am guessing that few people will care if the default
changes, so maybe we should just do that...
I'm obviously not in any position of authority here, but as for my personal opinion, I would have no objection whatsoever to making vc-mistrust-permissions default to true for safety's sake. Might also want to put a warning in the documentation of the variable about what might happen if you set it to false and then use vc-next-action on a file with non-checked-out changes.

  Jon

--------------060300030200010905030508--