[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[elpa] master f05c908 6/7: multishell - reduce multishell-primary-name s
[elpa] master f05c908 6/7: multishell - reduce multishell-primary-name savehist extra fuss
Tue, 26 Jan 2016 16:58:18 +0000
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
multishell.el | 27 ++++++---------------------
1 files changed, 6 insertions(+), 21 deletions(-)
diff --git a/multishell.el b/multishell.el
index 8228ad0..dc20308 100644
@@ -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
-;;; 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
-;; (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)
- [elpa] master updated (ad2214a -> e7f3aa4), ken manheimer, 2016/01/26
- [elpa] master 0341f3e 1/7: multishell README.md - Add link to ELPA package entry., ken manheimer, 2016/01/26
- [elpa] master 96c6843 3/7: multishell - simplify multishell-start-shell-in-buffer, ken manheimer, 2016/01/26
- [elpa] master bd088d0 2/7: multishell - Refine documentation a bit., ken manheimer, 2016/01/26
- [elpa] master 423c41a 4/7: multishell - use eval-after-load when with-eval-after-load isn't around., ken manheimer, 2016/01/26
- [elpa] master 4d6a16a 5/7: multishell - save match-data whenever; relocate some helper funcs, ken manheimer, 2016/01/26
- [elpa] master f05c908 6/7: multishell - reduce multishell-primary-name savehist extra fuss,
ken manheimer <=
- [elpa] master e7f3aa4 7/7: multishell - merge code tidying, still on 1.0.8., ken manheimer, 2016/01/26