FVWM: initfunc or startfunc?

[Jason Timrod]

hi all,

i keep finding different references on the internet to both initfunc or startfunc, and problems using initfunc. since i am trying to be a good fvwm user and understand this more, could someone explain which one(s) i am to use and why?

sorry if this is documented - if so, can i have a link or sth?

many thanks.

Jason

[Shaika-Dzari]

Post by Jason Timrod
hi all,
i keep finding different references on the internet to both initfunc or startfunc, and problems using initfunc. since i am trying to be a good fvwm user and understand this more, could someone explain which one(s) i am to use and why?
sorry if this is documented - if so, can i have a link or sth?
many thanks.
Jason

Hi Jason,

Check here : https://wiki.archlinux.org/index.php/FVWM#2._InitFunction_versus_StartFunction_versus_RestartFunction


Regards.

[Jason Timrod]

Post by Shaika-Dzari
Hi Jason,
Check here : https://wiki.archlinux.org/index.php/FVWM#2._InitFunction_versus_StartFunction_versus_RestartFunction

thanks. so if i get it right, i only need startfunc then? is there a more detailed explanation of this, do you know? how does fvwm go about loading up and reading configs?

thanks for writing that info though, it was helpful.

Jason

[Shaika-Dzari]

Post by Jason Timrod

Post by Shaika-Dzari
Hi Jason,
Check here : https://wiki.archlinux.org/index.php/FVWM#2._InitFunction_versus_StartFunction_versus_RestartFunction

thanks. so if i get it right, i only need startfunc then? is there a more detailed explanation of this, do you know? how does fvwm go about loading up and reading configs?

Yes, you only need startfunc.
To get more explanation, you should check the man page :
http://www.fvwm.org/documentation/manpages/unstable/


Personally, I split my configuration in multiple file (function.fvwm,
style.fvwm, menu.fvwm, etc) and I use a master file to read it.

Something like this :

#------------------------------------------------------------------------
# Read Configuration Files
#------------------------------------------------------------------------
Read $[FVWM_USERDIR]/seed/src/style.fvwm
Read $[FVWM_USERDIR]/seed/src/functions.fvwm
Read $[FVWM_USERDIR]/seed/src/bar.fvwm
Read $[FVWM_USERDIR]/seed/src/events.fvwm
Read $[FVWM_USERDIR]/seed/src/menu.fvwm

# At last, startfunc file
Read $[FVWM_USERDIR]/seed/src/start.seed

Post by Jason Timrod
thanks for writing that info though, it was helpful.

Thomas Adam is the author I think.



Regards.

[Thomas Adam]

Post by Shaika-Dzari
Personally, I split my configuration in multiple file (function.fvwm,
style.fvwm, menu.fvwm, etc) and I use a master file to read it.

http://www.mail-archive.com/***@lists.math.uh.edu/msg16494.html

-- Thomas Adam

[Jason Timrod]

hi,

this link is cool. but theres a lot of information in there and its too much for me to understand all at once. i wonder why its not in the man page or the faq? it might be in the man page but it seems to me your explanation is easier to read =)

thank you for that.

Jason

[Thomas Adam]

Post by Jason Timrod
hi,
this link is cool. but theres a lot of information in there and its too
much for me to understand all at once. i wonder why its not in the man
page or the faq? it might be in the man page but it seems to me your
explanation is easier to read =)

This comes up from time to time (the last time it did, ISTR I was insulted
rather a lot, but that's by-the-by), and it amazes me this seems like such a
popular topic.

What's in the INITIALIZATION section of "man fvwm" should suffice --
although I suppose what it doesn't list is the information about why
StartFunction is preferred over InitFunction, and the caveats about it.

Most of my explanations in that post are simply put too detailed for the man
page -- at least, that's how I see it. If this is generally useful
information (and I'd be interested to know which bits) then I will happily
add it.

But note that whilst it will be added to my personal FVWM-TODO file, I won't
make it a priority before 2.6, and I would much rather someone else sent me
a patch instead. That would work, you know -- a patch. :)

At one point I was sick of answering these questions, so that post is
deliberately long so I can always refer back to it in its entirety, even if
a only a small part of it is relevant to a question, such as your original
one, Jason. So don't let the length of it put you off distilling any useful
bits.

So, any takeers? ;P

-- Thomas Adam

[Jason Timrod]

Post by Thomas Adam
But note that whilst it will be added to my personal
FVWM-TODO file, I won't
make it a priority before 2.6, and I would much rather
someone else sent me
a patch instead.  That would work, you know -- a
patch.  :)

thanks but i wouldnt know what would be the best bits to put in it. i am not much of a writer as you can see from my emails. but if you could put it on your list of things to get done i think it would be a good thing, what ever you decide to add.

or would shaika-dzari be able to help?

hny,

Jason

[Thomas Adam]

Post by Shaika-Dzari
#------------------------------------------------------------------------
# Read Configuration Files
#------------------------------------------------------------------------
Read $[FVWM_USERDIR]/seed/src/style.fvwm
Read $[FVWM_USERDIR]/seed/src/functions.fvwm
Read $[FVWM_USERDIR]/seed/src/bar.fvwm
Read $[FVWM_USERDIR]/seed/src/events.fvwm
Read $[FVWM_USERDIR]/seed/src/menu.fvwm

You can shorten this to just:

Read seed/src/...

FVWM will look in $[FVWM_USERDIR] on your behalf. See also "$."

I meant to mention this yesterday but forgot.

-- Thomas Adam