From: Michael Heerdegen <michael_heerdegen@web.de>
To: Drew Adams <drew.adams@oracle.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Multiple M-x shells sharing input ring
Date: Thu, 04 Sep 2014 22:40:48 +0200 [thread overview]
Message-ID: <87bnqvktkf.fsf@web.de> (raw)
In-Reply-To: <7fba0cb5-c7a9-40ef-9de4-3191a6c52f3a@default> (Drew Adams's message of "Thu, 4 Sep 2014 13:09:42 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
> Too bad that `comint-input-ring' is "permanent local".
> Should it be, or is that a bug?
The variable is made local in the comint code with
`make-local-variable'.
Since very different modes are based on comint, making such vars
permanently local seems ok in this case. You probably don't want to
share an input history between a shell and a scheme buffer. Using a
global variable is not a good idea here.
> It does not sound to me like `comint-input-ring' fits that description
> at all.
>
> Anyway, presumably you could remove its permanent-local status, by
> removing property `permanent-local' from symbol `comint-input-ring'.
>
> Then you should be able to use `kill-local-variable', to have all
> comint buffers share the same variable (value). (Dunno whether that
> is what is what Joseph wants.)
It's not that easy, since `comint-mode' does a lot of explicit
`make-local-variable' calls including for `comint-input-ring'.
Michael.
next prev parent reply other threads:[~2014-09-04 20:40 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 [this message]
2014-09-04 20:58 ` Drew Adams
2014-09-04 21:21 ` Michael Heerdegen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bnqvktkf.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=drew.adams@oracle.com \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).