[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[elpa] master f05c908 6/7: multishell - reduce multishell-primary-name s

From: ken manheimer
Subject: [elpa] master f05c908 6/7: multishell - reduce multishell-primary-name savehist extra fuss
Date: Tue, 26 Jan 2016 16:58:18 +0000

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

    multishell - reduce multishell-primary-name savehist extra fuss
    I'm finding that preserving multishell-primary-name across sessions
    isn't so desirable, and thinking that the idea about including the value
    of savehist-additional-variables on savehist-additional-variables may
    not be either effective or necessarily useful, so removing the note
    about it.
 multishell.el |   27 ++++++---------------------
 1 files changed, 6 insertions(+), 21 deletions(-)

diff --git a/multishell.el b/multishell.el
index 8228ad0..dc20308 100644
--- a/multishell.el
+++ b/multishell.el
@@ -220,28 +220,13 @@ path) will be conveyed between emacs sessions."
 (defvar multishell-primary-name "*shell*"
   "Default shell name for un-modified multishell-pop-to-shell buffer target.
-This is adjusted by `multishell-pop-to-shell' when it is
-invoked (with doubled universal argument) to set the default.
-To track the current primary across emacs restarts, add the name
-of this variable to `savehist-additional-variables' by
-customizing the latter.")
-;;; Can't just add multishell-primary-name to savehist-additional-variables
-;;; - it'll be lost any time the user runs emacs without loading
-;;; multishell.  So instead, inform the user that they can customize
-;;; savehist-additional-variables.
-;;; I suspect that including savehist-additional-variables *on*
-;;; savehist-additional-variables could avoid this problem, as long as it
-;;; doesn't conflict with user customizations. However, even if that works,
-;;; doing so from multishell would change a behavior (for the better, but)
-;;; beyond multishell's scope, making the change hard to track down.
-;; (when (not (member 'multishell-primary-name
-;;                    savehist-additional-variables))
-;;   (setq savehist-additional-variables
-;;         (cons 'multishell-primary-name savehist-additional-variables)))
+This is set by `multishell-pop-to-shell' as the current default,
+when invoked with doubled universal argument.
+If you want the designated primary that you have at the end of
+one emacs session to be resumed at the next, customize
+`savehist-additional-variables' to include the
 ;; Multiple entries happen because completion also adds name to history.
 (defun multishell-register-name-to-path (name path)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]