GNU bug report logs - #13801
[PATCH] Trivial fix for files.el

Previous Next

Full log

Message #17 received at 13801 <at> debbugs.gnu.org (full text, mbox):

From: "Drew Adams" <drew.adams <at> oracle.com>
To: "'Stephen Berman'" <stephen.berman <at> gmx.net>
Cc: 'Xue Fuqiao' <xfq.free <at> gmail.com>, 'Eli Zaretskii' <eliz <at> gnu.org>,
	13801 <at> debbugs.gnu.org
Subject: RE: bug#13801: [PATCH] Trivial fix for files.el
Date: Sun, 24 Feb 2013 14:27:06 -0800

> > "Non-nil means break a hard link for the visited file and 
> write to a new file."
> 
> To keep it under 68 characters (as per (elisp) Documentation 
> Tips), how about:
> 
> Non-nil means write visited file to a new file, breaking hard links.

OK by me.  (I was thinking the guideline limit is more than 68.)

But that text suggests that a new file is always used.  Using "any hard link" or
"a hard link" is a bit better, suggesting that the new file thing is conditional
on there being a hard link.

Maybe this (66 chars)?

Non-nil means write new file if `buffer-file-name' is hard-linked.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.