unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: how to force auto-save of buffers not visiting files, right now?
Date: Sun, 20 Mar 2022 05:56:18 +0100	[thread overview]
Message-ID: <87a6dlrzm5.fsf@zoho.eu> (raw)
In-Reply-To: 8735jd5v9s.fsf@web.de

Michael Heerdegen wrote:

>> For example, I may edit a file '/usr/local/bin/example.pl'
>> which is owned by foo:foo because I made that so.
>> The directory '/usr/local/bin/' is owned by root. How do
>> you expect emacs to create a backup file there? For remote
>> files, I have set tramp-auto-save-directory to a local
>> directory, and I'm missing an equivalent option for
>> local files.
>
> I'm was talking about backup files, not about auto save.
> You can control where these are saved.

auto-save, `temporary-file-directory' ?
backup, `backup-directory-alist' ?

Never used any actively so don't know for sure ...

You can obviously "control" both/any/all in Emacs :)

> What kind of solution d you want to have? I find some of
> your answers contradicting, e.g. you say you don't want lots
> of backups because you don't want to delete them manually.
> But automatic deletion is also not good because ...

1. Keep files small.

X. Backup files don't take any disk space in any order
   of significance.

2. Backups should be set up to be kept out of the way
   automatically - or "not selected for the ACTUAL way when
   push comes to shove" - or ... well, whatever, only this
   should just work and be automated, so spend time to get it
   right OR be happy to live on the edge with no backups.
   Because there's no WAY in between!

... uhm, what's the right answer again?

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2022-03-20  4:56 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
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 [this message]
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=87a6dlrzm5.fsf@zoho.eu \
    --to=help-gnu-emacs@gnu.org \
    --cc=moasenwood@zoho.eu \
    /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).