fvwm-themes-users — Support for FVWM Themes users

Re: [FVWM-Themes] fvwm-themes-com generates no lock Fifo

[Thomas F. <t....@we...>]

"Mikhael Goikhman" <mi...@fr...> wrote:
>It took some time, but I read this long discussion fully.

First I thought you were a little bit displeased because of my comments
about FvwmScript-ThemesCenter but now I am relieved :D ...


>If fvwm-themes-config misses some output option, it is not very
>difficult to add it. I would start with this approach first.

The GUI must work without any changes in existing code because of
interoperability problems with other parts. So this is only an option
if no workaround is possible.


>Also, there is a menu item "Configuration / Theme Settings (gtk)".
>You get it when you have FvwmGtk built (i.e. with gtk1 and more).
>It is limited, but you can still take a look at it, if not yet.
>
>If I look at forms/FvwmGtk-Themes then it even hints that I had an
>idea (possibly not very practical) to add command-line script
>fvwm-themes-gtk, to auto-generate this GTK "Theme Settings" dialog.

Most distributions doesn't support Gtk1 anymore and therefore I think
it's not very useful to look inside the code ... furthermore the Gtk2
GUI is basically finished (the coverage). But if you think it is useful
anymore I will do it.


>There is no need to restart fvwm when switching themes, you do it by
>calling fvwm functions defined in ~/.fvwm/themes-rc file. Similarly
>to how themes can be loaded/configured using autogerated root menus.

Yes, I've seen it in FvwmScript-ThemesCenter because I tried with
fvwm-themes-config activating a change which I done but it doesn't work. Only
with fvwm functions it was possible.


>> But then I thought why not take the com mode of fvwm-themes-config
>> like in FvwmScript-ThemesCenter. It looks more handy than
>> fvwm-themes-configcommands to get themes, options, variants, etc.
>
>The com-mode can be useful, but it was implemented before we had
>fvwm-perllib. So I would suggest to try one of 2 other solutions
>first (the approach taken by current GUIs in FvwmForm and FvwmGtk,
>or creating some perl classes for fvwm-themes: FVWM::Modules::Themes*
>to be used by GUIs).

Ah, ok. In the last two days I've programmed the client com version. It
works good. Now I can simulate the calls made in FvwmScript-ThemesCenter :-)
But the 2nd solution with perl classes sounds interesting. I must read the
documentation again before I can say more ...


>I am ready to answer any questions and try to fix bugs if you report
>them. Also, if you allow for a slow developing, then maybe I can help
>you to make it work, either using fvwm-themes-config, or by creating
>some base perl class, like FVWM::Module::ThemesConfig, so that your
>FVWM module FvwmThemes[Gtk2]Center could just use it instead (or
>together with) FVWM::Module::Gtk2.

Thanks for your proposal :-) ... I will certainly get back to it ;-)


>If Olivier or you can fix the com-mode, this is a possibility too.

There are many analogies between fvwm-themes-config and
fvwm-themes-com ... but Olivier should specify which parts he think must be
cleaned up ... A possibility could be implementing a new commandline parameter
like --with-lockfile in fvwm-themes-config ...


>Let's possibly switch to fvwm-themes-devel mailing list.

Ok, my next answer will come over fvwm-themes-devel mailing list.


Thanks again, that you will help me.
Regards, Thomas
___________________________________________________________
Neu: WEB.DE De-Mail - Einfach wie E-Mail, sicher wie ein Brief!  
Jetzt De-Mail-Adresse reservieren: https://produkte.web.de/go/demail02

Re: [FVWM-Themes] fvwm-themes-com generates no lock Fifo

[Mikhael G. <mi...@fr...>]

On 24 Nov 2010 22:07:25 +0100, Thomas Funk wrote:
> 
> I am programming another Fvwm-Themes-Center because the original
> is, I would say  a little bit moldy and user unfriendly (not
> intuitive and for 'normal' users not very usable).
> 
> My intend is to create a Fvwm environment which can be used like
> Xfce or LXDE.  Perhaps KDE or Gnome ;-) ... see my discussions on
> Fvwm-forum for better understanding:
> http://www.fvwmforums.org/phpBB3/viewtopic.php?f=44&t=2661 
> and
> http://www.fvwmforums.org/phpBB3/viewtopic.php?f=44&t=2672 

It took some time, but I read this long discussion fully.

I wish you came 8 years ago; we needed more enthusiasts back then.
But let's see what can be done now if you are serious about it.

> The first step was to develop a Gtk2-perl based GUI. Now I am on
> that point to implement the functionality of FvwmScript-ThemesCenter.
> I tried first the commandline parameters of fvwm-themes-config but
> it's very hard to create hash tables from these outputs. Also the 
> commands are not very good documented but after reading the config
> files and some  fvwm-themes-config outputs I found many parts for
> how to use them. 

If fvwm-themes-config misses some output option, it is not very
difficult to add it. I would start with this approach first.

Also, there is a menu item "Configuration / Theme Settings (gtk)".
You get it when you have FvwmGtk built (i.e. with gtk1 and more).
It is limited, but you can still take a look at it, if not yet.

If I look at forms/FvwmGtk-Themes then it even hints that I had an
idea (possibly not very practical) to add command-line script
fvwm-themes-gtk, to auto-generate this GTK "Theme Settings" dialog.

There is no need to restart fvwm when switching themes, you do it by
calling fvwm functions defined in ~/.fvwm/themes-rc file. Similarly
to how themes can be loaded/configured using autogerated root menus.

> But then I thought why not take the com mode of fvwm-themes-config
> like in FvwmScript-ThemesCenter. It looks more handy than
> fvwm-themes-configcommands to get  themes, options, variants, etc.

The com-mode can be useful, but it was implemented before we had
fvwm-perllib. So I would suggest to try one of 2 other solutions
first (the approach taken by current GUIs in FvwmForm and FvwmGtk,
or creating some perl classes for fvwm-themes: FVWM::Modules::Themes*
to be used by GUIs).

> Therefore I tested fvwm-themes-com in conjunction with
> fvwm-themes-config but I see that  there's no getting around to
> implement the com interface in my Fvwm-Themes-Center ...
> 
> Perhaps you could help me if I hang on the implementation (or
> Olivier) of some parts. I know  reading your posts you're mostly
> busy but for some hints here and there I am appreciated.

I am ready to answer any questions and try to fix bugs if you report
them. Also, if you allow for a slow developing, then maybe I can help
you to make it work, either using fvwm-themes-config, or by creating
some base perl class, like FVWM::Module::ThemesConfig, so that your
FVWM module FvwmThemes[Gtk2]Center could just use it instead (or
together with) FVWM::Module::Gtk2.

If Olivier or you can fix the com-mode, this is a possibility too.

Let's possibly switch to fvwm-themes-devel mailing list.

Regards,
Mikhael.

Re: [FVWM-Themes] fvwm-themes-com generates no lock Fifo

[Thomas F. <t....@we...>]

"Mikhael Goikhman"  wrote:
>To be honest I didn't need to use the com mechanism myself.
>Maybe it is possible to do what you want differently?
>Hard to say without knowing your original need.
>
>Looking at the code I see that fvwm-themes-com is more designed to
>work with "fvwm-themes-menuapp --com-mode". Try this:
>
>  % fvwm-themes-menuapp --com-mode &
>  % fvwm-themes-com --name menuapp --lock-and-get --message=menus-list
>  % fvwm-themes-com --name menuapp --message exit
>
>And "fvwm-themes-config --com-mode" does not create lock files for
>communication, you can see how FvwmScript-ThemesCenter uses it.
>But I have no examples of how to make it work with fvwm-themes-com.
>
>It is possible to patch fvwm-themes-config to manage lock fifo
>similarly to fvwm-themes-menuapp, but since it is not my code
>I would prefer not to change it without advice from Olivier;
>this can break communication with other programs (FvwmScript).
>
>Can you please tell us what you tried to achieve in the first place?
>
I am programming another Fvwm-Themes-Center because the original is, I would say 
a little bit moldy and user unfriendly (not intuitive and for 'normal' users not very usable).

My intend is to create a Fvwm environment which can be used like Xfce or LXDE. 
Perhaps KDE or Gnome ;-) ... see my discussions on Fvwm-forum for better understanding:
http://www.fvwmforums.org/phpBB3/viewtopic.php?f=44&t=2661 
and
http://www.fvwmforums.org/phpBB3/viewtopic.php?f=44&t=2672 

The first step was to develop a Gtk2-perl based GUI. Now I am on that point to implement 
the functionality of FvwmScript-ThemesCenter. I tried first the commandline parameters of 
fvwm-themes-config but it's very hard to create hash tables from these outputs. Also the 
commands are not very good documented but after reading the config files and some 
fvwm-themes-config outputs I found many parts for how to use them. 

But then I thought why not take the com mode of fvwm-themes-config like in 
FvwmScript-ThemesCenter. It looks more handy than fvwm-themes-configcommands to get 
themes, options, variants, etc.

Therefore I tested fvwm-themes-com in conjunction with fvwm-themes-config but I see that 
there's no getting around to implement the com interface in my Fvwm-Themes-Center ...

Perhaps you could help me if I hang on the implementation (or Olivier) of some parts. I know 
reading your posts you're mostly busy but for some hints here and there I am appreciated.

Best Regards,
Thomas
___________________________________________________________
Neu: WEB.DE De-Mail - Einfach wie E-Mail, sicher wie ein Brief!  
Jetzt De-Mail-Adresse reservieren: https://produkte.web.de/go/demail02

Re: [FVWM-Themes] fvwm-themes-com generates no lock Fifo

[Mikhael G. <mi...@fr...>]

On 24 Nov 2010 15:45:57 +0100, Thomas Funk wrote:
> 
> I want to communicate with a perl program with fvwm-themes-config
> via com mode. My first try with the perl program hangs, so I
> decided to try it over a terminal for better understanding:
> 
> tf@fvwmtest2:~/.fvwm$ fvwm-themes-config --com-mode &
> [5] 4737
> 
> ok, fvwm-themes-config creates the infifo:
> prw-r--r--  1 tf tf    0 2010-11-24 14:55 .tmp-com-in-config|
> 
> Then I tried to send a message:
> tf@fvwmtest2:~/.fvwm$ fvwm-themes-com --name config --lock-and-get --message="all-startup-stuff| 1"
> 
> fvwm-themes-com creates a outfifo:
> prw-r--r--  1 tf tf    0 2010-11-24 15:13 .tmp-com-out-config|
> 
> but after a timeout the following error occurs:
> com: No lock Fifo .tmp-com-lock-config for config communication
> 
> What did I wrong?

To be honest I didn't need to use the com mechanism myself.
Maybe it is possible to do what you want differently?
Hard to say without knowing your original need.

Looking at the code I see that fvwm-themes-com is more designed to
work with "fvwm-themes-menuapp --com-mode". Try this:

  % fvwm-themes-menuapp --com-mode &
  % fvwm-themes-com --name menuapp --lock-and-get --message=menus-list
  % fvwm-themes-com --name menuapp --message exit

And "fvwm-themes-config --com-mode" does not create lock files for
communication, you can see how FvwmScript-ThemesCenter uses it.
But I have no examples of how to make it work with fvwm-themes-com.

It is possible to patch fvwm-themes-config to manage lock fifo
similarly to fvwm-themes-menuapp, but since it is not my code
I would prefer not to change it without advice from Olivier;
this can break communication with other programs (FvwmScript).

Can you please tell us what you tried to achieve in the first place?

Regards,
Mikhael.

[FVWM-Themes] fvwm-themes-com generates no lock Fifo

[Thomas F. <t....@we...>]

Hi to all!

I want to communicate with a perl program with fvwm-themes-config via com mode.
My first try with the perl program hangs, so I decided to try it over a terminal for better understanding:
tf@fvwmtest2:~/.fvwm$ fvwm-themes-config --com-mode &
[5] 4737

ok, fvwm-themes-config creates the infifo:
prw-r--r--  1 tf tf    0 2010-11-24 14:55 .tmp-com-in-config|

Then I tried to send a message:
tf@fvwmtest2:~/.fvwm$ fvwm-themes-com --name config --lock-and-get --message="all-startup-stuff| 1"

fvwm-themes-com creates a outfifo:
prw-r--r--  1 tf tf    0 2010-11-24 15:13 .tmp-com-out-config|

but after a timeout the following error occurs:
com: No lock Fifo .tmp-com-lock-config for config communication

What did I wrong?

Thomas
___________________________________________________________
Neu: WEB.DE De-Mail - Einfach wie E-Mail, sicher wie ein Brief!  
Jetzt De-Mail-Adresse reservieren: https://produkte.web.de/go/demail02

Re: [FVWM-Themes] Releasing fvwm-themes CVS -> fvwm-themes-0.7.1

[Thomas A. <th...@xt...>]

On 5 September 2010 18:55, Mikhael Goikhman <mi...@ho...> wrote:
> I feel that we should release a new version. But since I never had a
> time to seriously develop it in the last years and I don't currently
> even run the latest cvs versions (but still pretty recent), and I see
> small bugs, I can't yet fully comment on it.

What bugs?  I updated CVS to get rid of numerous warning a few years
ago -- which today have still stood the test of time.

Even the transparent theme works well, for instance.

-- Thomas Adam

Re: [FVWM-Themes] Releasing fvwm-themes CVS -> fvwm-themes-0.7.1

[Mikhael G. <mi...@ho...>]

On 05 Sep 2010 14:51:58 +0100, Thomas Adam wrote:
> 
> I'm wondering if there's any fvwm-themes users out there still who'd
> notice this, so I will ask on the off-chance.

I think the lists work and have several dozens of subscribers.

> I'm satisfied with my improvements to the CVS version of fvwm-themes
> that we can do a new stable release.
> 
> How would people here feel about that?

I feel that we should release a new version. But since I never had a
time to seriously develop it in the last years and I don't currently
even run the latest cvs versions (but still pretty recent), and I see
small bugs, I can't yet fully comment on it.

I will try to spend one day on fvwm-themes next week and then I will
hopefully reply on the devel list. Please remind me if I don't.

Regards,
Mikhael.

[FVWM-Themes] Releasing fvwm-themes CVS -> fvwm-themes-0.7.1

[Thomas A. <th...@xt...>]

All,

I'm wondering if there's any fvwm-themes users out there still who'd
notice this, so I will ask on the off-chance.

I'm satisfied with my improvements to the CVS version of fvwm-themes
that we can do a new stable release.

How would people here feel about that?

Kindly,

-- Thomas Adam

Re: [FVWM-Themes] behavior of alt-tab + root menu

[Thomas A. <tho...@gm...>]

2010/1/26 Nicolas <nic...@gm...>:
> Hi there
>
> other newbie questions I am afraid ...
>
> i) Im using fvwm-themes and after I start it I seem to be able to use the
> "ALT"+"TAB" key to switch between the active windows ... however after a
> while and for reasons I dont understand, I cant use it anymore ("ALT"+"TAB"
> doesnt do anything) ... is there something I am missing here ?

Most likely a modifier issue such as numlock:

http://fvwm.org/documentation/faq/#0.1

> ii) I would like to change the entries in the root menu (left click): where
> is it located ?

http://fvwm-themes.sourceforge.net/doc/menus-extra

-- Thomas Adam

[FVWM-Themes] behavior of alt-tab + root menu

[Nicolas <nic...@gm...>]

Hi there

other newbie questions I am afraid ...

i) Im using fvwm-themes and after I start it I seem to be able to use the
"ALT"+"TAB" key to switch between the active windows ... however after a
while and for reasons I dont understand, I cant use it anymore ("ALT"+"TAB"
doesnt do anything) ... is there something I am missing here ?

ii) I would like to change the entries in the root menu (left click): where
is it located ?

am on ubuntu 9.04

thanks in advance for any help

-- 
_/\/¯¯¯¯¯¯\/\_ 33º49'45.24"S & 18º28'45.60"E
Dr. Nicolas Fauchereau
Senior Researcher
CSIR - NRE
Research Group: Ocean systems and climate
15 Lower Hope street, Rosebank 7700
South Africa
tel: 021 658 2764
_/\/¯¯¯¯¯¯\/\_ 33º49'45.24"S & 18º28'45.60"E

Re: [FVWM-Themes] another ICCCM 2.0 compliant WM is running

[Nicolas <nic...@gm...>]

hi Michael and thanks for your help
I've simply created an entry in my xsessions for fvwm-themes-start and
that's it ... could have thought about it before
cheers
Nicolas

2010/1/14 Mikhael Goikhman <mi...@ho...>

> On 14 Jan 2010 11:06:18 +0200, Nicolas wrote:
> >
> > I've installed fvwm-themes from the sources and it went fine but when
> > am trying to run it I've got this following message:
> >
> > ~$ fvwm-themes-start
> > [FVWM-Themes]: Starting FVWM under the main fvwm-themes session
> > [fvwm][SetupICCCM2]: <<ERROR>> another ICCCM 2.0 compliant WM is running,
> > try -replace
> >
> > I've tried fvwm-themes-start -replace but same error
>
> If you run this command inside fvwm, you may try to open FvwmConsole
> and issue "Restart fvwm-themes-start" in it.
>
> You may also temporarily run: fvwm-themes-start --fvwm 'fvwm --replace'
> or even: fvwm -f themes-rc
>
> But better just follow the instructions in "man fvwm-themes-start".
>
> Regards,
> Mikhael.
>



-- 
_/\/¯¯¯¯¯¯\/\_ 33º49'45.24"S & 18º28'45.60"E
Dr. Nicolas Fauchereau
Senior Researcher
CSIR - NRE
Research Group: Ocean systems and climate
15 Lower Hope street, Rosebank 7700
South Africa
tel: 021 658 2764
_/\/¯¯¯¯¯¯\/\_ 33º49'45.24"S & 18º28'45.60"E

Re: [FVWM-Themes] another ICCCM 2.0 compliant WM is running

[Mikhael G. <mi...@ho...>]

On 14 Jan 2010 11:06:18 +0200, Nicolas wrote:
> 
> I've installed fvwm-themes from the sources and it went fine but when
> am trying to run it I've got this following message:
> 
> ~$ fvwm-themes-start
> [FVWM-Themes]: Starting FVWM under the main fvwm-themes session
> [fvwm][SetupICCCM2]: <<ERROR>> another ICCCM 2.0 compliant WM is running,
> try -replace
> 
> I've tried fvwm-themes-start -replace but same error

If you run this command inside fvwm, you may try to open FvwmConsole
and issue "Restart fvwm-themes-start" in it.

You may also temporarily run: fvwm-themes-start --fvwm 'fvwm --replace'
or even: fvwm -f themes-rc

But better just follow the instructions in "man fvwm-themes-start".

Regards,
Mikhael.

Re: [FVWM-Themes] another ICCCM 2.0 compliant WM is running

[Thomas A. <tho...@gm...>]

2010/1/14 Nicolas <nic...@gm...>:
> Hi
>
> I am new to fvwm, and would like to use fvwm-theme (especially for the CDE
> theme !)
> I've installed fvwm-themes from the sources and it went fine but when am
> trying to run it
> I've got this following message:
>
> ~$ fvwm-themes-start
> [FVWM-Themes]: Starting FVWM under the main fvwm-themes session
> [fvwm][SetupICCCM2]: <<ERROR>> another ICCCM 2.0 compliant WM is running,
> try -replace

Then you must have another WM already running, perhaps FVWM itself?

-- Thomas Adam

[FVWM-Themes] another ICCCM 2.0 compliant WM is running

[Nicolas <nic...@gm...>]

Hi

I am new to fvwm, and would like to use fvwm-theme (especially for the CDE
theme !)
I've installed fvwm-themes from the sources and it went fine but when am
trying to run it
I've got this following message:

~$ fvwm-themes-start
[FVWM-Themes]: Starting FVWM under the main fvwm-themes session
[fvwm][SetupICCCM2]: <<ERROR>> another ICCCM 2.0 compliant WM is running,
try -replace

I've tried fvwm-themes-start -replace but same error

I'm on a i386 PC running ubuntu 9.04

thanks in advance for any help

-- 
_/\/¯¯¯¯¯¯\/\_ 33º49'45.24"S & 18º28'45.60"E
Dr. Nicolas Fauchereau
Senior Researcher
CSIR - NRE
Research Group: Ocean systems and climate
15 Lower Hope street, Rosebank 7700
South Africa
tel: 021 658 2764
_/\/¯¯¯¯¯¯\/\_ 33º49'45.24"S & 18º28'45.60"E

Re: [FVWM-Themes] [jg: Re: FuncFvwmRunInXterm not reading .bashrc file]

[Thomas A. <tho...@gm...>]

2009/10/29 Jamie Griffin <jg...@ko...>:
>> This is why I suggested wrapping your call to "bash -l -c '...'" and
>> if you're doing that for locale settings, then you're seriously doing
>> it wrong.  Worse yet, what I suspect you're doing is sourcing your
>> ~/.profile file from ~/.bashrc, and whilst this is a common idiom, is
>> ultimately wrong as the two serve completely different purposes.
>
> I'm sourcing my .bashrc from my .profile with this:
>
> if [ -f ~/.bashrc ]; then
> . ~.bashrc
> fi

OK, either way round makes no odds -- and as I said, although it's a
common idiom it's still "wrong" from the point of view that you no
longer have a separation of login shell and interactive, where some
login tasks have no business being part of an interactive shell.

>    and have set the $LANG and $MM_CHARSET variables (along with other
> environment stuff) from my .bashrc, which is what the FreeBSD manual
> said to do when setting locales. (i know you said you weren't interested
> in finding that out but you might just be being grumpy.)

No, not grumpy at all, just that it opens up a can of worms best left
to using /etc/environment, to be honest.

> I don't think there is anything
> unusual about the way i've set that up but i could be wrong.

Only in so much that you're now having to completely override
system-wide defaults, which applications are going to pick up on
before your own, and as you've seen due to the """"recommended""" way,
falls over when you appreciate how the environment works.

-- Thomas Adam

[FVWM-Themes] [jg: Re: FuncFvwmRunInXterm not reading .bashrc file]

[Jamie G. <jg...@ko...>]

> This is why I suggested wrapping your call to "bash -l -c '...'" and
> if you're doing that for locale settings, then you're seriously doing
> it wrong.  Worse yet, what I suspect you're doing is sourcing your
> ~/.profile file from ~/.bashrc, and whilst this is a common idiom, is
> ultimately wrong as the two serve completely different purposes.

I'm sourcing my .bashrc from my .profile with this:

if [ -f ~/.bashrc ]; then
. ~.bashrc
fi

    and have set the $LANG and $MM_CHARSET variables (along with other
environment stuff) from my .bashrc, which is what the FreeBSD manual
said to do when setting locales. (i know you said you weren't interested
in finding that out but you might just be being grumpy.) I don't think there is anything
unusual about the way i've set that up but i could be wrong. 
 
> So, you see now why you might think your environment is fine, but
> actually is not?  You could of course in the example of using
> ~/.xsession to start FVWM, just have something like this:
> 
> [ -e "$HOME/.bashrc" ] && source "$HOME/.bashrc"
> exec fvwm-themes-start

But yes, your explanation does make sense to me and seems the most likely cause, as i am using xdm to launch fvwm.  I will try it the way you have suggested and hopefully it will work. 

Thanks for your help though, much appreciated :0)

Re: [FVWM-Themes] FuncFvwmRunInXterm not reading .bashrc file

[Thomas A. <tho...@gm...>]

2009/10/29 Jamie Griffin <jg...@ko...>:
> On Thu 29.Oct'09 at 14:17:50 +0000, Thomas Adam wrote:
>> + I exec xterm -ls -fg $[fg.cs34] -bg $[bg.cs34] -g 80x40 -fn 7x14 -fb
>> 7x14bold +sb -ut -T "$0" -n "$0" -e /bin/bash -l -c "$1"
>>
>> You can't have a login shell and run "-e" commands at the same time,
>> which is where your problems are coming from.  The above trick of
>> spawning a containing login shell is a hack, essentially.  Fix your
>> environment *before* loading FVWM so that all shells spawned from it
>> inherit the environment.
>
> ok, i understand that; but, this is what i find confusing because my
> environment has been set up correctly. All regular shells opened do use the
> settings from the environment. I open xterms and rxvt's from the menu
> just like i do for the mail programs that 'RunInXterm'.

In that case, I dread to think what's in your .profile that's setting
this.  I am not interested in finding out either, just bear in mind
that /etc/environments exists as the only shell-agnostic way of
setting up things like LC_ALL, LANG, etc.

What I suspect is happening though is you're starting FVWM from a
display manager that launches FVWM directly -- this is annoying since
this doesn't give the user a chance to set the environment.  You can
achieve this with most display managers using their "failsafe" option,
but essentially setting up your ~/.xsession file such that you can do:

export FOO="bar"
exec fvwm-themes-start

...and have $FOO referenced from anything spawned from FVWM is *not*
what you're describing here.  Your ~/.bashrc is for interactive
shells, which means of course, if you open up a terminal which sources
that, you're under the allusion that it has inherited from the
environment, but that's not the case, the duration of that is
applicable only to the lifetime of the shell you started.  In the
example above, because FOO was exported before FVWM was, FVWM inherits
that environment, and hence anything else spawned from it.

This is why I suggested wrapping your call to "bash -l -c '...'" and
if you're doing that for locale settings, then you're seriously doing
it wrong.  Worse yet, what I suspect you're doing is sourcing your
~/.profile file from ~/.bashrc, and whilst this is a common idiom, is
ultimately wrong as the two serve completely different purposes.

So, you see now why you might think your environment is fine, but
actually is not?  You could of course in the example of using
~/.xsession to start FVWM, just have something like this:

[ -e "$HOME/.bashrc" ] && source "$HOME/.bashrc"
exec fvwm-themes-start

-- Thomas Adam

Re: [FVWM-Themes] FuncFvwmRunInXterm not reading .bashrc file

[Jamie G. <jg...@ko...>]

On Thu 29.Oct'09 at 14:17:50 +0000, Thomas Adam wrote:
> + I exec xterm -ls -fg $[fg.cs34] -bg $[bg.cs34] -g 80x40 -fn 7x14 -fb
> 7x14bold +sb -ut -T "$0" -n "$0" -e /bin/bash -l -c "$1"
> 
> You can't have a login shell and run "-e" commands at the same time,
> which is where your problems are coming from.  The above trick of
> spawning a containing login shell is a hack, essentially.  Fix your
> environment *before* loading FVWM so that all shells spawned from it
> inherit the environment.

ok, i understand that; but, this is what i find confusing because my
environment has been set up correctly. All regular shells opened do use the
settings from the environment. I open xterms and rxvt's from the menu
just like i do for the mail programs that 'RunInXterm'. 

The xterms and rxvts use the environment variables set in the .bashrc file,
it's just the shells that use this FuncFvwmRunInXterm function that do
not. 
I know this because if i invoke mutt, say, from an xterm or rxvt i already have open the locale display is right; when it is invoked with
the FuncFvwmRunInXterm function the locale display is not right.

Anyway, your suggestion/hack above has worked so thanks for that. 


The .Xdefaults file wasn't the problem and  is being read properly by xterms, etc,
and i did make sure i ran `xrdb .Xdefaults` after editing it.  

Jamie

Re: [FVWM-Themes] FuncFvwmRunInXterm not reading .bashrc file

[Thomas A. <tho...@gm...>]

2009/10/29 Thomas Adam <tho...@gm...>:
> 2009/10/29 Jamie Griffin <jg...@ko...>:
>> Does anyone know what i need to change to get this behaviour?
>
> Well, the function looks like this by default:
>
> DestroyFunc FuncFvwmRunInXterm
> AddToFunc   FuncFvwmRunInXterm
> + I exec xterm -fg $[fg.cs34] -bg $[bg.cs34] -g 80x40 -fn 7x14 -fb
> 7x14bold +sb -ut -T "$0" -n "$0" -e $1
>
> I would say that you need to make this a login shell, as:
>
> DestroyFunc FuncFvwmRunInXterm
> AddToFunc   FuncFvwmRunInXterm
> + I exec xterm -ls -fg $[fg.cs34] -bg $[bg.cs34] -g 80x40 -fn 7x14 -fb
> 7x14bold +sb -ut -T "$0" -n "$0" -e $1

Err, that cut and paste failed:

+ I exec xterm -ls -fg $[fg.cs34] -bg $[bg.cs34] -g 80x40 -fn 7x14 -fb
7x14bold +sb -ut -T "$0" -n "$0" -e /bin/bash -l -c "$1"

You can't have a login shell and run "-e" commands at the same time,
which is where your problems are coming from.  The above trick of
spawning a containing login shell is a hack, essentially.  Fix your
environment *before* loading FVWM so that all shells spawned from it
inherit the environment.

-- Thomas Adam

Re: [FVWM-Themes] FuncFvwmRunInXterm not reading .bashrc file

[Thomas A. <tho...@gm...>]

2009/10/29 Jamie Griffin <jg...@ko...>:
> Does anyone know what i need to change to get this behaviour?

Well, the function looks like this by default:

DestroyFunc FuncFvwmRunInXterm
AddToFunc   FuncFvwmRunInXterm
+ I exec xterm -fg $[fg.cs34] -bg $[bg.cs34] -g 80x40 -fn 7x14 -fb
7x14bold +sb -ut -T "$0" -n "$0" -e $1

I would say that you need to make this a login shell, as:

DestroyFunc FuncFvwmRunInXterm
AddToFunc   FuncFvwmRunInXterm
+ I exec xterm -ls -fg $[fg.cs34] -bg $[bg.cs34] -g 80x40 -fn 7x14 -fb
7x14bold +sb -ut -T "$0" -n "$0" -e $1

That should solve your problems.  As for your ~/.Xdefaults issue,
you're either not understanding the resource (remember they're case
sensitive), or more likely, you're not running "xrdb -load
~/.Xdefaults".

-- Thomas Adam

[FVWM-Themes] FuncFvwmRunInXterm not reading .bashrc file

[Jamie G. <jg...@ko...>]

Hello

I'm having a bit of trouble with the text-based mail readers
locale/display when they are invoked by the FuncFvwmRunInXterm. I've
made sure the locales are set correctly in the shell rc files, but it
seems these files are not read by xterms when launched by
FuncFvwmRunInXterm. I've copied the files function-appbind and
menu-programs and made a number of changes to the options used when
these functions are used but so far nothing i've tried has worked. I've
also used 'XTerm*locale:' entry in .Xdefaults but it seems even this is
being ignored by the xterms launched by FuncFvwmRunInXterm. 

Does anyone know what i need to change to get this behaviour? 

Thanks, Jamie 

Re: [FVWM-Themes] bindings-extras@personal not behaving as expected

[Thomas A. <tho...@gm...>]

On Fri, Oct 16, 2009 at 11:03:29PM +0200, th...@pi... wrote:
> Wheel is activated as should be clear from the results stated in my 
> first post which conforms to the lines just before your snippet:
> 
> Mouse 4 TSF A WindowShade true
> Mouse 4 TSF S Raise
> Mouse 5 TSF A WindowShade false
> Mouse 5 TSF S Lower

OK.  This obviously won't change pages though, which is what the example I
gave you originally showed.  But using the above you could include this
along with switching pages, as TSF doesn't apply to the root window.

> God will realise that I wish to over-ride the NOP on root window. 

Turn off numlock?  I use SloppyFocus for example, and root-window bindings
for the mouse pointer work fine, even those for Mouse {4,5}, so I suspect
you want to also read up on "IgnoreModifiers".

> Thanks for your help and your sarcasm.

No problem.  Thanks for your patience.

-- Thomas Adam

-- 
"It was the cruelest game I've ever played and it's played inside my head."
-- "Hush The Warmth", Gorky's Zygotic Mynci.

Re: [FVWM-Themes] bindings-extras@personal not behaving as expected

[<th...@pi...>]

Thomas Adam wrote:
> On Fri, Oct 16, 2009 at 01:22:34PM +0200, th...@pi... wrote:
>> I thought the lines just above its invocation were the function definition.
>>
>> DestroyFunc WheelScroll
>> AddToFunc WheelScroll
>> + I Exec echo "WheelScroll called with $0">> ~/.fvwm/config.log
>>
>> Mouse 4     R   A   WheelScroll down
>> Mouse 5     R   A   WheelScroll up
>>
>> That is what I see all over in example configs.
>> What have I missed?
> 
> themes/default/settings/wheel/enabled
> 
> is what you've missed.  That's the file that defined what happenes, as in:
> 
> Mouse 4 R   A Nop
> Mouse 5 R   A Nop
> Mouse 4 A  CM GotoPage 0p -1p
> Mouse 5 A  CM GotoPage 0p +1p
> Mouse 4 A SCM GotoPage -1p 0p
> Mouse 5 A SCM GotoPage +1p 0p
> 
> ... so God only knows what you thought you needed to do.

God may know but apparently you are not God (not quite).

Wheel is activated as should be clear from the results stated in my 
first post which conforms to the lines just before your snippet:

Mouse 4 TSF A WindowShade true
Mouse 4 TSF S Raise
Mouse 5 TSF A WindowShade false
Mouse 5 TSF S Lower

God will realise that I wish to over-ride the NOP on root window. 
Something is preventing this for taking effect. God also knows I don't 
want to be turning this into a two hand, five finger operation I want to 
scroll desktop with the smallest movement of the tip of one finger on 
the mouse wheel. Mouse plus SCM does not interest me one bit.

FVWM-themes suggests using bindings-extra@personal for personalisations 
but apparently this gets loaded BEFORE the default profile wheel 
settings so my function call was getting blow out by the NOPs in 
default. Commenting out the two NOP lines enables the behaviour I was 
trying to create.

Oh, "sorry for not reading your first post properly" ? No problem, don't 
mention it. It's easy to make a mistake when you're in a hurry to make 
smart remarks.

Thanks for your help and your sarcasm.


> 
> -- Thomas Adam
> 

Re: [FVWM-Themes] bindings-extras@personal not behaving as expected

[Thomas A. <tho...@gm...>]

On Fri, Oct 16, 2009 at 01:22:34PM +0200, th...@pi... wrote:
> I thought the lines just above its invocation were the function definition.
> 
> DestroyFunc WheelScroll
> AddToFunc WheelScroll
> + I Exec echo "WheelScroll called with $0">> ~/.fvwm/config.log
> 
> Mouse 4     R   A   WheelScroll down
> Mouse 5     R   A   WheelScroll up
> 
> That is what I see all over in example configs.
> What have I missed?

themes/default/settings/wheel/enabled

is what you've missed.  That's the file that defined what happenes, as in:

Mouse 4 R   A Nop
Mouse 5 R   A Nop
Mouse 4 A  CM GotoPage 0p -1p
Mouse 5 A  CM GotoPage 0p +1p
Mouse 4 A SCM GotoPage -1p 0p
Mouse 5 A SCM GotoPage +1p 0p

... so God only knows what you thought you needed to do.

-- Thomas Adam

-- 
"It was the cruelest game I've ever played and it's played inside my head."
-- "Hush The Warmth", Gorky's Zygotic Mynci.

Re: [FVWM-Themes] bindings-extras@personal not behaving as expected

[<th...@pi...>]

Thomas Adam wrote:
> 2009/10/16  <th...@pi...>:
>> HI,
>>
>> I've spent the last week or so getting used to fvwm and trying to fathom
>> out its arcane scripting language.
> 
> That's a matter of opinion, thanks.

No offence intended. It seems to offer enormous possibilities and using 
the themes package I had something usable pretty quickly. Now I have to 
learn to use it fully.


> 
>> I'm attempting to make the mouse scroll wheel events on the root window
>> scroll desktops. From the fvwm-themes page on SF
>> http://fvwm-themes.sourceforge.net/doc/creating-themes I try to use and
>> example
> 
>> DestroyFunc WheelScroll
>> AddToFunc WheelScroll
>> + I Exec echo "WheelScroll called with $0">> ~/.fvwm/config.log
> 
> Just FYI, a simple:
> 
> + I Echo Foo $*
> 
> would have done here, since oftentimes FVWM is logging to ~/.xsession-errors

I was aware of that file but it's content was years old. Apparently not 
the fvwm log here.

> 
>> Mouse 4     R   A   WheelScroll down
>> Mouse 5     R   A   WheelScroll up
> 
> This is correct.
> 
>> I replaced the page swapping code with the simple debugging message to test.
> 
> Right -- so logically then the problem is going to be with your
> definition for WheelScroll -- can we see it?

I thought the lines just above its invocation were the function definition.

DestroyFunc WheelScroll
AddToFunc WheelScroll
+ I Exec echo "WheelScroll called with $0">> ~/.fvwm/config.log

Mouse 4     R   A   WheelScroll down
Mouse 5     R   A   WheelScroll up

That is what I see all over in example configs.
What have I missed?

Thx.

> 
>> I configured mainly from cde style and to see mouse wheel effective on
>> title where it collapses the rest of the window to just the title bar.
>> (Is this what is called Shading in fvwm ?) This leads be to think that
> 
> Yes, it's called Shading.
> 
> I have no idea what you're asking since everything will work, so the
> only problem can be with the WheelScroll function.
> 
> -- Thomas Adam
> 
>