From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 44644@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#44644: /tmp/emacs0/ not cleaned up upon exit
Date: Fri, 27 Nov 2020 08:48:30 +0100 [thread overview]
Message-ID: <87zh33kzox.fsf@gnus.org> (raw)
In-Reply-To: <83sg8wqlpw.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 26 Nov 2020 15:41:31 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> At most, yes. The problem is, it isn't easy to know when the
> directory is under /tmp (we don't use temporary-file-directory, for
> the reasons explained in the comment to server-socket-dir). Maybe we
> should put some special property on server-dir when that is the case?
Did you mean server-socket-dir instead of server-dir here? Yes, I guess
that'd be possible, but the user may change server-socket-dir without
changing the property...
We could literally just check whether the parent of server-socket-dir is
"/tmp" and only delete then. It'd be pretty defensive, but should fix
this minor annoyance.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-11-27 7:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 19:47 bug#44644: /tmp/emacs0/ not cleaned up upon exit 積丹尼 Dan Jacobson
2020-11-16 23:06 ` Lars Ingebrigtsen
2020-11-17 15:00 ` Eli Zaretskii
2020-11-17 15:21 ` 積丹尼 Dan Jacobson
2020-11-24 5:42 ` Lars Ingebrigtsen
2020-11-24 8:48 ` Andreas Schwab
2020-11-24 8:52 ` Lars Ingebrigtsen
2020-11-24 9:29 ` Andreas Schwab
2020-11-24 15:28 ` Eli Zaretskii
2020-11-24 15:41 ` Jean Louis
2020-11-25 6:13 ` Lars Ingebrigtsen
2020-11-26 13:41 ` Eli Zaretskii
2020-11-27 7:48 ` Lars Ingebrigtsen [this message]
2020-11-27 8:12 ` Eli Zaretskii
2020-11-27 8:22 ` Jean Louis
2020-11-27 8:25 ` Lars Ingebrigtsen
2020-11-27 22:34 ` 積丹尼 Dan Jacobson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zh33kzox.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=44644@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jidanni@jidanni.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.