zsh-users
 help / color / mirror / code / Atom feed
From: Kurtis Rader <krader@skepticism.us>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: export
Date: Tue, 25 Nov 2014 21:38:55 -0800	[thread overview]
Message-ID: <CABx2=D8NhjWMA6rjop4vmi77jC4bDKSsBbvP-hs0w8N0b9_cww@mail.gmail.com> (raw)
In-Reply-To: <54756216.2070004@eastlink.ca>

[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]

No, it is not possible on UNIX like operating systems (which include
Microsoft Windows) for "export" to "work between" xterms or any other set
of programs. When you execute the "export" or "typeset -x" command in a zsh
process it can only modify the environment for that zsh process.

On Tue, Nov 25, 2014 at 9:16 PM, Ray Andrews <rayandrews@eastlink.ca> wrote:

> On 11/25/2014 08:54 PM, Kurtis Rader wrote:
>
>> If by "fake it" you mean cooperative processes that implement a protocol
>> for exchanging environment variables then, yes, you can achieve the result
>> desired by Ray. However I think that everyone trying to achieve this
>> result
>> wants to do so without having to implement a new data exchange protocol in
>> every program. If they were willing to implement a private data exchange
>> protocol they wouldn't be asking this question. :-)
>>
>
> As it is, I pass some variables between running shells all the time in
> 'preexec()'.
> Specifically every shell in every xterm knows the current directory of
> every
> other so I can do: " cp foo $t4 " with ' $t4 ' being the current dir in
> xterm #4.
>
> But that's not the problem, I just want 'export' to work between xterms if
> possible.
> It's hardly important tho.
>
>


-- 
Kurtis Rader
Caretaker of the exceptional canines Junior and Hank

  reply	other threads:[~2014-11-26  5:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26  0:57 export Ray Andrews
2014-11-26  2:36 ` export Eric Cook
2014-11-26  2:58 ` export Kurtis Rader
2014-11-26  4:32 ` export Bart Schaefer
2014-11-26  4:54   ` export Kurtis Rader
2014-11-26  5:16     ` export Ray Andrews
2014-11-26  5:38       ` Kurtis Rader [this message]
2014-11-26  5:07   ` export Ray Andrews
2014-11-26  5:43     ` export Kurtis Rader
2014-11-26  5:54       ` export Kurtis Rader
2014-11-26 17:43       ` export Ray Andrews
2014-11-26 18:26         ` export Павлов Николай Александрович
2014-11-26 18:45           ` export Ray Andrews
2014-11-26  5:50     ` export Павлов Николай Александрович
2014-11-26  6:21     ` export Kurtis Rader
     [not found]   ` <CABx2=D_zLTkdFsV+eT-VrwwaJQYr=1JeZF0eNqH44saPDYMD7Q__49907.9755544246$1416977797$gmane$org@mail.gmail.com>
2014-11-26  7:18     ` export Stephane Chazelas
2014-11-26 13:37       ` export Clint Hepner
2014-11-26  9:27 ` export Peter Stephenson

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='CABx2=D8NhjWMA6rjop4vmi77jC4bDKSsBbvP-hs0w8N0b9_cww@mail.gmail.com' \
    --to=krader@skepticism.us \
    --cc=rayandrews@eastlink.ca \
    --cc=zsh-users@zsh.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 public inbox

	https://git.vuxu.org/mirror/zsh/

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).