Is there a reason to have two files that are functionally equivalent namely
local/bin/sage-open local/bin/sage-osx-open and why are they slightly different than local/bin/sage-native-execute namely sage-native-execute replaces the variables whereas sage-open merely unsets them. Also they unset LIBRARY_PATH whereas sage-native- execute does not. If it causes problems for open shouldn't we have the same change in sage-native-execute? It seems as if calling `sage-native-execute open ...` would be nearly as easy as calling `sage-open ...` and cut down on maintenance assuming of course that they should be equivalent with regard to environment variables. I'd be happy to open a ticket and make the changes etc., but I'm not sure exactly what changes are safe to make. -Ivan --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
