From: Michael Albinus <michael.albinus@gmx.de>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: Marcin Borkowski <mbork@mbork.pl>, Corwin Brust <corwin@bru.st>,
Yuan Cao <yuancao85@gmail.com>,
help-gnu-emacs@gnu.org, John Yates <john@yates-sheets.org>
Subject: Re: Emacs in a Corporate Environment
Date: Sun, 16 Apr 2023 09:51:57 +0200 [thread overview]
Message-ID: <874jpgfen6.fsf@gmx.de> (raw)
In-Reply-To: <87sfd0j19v.fsf@thaodan.de> ("Björn Bidar"'s message of "Sun, 16 Apr 2023 00:14:52 +0300")
Björn Bidar <bjorn.bidar@thaodan.de> writes:
Hi Björn,
>> You can be sure that a copy of your remote data end up in your local
>> drive in /tmp. Tramp is busy to clenaup after the operations, but there
>> is no guarantee that it will cover everything. And if somebody calls
>> `file-local-copy' of a remote file, this ends up in your /tmp by
>> intention of the caller.
>
> Not to hijack this list even more but Emacs should probably use various
> directories other then /tmp under Unixes. Under those that use XDG
> (Linux, BSD, Solaris) ${XDG_CACHE_HOME} or ${XDG_STATE_HOME} comes to
> mind.
> Another option is to use ${XDG_RUNTIME_DIR}.
> All those are separate per user and the latter is likely deleted each
> time (tmpfs).
Emacs has the user option temporary-file-directory. It is initialized
using the environment variable $TMPDIR (or $TMP or $TEMP). If that
doesn't exist, "/tmp/" is used.
Prior starting Emacs, $TMPDIR could be set to "${XDG_CACHE_HOME}/emacs/"
(provided, subdirectory "emacs" is created). Alternatively, you could
set this user option in your init file.
Whether Emacs shall support this setting by default, including the
subdir creation, is a different question. Perhaps we shall do this as
opt-in, based on a user variable.
Similarly, you (we) could set small-temporary-file-directory to
"${XDG_RUNTIME_DIR}/emacs/".
> Br,
>
> Björn
Best regards, Michael.
next prev parent reply other threads:[~2023-04-16 7:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 19:48 Emacs in a Corporate Environment Yuan Cao
2023-04-12 20:10 ` Corwin Brust
2023-04-12 20:48 ` John Yates
2023-04-12 21:33 ` Yuan Cao
2023-04-13 0:08 ` Corwin Brust
2023-04-13 14:35 ` Marcin Borkowski
2023-04-14 14:36 ` Michael Albinus
2023-04-14 14:52 ` Eli Zaretskii
2023-04-14 15:08 ` Óscar Fuentes
2023-04-14 15:47 ` Eli Zaretskii
2023-04-14 16:11 ` tomas
2023-04-15 6:12 ` Marcin Borkowski
2023-04-15 7:31 ` tomas
2023-04-15 9:12 ` Marcin Borkowski
2023-04-15 6:11 ` Marcin Borkowski
2023-04-15 7:17 ` Eli Zaretskii
2023-04-15 7:34 ` tomas
2023-04-15 7:59 ` Eli Zaretskii
2023-04-15 8:21 ` tomas
2023-04-15 9:41 ` Eli Zaretskii
2023-04-15 11:16 ` Po Lu
2023-04-15 12:04 ` Marcin Borkowski
2023-04-15 12:18 ` Ruijie Yu via Users list for the GNU Emacs text editor
2023-04-15 13:22 ` tomas
2023-04-15 18:45 ` Michael Albinus
2023-04-15 6:10 ` Marcin Borkowski
2023-04-15 21:14 ` Björn Bidar
2023-04-16 7:51 ` Michael Albinus [this message]
2023-04-13 14:23 ` Marcin Borkowski
2023-04-13 17:23 ` Yuan Cao
2023-04-12 20:52 ` Jean Louis
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874jpgfen6.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=bjorn.bidar@thaodan.de \
--cc=corwin@bru.st \
--cc=help-gnu-emacs@gnu.org \
--cc=john@yates-sheets.org \
--cc=mbork@mbork.pl \
--cc=yuancao85@gmail.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).