[elpa] master cb35c72 1/3: multishell - Remove notes about tramp remote+sudo+homedir+sudo prob

[ken manheimer]

branch: master
commit cb35c72c3ce027994352b42f3c6f027ccc5b6770
Author: Ken Manheimer <address@hidden>
Commit: Ken Manheimer <address@hidden>

    multishell - Remove notes about tramp remote+sudo+homedir+sudo prob
    
    Apparently it's due to something in my local site configuration. The
    problem happens reliably in emacs started with -q, but I can't get it to
    happen if emacs was started with -Q.
    
    Unfortunately, I don't get a traceback, even with tramp-verbose=6, when
    the problem occurs, only "Selecting deleted buffer", and in *Messages*,
    "byte-code: Selecting deleted buffer". Nothing more happens if
    debug-on-error and debug-on-signal are set. This seems to suggest that
    something is swallowing the signal, yet still returning to
    top-level. Elusive.
---
 multishell.el |   30 ++++++------------------------
 1 files changed, 6 insertions(+), 24 deletions(-)

diff --git a/multishell.el b/multishell.el
index 65afc4c..8c16f16 100644
--- a/multishell.el
+++ b/multishell.el
@@ -3,7 +3,7 @@
 ;; Copyright (C) 1999-2016 Free Software Foundation, Inc. and Ken Manheimer
 
 ;; Author: Ken Manheimer <address@hidden>
-;; Version: 1.0.6
+;; Version: 1.0.7
 ;; Created: 1999 -- first public availability
 ;; Keywords: processes
 ;; URL: https://github.com/kenmanheimer/EmacsMultishell
@@ -54,16 +54,12 @@
 ;; [the multishell repository](https://github.com/kenmanheimer/EmacsMultishell)
 ;; issue tracker to report problems, suggestions, etc.
 ;;
-;; (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:
 ;;
+;; * 2016-01-23 1.0.7 Ken Manheimer:
+;;   - Remove notes about tramp remote+sudo+homedir problem. Apparently it's
+;;     due to something in my local site configuration (happens with -q but
+;;     not -Q).
 ;; * 2016-01-22 1.0.6 Ken Manheimer:
 ;;   - Add multishell-version function.
 ;;   - Tweak commentary/comments/docstrings.
@@ -76,16 +72,12 @@
 ;;     (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|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:
 ;;
-;; * Isolate tramp's sporadic failure to connect to remote|sudo+homedir
-;;   syntax
-;;   (eg, /ssh:xyz.com|sudo:address@hidden: or 
/ssh:xyz.com|sudo:address@hidden:~)
 ;; * Find suitable, internally consistent ways to tidy completions, eg:
 ;;   - first list completions for active shells, then present but inactive,
 ;;     then historical
@@ -102,7 +94,7 @@
 (require 'shell)
 (require 'savehist)
 
-(defvar multishell-version "1.0.6")
+(defvar multishell-version "1.0.7")
 (defun multishell-version (&optional here)
   "Return string describing the loaded multishell version."
   (interactive "P")
@@ -337,16 +329,6 @@ 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.
 
-\(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
 history but will not take effect for an already-running shell.