|
From: | Paul Eggert |
Subject: | Re: gnulib-tool: don't use hard links |
Date: | Sat, 20 May 2017 15:12:12 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 |
Bruno Haible wrote:
* When I edit a file in the testdir using 'vi', the change gets propagated back to the gnulib checkout. But it does not do so with 'emacs' or 'kate' as editor.
It works for me with Emacs, possibly because I have had the following in my ~/.emacs for many years:
(setq backup-by-copying-when-linked t) (setq backup-by-copying-when-mismatch t)I prefer the hard links; for me, they work better than symlinks would, because Emacs would chatter at me about following symlinks. I don't want to worry about symlinks vs hardlinks when editing these files; I just want to change the file everywhere without fuss. So I'd like to retain the ability to create test dirs with hard links, at least as an option.
How about something like the attached patch? The idea is to use hard links by default (the longstanding practice), and use symlinks if --symlink is given. If you'd prefer to implement a new --hardlink option, I could live with that.
gnulib-tool-symlink.diff
Description: Text Data
[Prev in Thread] | Current Thread | [Next in Thread] |