[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: all xterms



On Mon, Nov 01, 1999 at 10:43:02AM -0500, Brian Mays wrote:
> > On Mon, Nov 01, 1999 at 09:45:25AM -0500, Brian Mays wrote:
> >
> > > (...) What happens to your script if xterm isn't installed and your
> > > special environment variable isn't set? (...)
> 
> Tomasz Wegrzanowski <maniek@beer.com> added:
> 
> > Exactly the same what will happen now when you will chose x terminal
> > emulator from wmaker(by icon) or blackbox(by rightclick) without
> > having xterm(1x) But simply setting variable saves you in such
> > situation then.
> 
> The current situation is caused by the menu package running xterm
> instead of x-terminal-emulator.  This is fixed by correcting this bug
> in the menu package.  Your script, however, still does not work in our
> hypothetical situation after the menu package has been fixed, unless the
> environmental variable is set.

Not only menuing system. Two places Ive meant have nothing to do with menu system.
They are xwm-specific. And how do you want to fix alternatives to handle
another xterm for every user ? sensible-xterm is the much easier way, causing
less bugs.
BTW : Is anything using x-terminal-emulator ?

--- start sensible-xterm v0.2 ---
#!/bin/bash
shopt -s execfail
exec ${XTERM:-x-terminal-emulator} "$@"
exec xterm "$@"
echo "Couldn't find an xterm!" 1>&2
echo "Set the \$XTERM environment variable to your desired editor." 1>&2
exit 1
--- end ---

Now this is the most robust way to run x terminal emulator


Reply to: