unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: hw <hw@adminart.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: volatile /tmp [was: how to force auto-save of buffers not visiting files, right now?]
Date: Sun, 20 Mar 2022 12:13:15 +0100	[thread overview]
Message-ID: <YjcMS2WxhF6lIB3L@tuxteam.de> (raw)
In-Reply-To: <c63af710131a69df85f4cf26a46d65fceea79e4e.camel@adminart.net>

[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]

On Sun, Mar 20, 2022 at 11:36:05AM +0100, hw wrote:
> On Sun, 2022-03-20 at 09:05 +0100, tomas@tuxteam.de wrote:
> > On Sun, Mar 20, 2022 at 08:29:55AM +0100, tomas@tuxteam.de wrote:
> > 
> > [...]
> > 
> > > > Apprently that leads to puttting some files into /tmp, and I would
> > > > consider it a bug to put auto-save files into /tmp because doing that
> > > > totally defeats the auto-saving because /tmp is volatile.
> > 
> > Note that the convention on Gnu/Linux is to use /var/tmp for things
> > you want to persist across reboots. So perhaps just changing the
> > replacement value might make you happy.
> 
> Well, I have set `tramp-auto-save-directory' to a suitable value, so
> it doesn't really matter.
> 
> Shouldn't GNU Emacs use this GNU convention of using /var/tmp/ when
> it's all GNU?

That still depends on whether people want auto-saves to persist
reboots. There doesn't seem to be a majority for it, much less a
consensus.

So either change it for yourself (and document what you did, to
help others in your situation) or start convincing people if you
want that to become a more general default :-)

Cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2022-03-20 11:13 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14  4:55 how to force auto-save of buffers not visiting files, right now? hw
2022-03-14 12:48 ` Eli Zaretskii
2022-03-15  5:20   ` hw
2022-03-15  6:47     ` Jean Louis
2022-03-15  7:24       ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-17  4:35       ` hw
2022-03-17  5:00         ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-18  7:31           ` hw
2022-03-18 14:45             ` [External] : " Drew Adams
2022-03-19  2:33               ` hw
2022-03-19  2:38                 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-15 14:07     ` Eli Zaretskii
2022-03-16  0:51 ` Michael Heerdegen
2022-03-16  1:45   ` [External] : " Drew Adams
2022-03-17 19:23   ` hw
2022-03-17 22:07     ` Michael Heerdegen
2022-03-18  8:28       ` hw
2022-03-19  1:18         ` Michael Heerdegen
2022-03-19  3:14           ` hw
2022-03-19  3:47             ` Michael Heerdegen
2022-03-19  6:24               ` hw
2022-03-19  7:34                 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-19  7:51                 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-20  6:02                   ` hw
2022-03-20  6:26                     ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-19  9:58                 ` Michael Albinus
2022-03-20  6:36                   ` hw
2022-03-20  7:04                     ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-21 16:22                       ` [External] : " Drew Adams
2022-03-20  7:29                     ` tomas
2022-03-20  8:05                       ` volatile /tmp [was: how to force auto-save of buffers not visiting files, right now?] tomas
2022-03-20 10:36                         ` hw
2022-03-20 11:13                           ` tomas [this message]
2022-03-21  3:41                             ` hw
2022-03-21  5:53                               ` tomas
2022-03-21  8:47                               ` Michael Albinus
2022-03-20  9:57                       ` how to force auto-save of buffers not visiting files, right now? Michael Albinus
2022-03-20 10:21                         ` tomas
2022-03-20 10:19                       ` hw
2022-03-20 10:30                         ` tomas
2022-03-21  3:55                           ` hw
2022-03-21  4:13                             ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-21 12:22                             ` Eli Zaretskii
2022-03-23  6:12                               ` hw
2022-03-23  9:25                                 ` Michael Albinus
2022-03-20  0:21                 ` Michael Heerdegen
2022-03-20  4:56                   ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-20  7:39                   ` hw
2022-03-20  8:08                     ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-22  7:06                       ` hw
2022-03-22 19:50                         ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-22 21:45                         ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-21  7:22               ` 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=YjcMS2WxhF6lIB3L@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=help-gnu-emacs@gnu.org \
    --cc=hw@adminart.net \
    /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).