zsh-workers
 help / color / mirror / code / Atom feed
From: ZyX <kp-pav@yandex.ru>
To: Bart Schaefer <schaefer@brasslantern.com>,
	"zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: [Feature Request]: Globally updated Variables for all zsh instances for same user - just like fish shell
Date: Mon, 13 Jul 2015 18:17:22 +0300	[thread overview]
Message-ID: <3733861436800642@web20m.yandex.ru> (raw)
In-Reply-To: <150712154233.ZM5772@torch.brasslantern.com>

13.07.2015, 01:43, "Bart Schaefer" <schaefer@brasslantern.com>:
>   On Jul 12, 6:42pm, Zaxebo Yaxebo wrote:
>   }
>   } *"Fish Shell" has a feature known as universal variables, which allow a
>   } user to permanently assign a value to a variable across all the running
>   } fish shells of that user. The variable value is remembered across logouts
>   } and reboots, and updates in value are immediately propagated to all running
>   } shells.*
>
>   This was previously discussed in the thread starting here:
>
>   http://www.zsh.org/cgi-bin/mla/redirect?USERNUMBER=19431
>
>   The thread branches a bit but nobody suggested anything better than this:
>
>   http://unix.stackexchange.com/questions/137077/serialize-shell-variable-in-bash-or-zsh
>
>   We're almost certainly not going to implement the fish model of having a
>   background server process that all other shells can contact to receive
>   environment variable updates.



AFAIK there is no longer such a thing. I am not really following fish development, but recently I received github email with comment to one of my issues (https://github.com/fish-shell/fish-shell/issues/1257#issuecomment-120921485) and it contains, literally:

> @zanchey is this still slated for 3.0 or might we see 2.3, now that 2.2 is out and fishd is out of the picture (I'm not sure how the fishd.${HOST} file fits in now with fishd gone).

Highlight: “now with fishd gone”.

I failed to find GH issue that describes fishd death, but commit log shows that the death starts with https://github.com/fish-shell/fish-shell/commit/6a94b51cbadb8609580fac5c693c02ca4ab39734 (which is in 2.2 release).


  reply	other threads:[~2015-07-13 15:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-12 13:12 Zaxebo Yaxebo
2015-07-12 14:44 ` Christian Neukirchen
2015-07-12 22:42 ` Bart Schaefer
2015-07-13 15:17   ` ZyX [this message]
2015-07-13 16:59     ` Bart Schaefer
2015-07-13 18:04   ` Mikael Magnusson
2015-07-13 18:44     ` Bart Schaefer

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=3733861436800642@web20m.yandex.ru \
    --to=kp-pav@yandex.ru \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@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).