That's a good point. Ben H and I are talking about it now and we have an alternative actually ... we can use the "emit" function in fish. e.g. in the Bash script: `fish -c emit rvm_state_changed`
In fish we can register a function to listen for this event like so: function rvm_changed --on-event rvm_state_changed # parse some files or change some symlinks or something end I am not sure how this will help the isolated environment issue, but it might be worth exploring nonetheless for a *clean* implementation of fish support. On Thu, Sep 10, 2009 at 12:38 PM, Clifford Heath <[email protected]>wrote: > > On 10/09/2009, at 11:37 AM, Bodaniel Jeanes wrote: > > As such, RVM COULD actually set environment variables for fish by > > starting an instance and setting a global variable which, from what > > I read, should be available to ALL other sessions... right? > > Don't forget that the reason why RVM as a bash function is cool is > because > it *doesn't* change global state; it affects this shell instance > *only*, so that > any stuff you have running in other shells is unaffected. > > Clifford Heath. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~----------~----~----~----~------~----~------~--~---
