On 12:35 26 Jun 2002, Vineet Kumar <[EMAIL PROTECTED]> wrote: | * Peter T. Abplanalp ([EMAIL PROTECTED]) [020626 12:29]: | > > I don't know if the --command option for gnome-terminal causes a | > > different environment to be set. And if so if it's a feature or a | > > bug. After searching faqs, checking manuals and browsing bugzillas, | > > I give up. Would some kind soul shed some light on my frustrating | > > situation? | > i don't know why this is happening but why not try: | > gnome-terminal --command ". /home/<logname>/.bashrc;mutt" | I'm guessing this wouldn't work, as "." is a shell builtin. If | gnome-terminal were running the command in a shell, $OP wouldn't have | the problem in the first place!
No: .bashrc is _interactive_ shells only. | A better suggestion (As David T-G gave) is to get that environment | variable in your parent process' environment, maybe with ~/.Xsession or | similar. This is indeed a better suggestion, regardless of the above. -- Cameron Simpson, DoD#743 [EMAIL PROTECTED] http://www.zip.com.au/~cs/ >From a programmer's point of view, the user is a peripheral that types when you issue a read request. - Peter Williams
