.xinit vs. .fluxbox/startup

I tried to send this question before and it seemed to have disappared. 
If on the contrary it is a duplication, my apologies.

An autostart of applications can be done in .xsession or in 
.fluxbox/startup, but I have found from experience that if the former 
exists, the latter cannot end with an exec fluxbox line and cannot 
start applications. However, I cannot find any documentation for this, 
and so wonder if something might be wrong in my setup.

Second, where apps are started and the configuration of either of the 
two files determine whether fluxbox is running when apps start. Are 
there reasons why one would chose one file over the other to 
auto-start applications? It seems that .xsession is traditional and 
wonder why fluxbox felt it necessary to provide its own facility.

Besides auto-starting applications, I want them to start on specific 
workspaces. There are several ways to do this, which I have 
implemented at various times. 

However, I have two apps (mc, mutt) that start from a terminal, and I 
also want to be able to start a terminal from a keybinding on a 
current workspace. Telling the application window to remember 
sorkspace, position and size does not work in this case, for mc and 
mutt end up in the same place, and so does the terminal called with a 
keybinding. To straighten this out, I can try using ~/.flusbox/apps 
stanzas,
 or the -xrm option when calling the terminal, or call mutt 
with aterm, mc with xterm, and uxrvt with a keybinding. Any problems 
with these approaches and is one or another preferable?

Haines Brown

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july