GNU bug report logs -
#49261
28.0.50; File Locking Breaks Presumptuous Toolchains
Previous Next
Reported by: Mallchad Skeghyeph <ncaprisunfan <at> gmail.com>
Date: Mon, 28 Jun 2021 18:28:02 UTC
Severity: normal
Found in version 28.0.50
Fixed in version 28.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
Mallchad Skeghyeph <ncaprisunfan <at> gmail.com> writes:
> I've found for a little while now that a few default behaviors of GNU
> emacs pollutes directories.
Yes, this is a question that comes up from time to time, and I don't
think we've documented in a comprehensive way how to make Emacs not
write anything in the directories it visits.
For auto-save files, that's auto-save-file-name-transforms.
For backup files, that's backup-directory-alist.
For lock files, they can be switched off with create-lockfiles.
Would it make sense to allow the user to control where the lockfiles are
written? The lockfiles are symlinks, so it should theoretically be
possible to have them elsewhere without being any racier than the code
currently is, I think.
Any opinions?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
This bug report was last modified 3 years and 305 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.