Subject:
|
Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Fri, 13 Feb 2004 14:57:18 GMT
|
Viewed:
|
4045 times
|
| |
|
|
In lugnet.cad.dev, Steve Bliss wrote:
> In lugnet.cad.dev, Don Heyse wrote:
> > Anyhow, the unix PATH variable uses ':' as the delimiter (at least
> > with the bash shell). So maybe '|' is better, even though you need
> > to use quotes when setting the environment variable to avoid it being
> > interpreted as a pipe. Is there any other character that's illegal
> > in a directory name, but doesn't require quotes to get it into an
> > environment variable?
>
> Perhaps the delimiter character needs to be platform dependent? I
> realize that's not an ideal solution for programs. But I don't
> think people will be shipping LDraw search path settings between
> OS's, so it would be alright for users.
>
> I don't think using the pipe character would be a good choice, for
> Windows or for Linux (and Mac I guess). For Windows (and DOS), the
> semi-colon has a *strong* precedent for use in path lists / search
> paths. Colon would not work at all for Windows, but seems to be the
> character of choice for path lists in Linux/Mac.
I disagree with the idea of platform specific solutions, especially
since we're now thinking about including extra information in the list
(such as directives to hide certain paths) to make it more compatible
with the list used by MLCAD. If it's not exactly a list of paths,
perhaps we shouldn't make it look like one. In fact, maybe we should
use a completely different, yet familiar format like XML to describe
this list. I just don't want it to be too wordy and bloat the
environment.
I was initially squeamish about the pipe symbol because it requires
quotes to avoid being interpreted as a pipe directive. However, times
change. Filenames with spaces require quotes already so it's not such
a big deal anymore. Plus the semicolon approach is now broken, since
you can create filenames containing semicolons in Windows. I think
the benefits of writing one parser and one set of instructions
outweigh any perceived drawbacks. Besides, unsophisticated users will
probably use a GUI to set this path anyways.
Don
|
|
Message is in Reply To:
 | | Re: LDRAWPREDIRS LDRAWPOSTDIRS - additional search paths
|
| (...) Perhaps the delimiter character needs to be platform dependent? I realize that's not an ideal solution for programs. But I don't think people will be shipping LDraw search path settings between OS's, so it would be alright for users. I don't (...) (21 years ago, 13-Feb-04, to lugnet.cad.dev)
|
132 Messages in This Thread:
(Inline display suppressed due to large size. Click Dots below to view.)
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
