From: Michael Weller (eowmob@exp-math.uni-essen.de)
Date: Fri 03 Apr 1998 - 13:12:14 IDT
On Fri, 3 Apr 1998, 101 wrote: > > > On Fri, 3 Apr 1998, Michael Weller wrote: > > > On Fri, 3 Apr 1998, 101 wrote: > > > > While true, I'd still appreciate if there remained the enviroment variable > > (maybe in addition to .svgalibrc). This way you can easily write a script > > calling squake after setting GSVGACONFIG. s.t. you can have certain > > settings be active ONLY for squake, say. This is much more difficult with > > ..svgalibrc . > > Yep. You are right. But how can you put newlines in the GSVGACONFIG env > variable ? Well, in theory something like: GSVGACONFIG=blabla\ blabla or GSVGACONFIG='blabla blabla' (Note, something like echo "$GSVGACONFIG" is needed to make echo NOT transform the newline to a space if you wanna see it's really two lines.. well actually its the shell that does that transformation.. but anyway.) should work. Apart from that, you simply don't put newlines in there. The config commands for svgalib can happily all be in one line. The config file/env variable parser is really a kitchen sink. Which also means it silently ignores anything unknown to him. (which is in a sense required because the file is first read by vga.c and then as a whole again by the chipset driver..). Hmm, no I never said all this is really perfect. Michael. -- Michael Weller: eowmob@exp-math.uni-essen.de, eowmob@ms.exp-math.uni-essen.de, or even mat42b@spi.power.uni-essen.de. If you encounter an eowmob account on any machine in the net, it's very likely it's me.
This archive was generated by hypermail 2.1.4 : Wed 21 Jan 2004 - 22:10:22 IST