#43798: .cshrc - setenv path not in quotes ----------------------------------+-------------------------------- Reporter: joseph.montibello@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.2.1 Resolution: | Keywords: Port: | ----------------------------------+-------------------------------- Comment (by ryandesign@…): Replying to [ticket:43798 joseph.montibello@…]:
I think this setenv was causing the problem because my local $PATH setting has escaped space characters in it, and the whole thing is enclosed in quotes. I think this problem would be solved if macports would simply wrap its setenv PATH in quotes:
You're quite right, we should fix that. It applies not only to PATH but also MANPATH, and not only to tcsh but also bash. We could simply quote all environment variables we set, since there's a function we call to write an environment variable to the shell startup file. Note that it is somewhat unusual to install programs in paths that contain spaces and then set that in PATH. Particularly, autotools-based build systems will not work when the path contains spaces, and the developers of autotools consider that a user error and not a program bug. So there's a limited set of software that you could install in such a path anyway. -- Ticket URL: <https://trac.macports.org/ticket/43798#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X