On Sat, May 14, 2011 at 1:26 AM, Brian Ryans wrote:
> Quoting Camaleón on 2011-04-23 05:44:
>> Nowadays it should handle smb:// or other network protocol just the same
> Quoting Erwan David on 2011-04-23 08:48: (re: Camaleón)
>> Prgrams that I know which do this (eg emacs with tramp editing) use a
>> temporary copy on local file. And it is the applicaton which deals with
>> this, not the OS.
> This is the same method vim uses with its netrw plugin. Each app handles it
> itself (as vim and emacs do) or (theoretically) uses some library to do it (as
> I believe KDE does; haven't used KDE since etch)
Unfortunately, these "methods" vary, tremendously, with applications.
For example, I would use Emacs to edit files show them to a colleague,
make my changes, and then save it.. But he would review it by editing
it with vi, *while I had it open*, and when he quit it would overwrite
my work, even though he was using vi in "read-only" mode. Drove me
*NUTS* when I realized: He was mad at me for making unauthorized
changes in core system files, and I was *furious* at him for using an
editor to simply *review* a file, and he absolutely refused to put the
things under any normal source control.
The point is, don't believe that because one application handles file
locking responsibly, that other applications will cooperate with it.