Michel Schinz <Michel.Schinz@epfl.ch> writes:
> Martin Gasbichler <firstname.lastname@example.org> writes:
>> I'm also thinking about installing the program scsh-config that
>> prints some installation related informations to stdout. scsh-config
>> is currently simply generated in the top-level of the build
>> directory but not installed in $prefix/bin. At least scx, our
>> library for accessing Xlib, could make use of scsh-config but I'm
>> not sure if it is generally useful at the moment. Opinions?
> I think it's generally useful to have that, yes. I wonder, however, if
> this could not be simply integrated in scsh itself, via some new
> options (say "scsh -config ..."). I tend to prefer that solution
> simply because it puts one less executable in the path, but that's a
I wonder why other people did not choose this way but provided
> Now that I think about it, why not do the following:
> - make all configuration parameters accessible in scsh through
> variables or functions,
What exactly do you mean by configuration parameter? The variables
substituted into the Makefile by configure or more complex stuff like
the output of scsh-config --libs?
> - provide a new option for scsh, say -p, which evaluates an
> expression, print its result and then exit (i.e. does what -c
> does, but additionaly print the result of the evaluation).
> That way, instead of writing
> scsh-config --libs
> one could write
> scsh -p scsh-config-libs
So all you would save by adding another command line option instead of
using the -c option is a call to DISPLAY? That sounds like a waste of
command line options to me...