From: Jean Louis <bugs@gnu.support>
To: hw <hw@adminart.net>
Cc: Help GNU Emacs <help-gnu-emacs@gnu.org>
Subject: Re: auto-save directory?
Date: Sat, 19 Mar 2022 08:30:18 +0300 [thread overview]
Message-ID: <YjVqalSQD9gG0CFy@protected.localdomain> (raw)
In-Reply-To: <e2aab671ad0329169ecc077c8c6992617a3cc6bb.camel@adminart.net>
* hw <hw@adminart.net> [2022-03-19 07:07]:
>
> Hi,
>
> I'm wondering if there is a way to have emacs put all auto-save files
> into a configurable directory. We can set `tramp-auto-save-directory`,
> but there doesn't seem an equivalent option for files that are not
> remote. I couldn't find one in either the documentation, nor the source.
>
> I'd find it nicer to have all auto-save files in one place instead of
> all over the place. Is there such an option, and if there isn't, would
> that be worth making a feature request?
> ‘auto-save-file-name-transforms’
>
Evaluate this below to get into Info file:
(info "(emacs) Auto Save Files")
The variable ‘auto-save-file-name-transforms’ allows a degree of
control over the auto-save file name. It lets you specify a series of
regular expressions and replacements to transform the auto save file
name. The default value puts the auto-save files for remote files
(*note Remote Files::) into the temporary file directory on the local
machine.
On my side the variable ‘auto-save-file-name-transforms’ looks as
this:
[INS] [DEL] List:
Regexp: \`/[^/]*:\([^/]*/\)*\([^/]*\)\'
Replacement: /home/data1/protected/tmp/\2
Uniquify: [Toggle] on (non-nil)
or as this:
auto-save-file-name-transforms ⇒ (("\\`/[^/]*:\\([^/]*/\\)*\\([^/]*\\)\\'" "/home/data1/protected/tmp/\\2" t))
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2022-03-19 5:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 4:06 auto-save directory? hw
2022-03-19 5:30 ` Jean Louis [this message]
2022-03-20 9:27 ` hw
2022-03-19 6:10 ` tomas
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=YjVqalSQD9gG0CFy@protected.localdomain \
--to=bugs@gnu.support \
--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).