On Fri, 26 Sep 2008 14:17:51 +0100 <[EMAIL PROTECTED]> wrote: > There are plenty of other characters allowed: > > setenv 'h e h e' foo > > The environment block is just text, I don't think you can really stop > characters other than '=' and 0x00 begin used. >
OK. But it's not exactly what I was asking about. My problem is that ksh removes those variables from the environment. I should probably explain the issue better. Assume I'm in a tcsh session: # setenv a-b foo # printenv | grep foo a-b=foo Now i start ksh: # ksh # printenv | grep foo # i.e., the variable a-b is not present in the ksh environment even though it was set in the parent shell (tcsh) which means ksh altered the environment and I think this is wrong since POSIX suggests the application should tolerate such variables (at least some other shells like bash do). Regards. -- Tomáš Smetana Sr. Software Maintenance Engineer, Red Hat RH IRC: #brno #devel #base-os #seg-team; Freenode IRC: #fedora-devel _______________________________________________ ast-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-users
