X and Fluxbox :: Using .xinitrc to launch programs at startup
kerry and mikshaw i think you have spend too much time to it. It is not worth it. I really apreciate you help and all the effort. But since Gqview doesn't cooperate, I would propably use another application to do the job.
I will have a go with the settings in your .xinitrc mikshaw (although I do not like jmw).
Thank you again for all the effort and time you have spent on my query.
I will post when I will have this up and running. For the time being i am occupied with some exams. (university student see)
You have been very helpfull and i really appreciate it. I have something that seems to work with fluxbox and with icons, although it's not 100% reliable. It seems that gqview or fluxbox (not sure if it's one or both to blame) is VERY sensitive to other applications opening at the same time, and the result seems to be that gqview gets confused about what it's supposed to do. And it is not entrely consistent about it. Gqview also has trouble when other applications open after it, and configuring fluxbox to not focus new windows doesn't seem to be a useful alternative. Mainly I think GQview is the main issue, though, considering that there seems to be no logical reason for it to open its main window regardless of what's happening around it. I don't know anything about how X events work, so i could only play around with different things until something seemed to work. And this seems to work on my machine....
Everything else in .xinitrc is the same as in vanilla dsl 2.4, except i also commented out dillo.
Depending on your processor speed, you may need to increase the sleep time if you're still getting the window popping up. Also note that I moved wmswallow to the top of the list to give it more time to initialize (it seems to take a bit longer than the other apps).This does not work mikshaw. It boots up the Fluxbox, loads everything else and stops there. It doesn not load the Gqview.
What does fluxpid=$ do? $ is a pointer right??. Pid is the process id number. So i am imaging that you tell it to wait until a process (fluxbox?) completeley loads? Why did you use the wait $fluxpid after the GQview command?
I tried to install Feh but it gives me an error : no acceptable c compiler found in $path. i know that there the TCC compiler but it doesn't look for that at all. How can I point the "./configure" command to look for the tiny c ?The "$" in Bash signifies that the following string should be interpreted as a variable, and in Bash, "$!" is an internal variable that represents the pid of the last job run in the background (in this case, fluxbox &).
Since gqview was being annoying when it was not the very last program to run, I had to background everything, including fluxbox. If gqview was not backgrounded as well, the x session would be terminated as soon as you close gqview...there are no more commands to run, so .xinitrc closes, taking X with it. In order to keep the session going, the .xinitrc script must wait for something to happen, or continue running commands. The wait $fluxpid command is put there so that the script will wait for fluxbox to be terminated before closing itself.
Usually configure scripts will include a variable "CC", which is often set to "gcc". You might try changing it to "tcc". I wouldn't get your hopes up that you'll be able to compile feh with a base DSL system, though.
original here.
