Peder Stray <[EMAIL PROTECTED]> writes: > Dan Espen <[EMAIL PROTECTED]> writes: > > > > when i think about it $FVWM_INCLUDE would be really nice... that > > > way we could just set that variable depending on the users type > > > and location. > > > > If thats what you want, you already have it: > > > > Setenv X /usr/local/myconfig > > Read $[X] > > > > $X can be exported before Fvwm starts too. > > and the will seach the given path for files i include from the config? > > what i wanted $FVWM_INCLUDE to do was too add a directory to the > include path, after FVWM_USERDIR, before FVWM_DATADIR.
Well, you probably already realize that an environment variable can serve as a generalized read path, but: Setenv X /usr/local Read $[X]/myconfig In "myconfig": Read $[X]/anotherconfigfile ... Read $[X]/anotherconfigfile/inasubdirectory but I still think you should be looking at PipeRead. PipeRead will read configuration from anywhere you like and provides the necessary flexibility to tailor the Fvwm configuration as its read. -- Dan Espen 444 Hoes Lane Room RRC 1C-214 E-mail: [EMAIL PROTECTED] Piscataway, NJ 08854 Phone: (732) 699-5570 -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
