From 304d022a66f2c71ee643021db69c1c99d135df55 Mon Sep 17 00:00:00 2001 From: Michael Albinus Date: Tue, 8 Oct 2019 15:41:00 +0200 Subject: [PATCH] * etc/PROBLEMS: Describe navigation problem from Nautilus. (Bug#37573) * lisp/userlock.el (create-lockfiles): Set `safe-local-variable' property. --- etc/PROBLEMS | 17 +++++++++++++++++ lisp/userlock.el | 3 +++ 2 files changed, 20 insertions(+) diff --git a/etc/PROBLEMS b/etc/PROBLEMS index c0d30ae5b44..504570e911b 100644 --- a/etc/PROBLEMS +++ b/etc/PROBLEMS @@ -1183,6 +1183,23 @@ always) doesn't insert the whitespace of the killed and yanked line. The solution is to set the GPaste "trim items" option to OFF. +*** Gnome: Navigation from Nautilus to remote files. + +If you navigate to a file, which belongs to a remote server, in +Nautilus via "Open With Emacs" you might not be able to save this file +once you have modified it in Emacs. The reasons for the failure can +vary, and for some connection methods saving the file might even succeed. + +If the remote connection in Nautilus uses ssh or sftp, you could +mitigate the problem by the following lines in your .emacs file: + +(dir-locals-set-class-variables 'gvfs '((nil . ((create-lockfiles . nil))))) +(dir-locals-set-directory-class (format "/run/user/%d/gvfs" (user-uid)) 'gvfs) + +A better approach might be to avoid navigation from Nautilus to Emacs +for such files, and instead to open the file in Emacs using Tramp +remote file name syntax. + *** KDE: When running on KDE, colors or fonts are not as specified for Emacs, or messed up. diff --git a/lisp/userlock.el b/lisp/userlock.el index f077bc9ad62..209768620c1 100644 --- a/lisp/userlock.el +++ b/lisp/userlock.el @@ -34,6 +34,9 @@ (eval-when-compile (require 'cl-lib)) +;;;###autoload +(put 'create-lockfiles 'safe-local-variable 'booleanp) + (define-error 'file-locked "File is locked" 'file-error) ;;;###autoload -- 2.30.2