From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Multiple M-x shells sharing input ring
Date: Thu, 04 Sep 2014 23:21:07 +0200 [thread overview]
Message-ID: <87ha0njd4s.fsf@web.de> (raw)
In-Reply-To: 6938458c-7116-458a-9e10-8397dfa5b25a@default
Drew Adams <drew.adams@oracle.com> writes:
> There are not only two alternatives: permanent-local and global.
> The normal way to handle what you describe is to make the variable
> local in each buffer where it should be local. It can even be made
> automatically local everywhere (`make-variable-buffer-local').
>
> And any mode derived from comint mode that happens to want a separate
> history can easily obtain that, even if the variable is not declared
> automatically local. Nothing prevents scheme mode or whatever from
> doing `make-buffer-local' in its buffers. That's the usual way these
> things are done.
Yes, but if you want to have a shared input history for all shell
buffers, and another shared history for all interactive scheme buffers,
using a global var is not good enough either.
> AFAICT, `permanent-local' is for a different purpose. At least its
> doc claims that. It speaks specifically of "the file". Again:
>
> Permanent locals are appropriate for data pertaining to where the
> file came from or how to save it, rather than with how to edit the
> contents.
>
> I don't see how anything in that description applies here.
It doesn't say that it's inappropriate for all other cases ;-)
> > It's not that easy, since `comint-mode' does a lot of explicit
> > `make-local-variable' calls including for `comint-input-ring'.
>
> Why would it do that, if the variable is already permanent-local?
> Doesn't permanent-local imply buffer-local?
I think no:
(put 'foo 'permanent-local t)
(setq foo 1)
(local-variable-p 'foo)
==> nil
(make-local-variable 'foo)
(setq foo 2)
(local-variable-p 'foo)
==> t
(kill-all-local-variables)
(local-variable-p 'foo)
==> t
> And even if it does that, that just makes the variable buffer-local.
> What prevents one from then killing that local variable and using
> the global one instead?
Nothing, but I just think a per-mode input history could be more useful.
Michael.
next prev parent reply other threads:[~2014-09-04 21:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 8:54 Multiple M-x shells sharing input ring Joseph Xu
2014-09-04 14:58 ` Subhan Michael Tindall
2014-09-04 15:55 ` Joseph Xu
2014-09-04 19:46 ` Michael Heerdegen
2014-09-04 20:09 ` Drew Adams
2014-09-04 20:40 ` Michael Heerdegen
2014-09-04 20:58 ` Drew Adams
2014-09-04 21:21 ` Michael Heerdegen [this message]
2014-09-04 21:33 ` Drew Adams
2014-09-05 7:33 ` Joseph Xu
[not found] ` <mailman.8284.1409864361.1147.help-gnu-emacs@gnu.org>
2014-09-04 21:09 ` Stefan Monnier
2014-09-04 21:20 ` Drew Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ha0njd4s.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.