[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] those pesty .#blah emacs symlinks

From: Robert Anderson
Subject: Re: [Gnu-arch-users] those pesty .#blah emacs symlinks
Date: Thu, 29 Apr 2004 18:58:50 -0500

--- Original Message ---
From: Miles Bader <address@hidden>
To: Robert Anderson <address@hidden>
CC: address@hidden
Subject: Re: [Gnu-arch-users] those pesty .#blah emacs symlinks

>On Thu, Apr 29, 2004 at 05:44:46PM -0500, Robert Anderson wrote:
>> Some of my developers are complaining about always having to
>> remove .#blah emacs symlink droppings so they can commit.
>I find that to be a _good_ thing -- it prevents you from
committing when
>you've forgotten to save a file!
>If you've saved all your files, there should be no .#* files
around (if there
>are, and emacs didn't crash or something, then it's a bug, so ...).
>What exactly is the situation where this is a problem?  Do
people really want
>to commit with unsaved changes to files in the tree?  If it's
just an
>occasional `I changed this one file but don't want to commit the
>then a quick-n-dirty way to handle it is mark the buffer as
unmodified (M-~),
>do the commit, and then modify the buffer again to make sure
emacs saves it.

>From my own experience, the issue is usually an emacs which was
killed for some reason and left the symlinks around.  But I'm
guessing why others are running into this often enough to
complain about.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]