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. Clive Darke Product Consultant QA-Xpertise Abbey Court, Eagle Way, Sowton, Exeter, EX2 7HY Email [EMAIL PROTECTED] Web www.qa-iq.com QA-Xpertise works with customers to transform business performance by developing the knowledge, skills and attitude of their people. From individual places on the most comprehensive range of technical, desktop, professional best practice and management & personal development courses, to bespoke learning programmes and services, QA-Xpertise is dedicated to meeting the extensive learning and development needs of organisations nationwide and across the world. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. QA-IQ Ltd. Rath House, 55-65 Uxbridge Road, Slough, Berkshire, SL1 1SG. QA-IQ Ltd. is a company registered in England with company registration number: 2413137 Xpertise Group PLC, Islington House, Brown Lane West, Leeds, Yorkshire, LS12 6BD Xpertise Group PLC is a company registered in England with company registration number: 675312 -----Original Message----- From: [EMAIL PROTECTED] on behalf of Tomás Smetana Sent: Fri 26/09/2008 13:38 To: [email protected] Subject: [ast-users] ksh/tcsh and variables with hyphen in name Hello, I'm having problem with tcsh/ksh interaction: tcsh allows an environment variable to contain a hyphen in its name, so the following would work in tcsh: setenv a-b foo However when starting ksh from tcsh such a variable is not visible in ksh's environment and it is not passed on when e.g. starting another tcsh instance from ksh. My question is: shouldn't be such variables tolerated in the environment? Thanks in advance for the answer. -- Tomás 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 -- Scanned by iCritical for Virus and Spyware
_______________________________________________ ast-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-users
