Timeline for Sharing a project tree between environments
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 28, 2014 at 12:54 | comment | added | Tom Goodfellow | Thanks for the steer on backup-by-copying-when-linked - as always with emacs "there's another way to do it" (and since that handles anything but new files I might well survive with it). I also checked gedit and as a pleasant surprise it preserves the inode - beneath it all in glib/gfile is handle_overwrite_open() which explicitly checks for hard links along with other issues that prevent the rename strategy) and if so makes an explicit backup copy (presume it tries copying it back upon a write failure, but I didn't dig through the code that far). So editors using glib should be ok too. | |
| May 28, 2014 at 10:11 | comment | added | gena2x | Hm, yes. This is configurable in emacs: kb.iu.edu/data/acxl.html Thought second time about it. It seems my answer doesn't really adds a lot, symlinks seems the best solution. | |
| May 28, 2014 at 9:57 | comment | added | Tom Goodfellow | I'd prefer to avoid even having "both my dirs" since that then introduces synchronisation between them (and the opportunity for me to forget...) - hence preferring some form of link | |
| May 28, 2014 at 9:52 | comment | added | Tom Goodfellow | With emacs each save creates a new file, e.g.: after ln foo bar ls -i shows the same inode for both files. Now edit bar and save, ls -i now shows different inodes. It makes sense that an editor doesn't just overwrite the existing file, since that risks losing existing contents if there's an error during the operation - for interest why not try it with your favourite editor and see how that behaves? | |
| May 28, 2014 at 9:45 | history | answered | gena2x | CC BY-SA 3.0 |