From: "John Wiegley" <johnw@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Propagating local variables?
Date: Wed, 16 May 2018 11:59:06 -0700 [thread overview]
Message-ID: <m2r2mbtojp.fsf@newartisans.com> (raw)
In-Reply-To: <jwvvabnjynh.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Wed, 16 May 2018 13:34:41 -0400")
>>>>> "SM" == Stefan Monnier <monnier@iro.umontreal.ca> writes:
SM> I think most other "multi-buffer" packages tend to treat one of their
SM> buffers as a kind of "master" and have all others point to it, so they can
SM> lookup shared local variables via something like (buffer-local-value
SM> my-parent-buffer 'varname).
If you're the author of all the code that relates to that buffer, sure. But I
can't expect shell.el to reference the buffer-local `process-environment' of
my Coq buffer in order to setup the right PATH for that project-specific
sub-shell.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2018-05-16 18:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 19:37 Propagating local variables? John Wiegley
2018-05-16 3:42 ` Roland Winkler
2018-05-16 17:34 ` Stefan Monnier
2018-05-16 18:59 ` John Wiegley [this message]
2018-05-16 20:49 ` Stefan Monnier
2018-05-16 22:46 ` John Wiegley
2018-05-17 14:45 ` Stefan Monnier
2018-05-16 21:02 ` Roland Winkler
2018-05-17 3:00 ` Richard Stallman
2018-05-17 5:16 ` John Wiegley
2018-05-18 2:32 ` Richard Stallman
2018-05-18 4:28 ` John Wiegley
2018-05-18 20:15 ` Shea Levy
2018-05-19 3:19 ` Richard Stallman
2018-05-19 15:09 ` John Shahid
2018-05-20 3:19 ` Richard Stallman
2018-05-17 12:18 ` Shea Levy
2018-05-17 14:27 ` Clément Pit-Claudel
2018-05-18 2:33 ` Richard Stallman
2018-05-18 3:18 ` Stefan Monnier
2018-05-19 12:06 ` Philipp Stephani
2018-05-20 19:09 ` Clément Pit-Claudel
2018-05-19 12:11 ` Philipp Stephani
2018-05-19 19:12 ` Stefan Monnier
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=m2r2mbtojp.fsf@newartisans.com \
--to=johnw@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.