Improve Tramp robustness

* lisp/net/tramp-sh.el (tramp-open-connection-setup-interactive-shell):
Check for `tramp-string-empty-or-nil-p'.

diff --git a/lisp/net/tramp-sh.el b/lisp/net/tramp-sh.el
index 2ef97d540a05972ab780c1b68b3c1447a4eaa6ce..2df3006c1d9ca296bb30d0efee25934ec05c5a18 100644 (file)
--- a/lisp/net/tramp-sh.el
+++ b/lisp/net/tramp-sh.el
@@ -4496,7 +4496,7 @@ process to set up.  VEC specifies the connection."
 
     ;; Set `remote-tty' process property.
     (let ((tty (tramp-send-command-and-read vec "echo \\\"`tty`\\\"" 'noerror)))
-      (unless (string-empty-p tty)
+      (unless (tramp-string-empty-or-nil-p tty)
        (process-put proc 'remote-tty tty)
        (tramp-set-connection-property proc "remote-tty" tty)))
 

diff --git a/lisp/net/tramp.el b/lisp/net/tramp.el
index eb4cb9ce082de76324465c38fd6c454d4da7b54e..3420bb76d144de4defc29bcdb624986075bb0374 100644 (file)
--- a/lisp/net/tramp.el
+++ b/lisp/net/tramp.el
@@ -4793,7 +4793,7 @@ Do not set it manually, it is used buffer-local in `tramp-get-lock-pid'.")
        (signal 'file-error `("Cannot remove lock file for" ,file)))
     ;; `userlock--handle-unlock-error' exists since Emacs 28.1.  It
     ;; checks for `create-lockfiles' since Emacs 30.1, we don't need
-    ;; this chweck here, then.
+    ;; this check here, then.
     (error (unless (or (not create-lockfiles)
                        (bound-and-true-p remote-file-name-inhibit-locks))
              (tramp-compat-funcall 'userlock--handle-unlock-error err)))))