multishell - still 1.0.6, clarify conditions for tramp homedir bug

[gnu-emacs-elpa] / packages / multishell / multishell.el

diff --git a/packages/multishell/multishell.el b/packages/multishell/multishell.el
index 8aea919464ebfcc6967ca99eb4d69f32607704ed..65afc4c4705107d090459853c475c0f0c1e3a12b 100644 (file)
--- a/packages/multishell/multishell.el
+++ b/packages/multishell/multishell.el
@@ -54,13 +54,13 @@
 ;; [the multishell repository](https://github.com/kenmanheimer/EmacsMultishell)
 ;; issue tracker to report problems, suggestions, etc.
 ;;
 ;; [the multishell repository](https://github.com/kenmanheimer/EmacsMultishell)
 ;; issue tracker to report problems, suggestions, etc.
 ;;

-;; (NOTE - tramp sometimes fails to open a remote shell when pointed at a
-;; homedir, eg `/ssh:example.net:` or `/ssh:example.net:~`. Once it fails
-;; for a shell path, that path won't work for the rest of the
-;; session. Non-homedir remote access isn't disrupted. You can always work
-;; around this by switching to an explicit, non-homedir remote path when
-;; the problem occurs, and then cd'ing to wherever, including your homedir,
-;; in the remote shell.)
+;; (NOTE - tramp sometimes fails to open specifically a remote shell to
+;; sudo to a homedir, eg `/ssh:example.net|sudo:root:` or
+;; `/ssh:example.net|sudo:root:~`. Once it fails for a specific path, that
+;; path won't work for the rest of the session. Non-homedir remote access
+;; isn't disrupted. You can always work around this by switching to an
+;; explicit, non-homedir remote path when the problem occurs, and then
+;; cd'ing to wherever, including your homedir, in the remote shell.)

 ;;
 ;; Change Log:
 ;;
 ;;
 ;; Change Log:
 ;;


@@ -76,14 +76,14 @@
 ;;     (Currently the only UI mechanism to remove history entries.)
 ;;   - Fix - prevent duplicate entries for same name but different paths
 ;;   - Fix - recognize and respect tramp path syntax to start in home dir
 ;;     (Currently the only UI mechanism to remove history entries.)
 ;;   - Fix - prevent duplicate entries for same name but different paths
 ;;   - Fix - recognize and respect tramp path syntax to start in home dir

-;;     - But tramp bug, remote w/empty path (homedir) often fails, gets wedged.
+;;     - But tramp bug, remote|sudo to homedir, often fails, gets wedged.

 ;;   - Simplify history var name, migrate existing history if any from old name
 ;; * 2016-01-04 1.0.4 Ken Manheimer - Released to ELPA
 ;; * 2016-01-02 Ken Manheimer - working on this in public, but not yet released.
 ;;
 ;; TODO:
 ;;
 ;;   - Simplify history var name, migrate existing history if any from old name
 ;; * 2016-01-04 1.0.4 Ken Manheimer - Released to ELPA
 ;; * 2016-01-02 Ken Manheimer - working on this in public, but not yet released.
 ;;
 ;; TODO:
 ;;

-;; * Isolate tramp's sporadic failure to connect to remote+homedir (empty path)
+;; * Isolate tramp's sporadic failure to connect to remote|sudo+homedir

 ;;   syntax
 ;;   (eg, /ssh:xyz.com|sudo:root@xyz.com: or /ssh:xyz.com|sudo:root@xyz.com:~)
 ;; * Find suitable, internally consistent ways to tidy completions, eg:
 ;;   syntax
 ;;   (eg, /ssh:xyz.com|sudo:root@xyz.com: or /ssh:xyz.com|sudo:root@xyz.com:~)
 ;; * Find suitable, internally consistent ways to tidy completions, eg:


@@ -337,14 +337,15 @@ emacs activities, like dired, will seamlessly be in the auspices
 of the target account, and relative to the current directory, on
 the host where the shell is running.
 
 of the target account, and relative to the current directory, on
 the host where the shell is running.
 

-\(NOTE that there is a problem with specifying a remote homedir
-using tramp syntax, eg '/ssh:example.net:'. That sometimes fails
-on an obscure bug. Once it fails for a shell path, that path
-won't work for the rest of the session. You can always work
-around this by switching to an explicit, non-homedir remote path
-when the problem occurs, and then cd'ing to wherever, including
-your homedir, in the remote shell. Non-homedir initial paths
-aren't disrupted.)
+\(NOTE - tramp sometimes fails to open specifically a remote shell
+to sudo to a homedir, eg `/ssh:example.net|sudo:root:` or
+`/ssh:example.net|sudo:root:~`. Once it fails for a specific
+path, that path won't work for the rest of the
+session. Non-homedir remote access isn't disrupted. You can
+always work around this by switching to an explicit, non-homedir
+remote path when the problem occurs, and then cd'ing to wherever,
+including your homedir, in the remote shell. Non-homedir initial
+paths aren't disrupted.)

 
 You can change the startup path for a shell buffer by editing it
 at the completion prompt. The new path will be preserved in
 
 You can change the startup path for a shell buffer by editing it
 at the completion prompt. The new path will be preserved in


@@ -604,7 +605,7 @@ and path nil if none resolved."
            (signal (car err)
                    (list
                     (format "%s, %s (\"%s\")"
            (signal (car err)
                    (list
                     (format "%s, %s (\"%s\")"

-                            "Tramp shell can fail on empty (homedir) path"
+                            "Tramp shell can fail on remote|sudo to homedir"

                             "please try again with an explicit path"
                             (cadr err))))
          (signal (car err)(cdr err)))))
                             "please try again with an explicit path"
                             (cadr err))))
          (signal (car err)(cdr err)))))