Gnus development mailing list
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Michael Ekstrand <michael@elehack.net>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: frame-environment
Date: Sat, 17 Jan 2009 20:59:02 -0500	[thread overview]
Message-ID: <jwv7i4twf8t.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87d4elfwcj.fsf@elehack.net> (Michael Ekstrand's message of "Sat,  17 Jan 2009 15:37:00 -0600")

> As I said, I have not taken the time to look in to this problem in depth
> yet; I've just been working around it.  I just saw the message here and
> wanted to make sure that these considerations were brought to light when
> deciding what to do with this functionality -- when we have multiple
> processes (with multiple environments and differing access to resources)
> functioning as one Emacs, situations can arise where the environment of
> the process a user is using to initiate a command is important.

Yes, we know about that, it was discussed for a while on this
very list.  It was the kind of motivation that brought the frame's
`environment' parameter.  But this functionality has not been fully
implemented and until this happens, I reverted it to the
previous behavior.  The problem being that while it's sometimes
convenient to use the emacsclient's environment, it can be the wrong
thing to do at other times.

So the emacsserver and emacsclient environments really need to be
"merged" somehow, and there might even be a need to change the way this
merge happens on different occasions.


        Stefan






  reply	other threads:[~2009-01-18  1:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <uprim2cmx.fsf@gnu.org>
     [not found] ` <87ocy596x4.fsf@cyd.mit.edu>
2009-01-17 21:37   ` frame-environment Michael Ekstrand
2009-01-18  1:59     ` Stefan Monnier [this message]
2009-01-18  4:11     ` frame-environment Eli Zaretskii

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=jwv7i4twf8t.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=michael@elehack.net \
    /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 NNTP newsgroup(s).