On Sat, 07 May 2005 22:08:33 +0100, Thomas Adam wrote
(<[EMAIL PROTECTED]>):
>
> --- Felix Karpfen <[EMAIL PROTECTED]> wrote:
>> It would help at least one novice to have an example of an entry in the
>> (personal) configuration file that shows how to make a routinely used
>> menu into a permanen
This solution is application-specific, but what i do is include the
working directory in the xterm titlebar. And then do this separately for
other applications in which i want more information, for instance.
.bashrc:
case $TERM in
xterm*)
TITLEBAR='\[\033]0;xterm:\w\007\]'
hi guys:
I use Alt+tab in FVWM to switch between windows. the problem that
bothers me is that there is too little information showing in the
windowlist, for example, all xterm windows just show "xterm". so I do
not know which xterm window is the one I want to go to. it would be
more informa
On 09 May 2005 10:52:08 +0100, Nick Fortune wrote:
>
> I'm tending towards saying "create a directory $FVWM_USERDIR/perl and
> put the .pm files in there" and then pointing the script at the modules
> with a "use lib" directive. The trouble is that's fragile. If I
> hardcode the location and they
Greetings, All.
I'd like to ask the advice of this list's readers. I'm writing a module in
Perl. More to the point, I'm writing a HowTo about writing modules in Perl,
and I'd like my doc to reflect something approaching best practice.
The thing is that the code is approaching that level of comp
Hi there,
On 06 May 2005 at 18:59:56 -0400, Dan Espen wrote:
> don fisher <[EMAIL PROTECTED]> writes:
> > Sorry, this is probably obvious, but I use a high resolution monitor
> > and end up with a very small black cursor that is hard do find. It
> > here a way to make the cursor obvious. Change
