On Thu, Apr 25, 2013 at 09:44:24PM -0400, Michael Gogins wrote:
> At the Csound Conference 2011 we discussed default paths for Csound
> environment variables. This has not been implemented.
> 
> Is this still a good idea? If so, I will implement them.
> 
> I think it is a good idea. It would mean that on some systems, certainly
> Windows, environment and PATH variables could be set, but would not NEED to
> be set if things were found in standard locations.
> 
I don't think I'd like this.  I typically work in a project folder, and
I prefer all my files to end up and be read from there, so I leave the
variables unset.  I suspect that having to always use full paths or set
environment variable for each case would be much more of a pain.

This of course only applies to things like SADIR and SSDIR, which tend
to be project-specific.  Fixed folders, like OPCODEDIR, are another
matter and I agree would benefit from defaults.

Maybe an option '--use-defaults' or something, would be a good compromise?

	-- Pete --


------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net