I have thought for a while how clean it would be to store variables as files, similar to how functions are stored as files. Then you can read and change them outside Fish, even when Fish is not running. That's conceptually simpler, a form of init file. It also seems to me technically simpler to implement robustly than making sure the daemon does not die, etc.
But for the rest of the proposal, is there enough reason to do it? First, it may be more humane to have the user set variables explicitly; as you said this happens rarely. It may be that setting them automatically is not the right thing to do in many cases. If they are updated automatically, each Fish instance has to know where to get or send its updates, and configuring that may be too much overhead for most use cases. Also, if the network connection breaks, when it is re-established updates have to be merged and there may be conflicts. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
