all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Multiple M-x shells sharing input ring
Date: Thu, 04 Sep 2014 17:09:45 -0400	[thread overview]
Message-ID: <jwvoauvksej.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: mailman.8284.1409864361.1147.help-gnu-emacs@gnu.org

> I don't see how anything in that description applies here.  Maybe
> the description is faulty.  Or maybe this variable should not be
> permanent-local.  But so far, the description does not seem (to me)
> to fit the `comint-input-history' case.

permanent-local is used to mark variables as pertaining to the content
of a buffer rather than to its mode.  The effect it has is that the
variable won't be reset if you change major mode (i.e. it's not
"killed" by kill-local-variables).

It's reasonably common in comint buffer to reset the major mode
(typically, you kill the process and re-run it which sets up the comint
mode again) and you generally want to preserve the input-history, hence
the `permanent-local' property.

Note also that the `permanent-local' property does not make a variable
buffer-local.  It just makes it stay local longer, in case it was
made local.


        Stefan


  parent reply	other threads:[~2014-09-04 21:09 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
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 [this message]
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=jwvoauvksej.fsf-monnier+gnu.emacs.help@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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.