From: Xue Fuqiao <xfq.free@gmail.com>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'Stephen Berman' <stephen.berman@gmx.net>, 13801@debbugs.gnu.org
Subject: bug#13801: [PATCH] Trivial fix for files.el
Date: Mon, 25 Feb 2013 06:47:26 +0800 [thread overview]
Message-ID: <20130225064726.055f56d71d382b127005836d@gmail.com> (raw)
In-Reply-To: <D38CD05959484E71BA64346B664176FF@us.oracle.com>
On Sun, 24 Feb 2013 14:27:06 -0800
"Drew Adams" <drew.adams@oracle.com> wrote:
> > > "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.
I think there are three problems (to me) about this version:
1. "write new file" is confusing. I don't know what kind of thing will be write to which file;
2. `buffer-file-name' has both a function cell and a value cell, a little confusing;
2. `buffer-file-name' is a string (or returns a string), not a file, so the file cannot be hard-linked.
But I can't give a better version, sorry.
--
Best regards, Xue Fuqiao.
http://www.emacswiki.org/emacs/XueFuqiao
next prev parent reply other threads:[~2013-02-24 22:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-24 6:33 bug#13801: [PATCH] Trivial fix for files.el Xue Fuqiao
2013-02-24 15:06 ` Eli Zaretskii
2013-02-24 17:47 ` Drew Adams
2013-02-24 21:45 ` Stephen Berman
2013-02-24 22:27 ` Drew Adams
2013-02-24 22:47 ` Xue Fuqiao [this message]
2013-12-17 15:10 ` Chong Yidong
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130225064726.055f56d71d382b127005836d@gmail.com \
--to=xfq.free@gmail.com \
--cc=13801@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=stephen.berman@gmx.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.