[bug #13673] `mcedit /some/file' doesn't create a lock file
- From: Pavel Tsekov <savannah-bounces gnu org>
- To: Pavel Tsekov <ptsekov gmx net>, mc-devel gnome org
- Cc:
- Subject: [bug #13673] `mcedit /some/file' doesn't create a lock file
- Date: Thu, 7 Jul 2005 14:21:43 +0000
Follow-up Comment #1, bug #13673 (project mc):
The reason for this behaviour is that the function
edit_lock_file() assumes that the filename being passed as an argument is a
relative filename. It uses the filename of the file being edited to create the
name of the lockfile. In the case of mcedit being invoked from the command
line the filename being passed to edit_lock_file() ends up being absolute
filename. The lock filename created as a result looks like this:
.#/tmp/test.txt
Obviously creating a symlink with this name cannot succeed under normal
circumstances.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=13673>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]