unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: Po Lu <luangruo@yahoo.com>,  Eli Zaretskii <eliz@gnu.org>,
	help-gnu-emacs@gnu.org
Subject: Re: Emacs in a Corporate Environment
Date: Sat, 15 Apr 2023 20:45:43 +0200	[thread overview]
Message-ID: <87a5z9f0h4.fsf@gmx.de> (raw)
In-Reply-To: <87edol5p2u.fsf@mbork.pl> (Marcin Borkowski's message of "Sat, 15 Apr 2023 14:04:25 +0200")

Marcin Borkowski <mbork@mbork.pl> writes:

Hi Marcin,

>> I think you're all missing the most obvious snafu (which has actually
>> gotten me in trouble with our security folks): auto-save files.
>
> Good point!  Is there a way to disable them wholesale on remote machines
> (when using TRAMP)?

From the Tramp manual (master branch):

--8<---------------cut here---------------start------------->8---
   Set ‘auto-save-file-name-transforms’ to ‘nil’ to save auto-saved
files to the same directory as the original file.

   Alternatively, set the user option ‘tramp-auto-save-directory’ to
direct all auto saves to that location.

   If you want to suppress auto-saving of remote files at all, set user
option ‘remote-file-name-inhibit-auto-save’ to non-‘nil’.
--8<---------------cut here---------------end--------------->8---

See (info "(tramp) Auto-save File Lock and Backup")

> TIA,

Best regards, Michael.



  parent reply	other threads:[~2023-04-15 18:45 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 [this message]
2023-04-15  6:10             ` Marcin Borkowski
2023-04-15 21:14             ` Björn Bidar
2023-04-16  7:51               ` Michael Albinus
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=87a5z9f0h4.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=mbork@mbork.pl \
    /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).