[4674] in testers
Re: xalf and me
daemon@ATHENA.MIT.EDU (Greg Hudson)
Thu May 24 17:57:11 2001
Message-Id: <200105242156.RAA09191@egyptian-gods.MIT.EDU>
To: Bill Cattey <wdc@MIT.EDU>
cc: testers@MIT.EDU, aui@MIT.EDU
In-Reply-To: Your message of "Thu, 24 May 2001 21:42:39 -0000."
<Uv3M1D5z000151tEcC@mit.edu>
Date: Thu, 24 May 2001 17:56:58 -0400
From: Greg Hudson <ghudson@MIT.EDU>
> But when I type:
> xalf -n messages
> it starts just fine.
"xalf -n messages" is the same as just "messages".
You could also run xalf in "mapping mode", using the -m option, but
then any mapped window (including, say, a zephygram) would turn off
the indicator. Making mapping mode the default might still be a
better choice than disabling xalf in libgnome altogether.
> Specifying "-n messages" in the launcher properties doesn't work though.
Yes, because libgnome actually runs "xalf sh -c 'command'", more or
less.
If you want to disable xalf on a per-entry basis, you can give the
entry a command of "NO_XALF command". The faculty liaisons could use
this in the menus, but obviously users aren't going to know to do that
when making a launcher for a program compiled against old X libraries;
nor would they receive any kind of diagnostic which would suggest it.
> Is it possible that we've got a fixable xalf bug here?
Not really. The problem is pretty much impossible to solve.
