* etc/PROBLEMS: Describe navigation problem from Nautilus. (Bug#37573)

* lisp/userlock.el (create-lockfiles): Set `safe-local-variable' property.

diff --git a/etc/PROBLEMS b/etc/PROBLEMS
index c0d30ae5b44c0d087d4c7754560d57ecf501f122..504570e911b569bd1ebdd64486ed5ac046ff9a9e 100644 (file)
--- 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 f077bc9ad62aa8f5457e52701e996901a1e0e826..209768620c1d5bb9761304d4695caf8e5f3fd865 100644 (file)
--- 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