You are not logged in.
Pages: 1
Hello. I'm just starting to wade into the waters of tiling wms. I started with icewm, but it has very limited options. Next I tried fluxbox + wumwum, but I didn't like the feel of it. So I read the "comparison of tiling window managers" wiki and I decided on echinus since it had floating and tiling options, as well as title bars. I also like the fact that it's written in C. I'm not sure, but I hope it can update config changes on the fly. But after installing it, I don't know what to do with it. My only knowledge comes from reading the rc, but I don't understand all of the options.
Here's what I can do:
open xterm, toggle window borders and titles, close and maximize windows, cycle through open windows
Here's what I want to do:
tile windows, have ourico launch on startup (I use startx to login with .xinitrc), what can I do to customize it
I've looked at the echinus homepage, arch wiki, arch forums, and the rc file. I've even googled a bit. I found a config file and a thread at puppy, but nothing like a tutorial.
Any help is appreciated.
john
Last edited by OU812 (2011-01-16 15:49:54)
Offline
I'm doing better. Here's what i still can't figure out:
The rc suggests A + space to toggle between tiling and floating modes. Doesn't seem to work.
How do I get ourico to launch on startup?
Thanks.
john
P.S. I'm going to edit rc so that tiling instead of floating is default. We'll see.
Offline
Interesting. I changed the default from floating to tiling and it seems fine now. Behaves as expected. Anyone know how to get ourico to launch at startup? I use startx with .xinintrc. Thanks!
john
Offline
John - please learn to use the 'Edit' button and don't bump your thread https://wiki.archlinux.org/index.php/Fo … te#Bumping
There is a README for echinus - it sets out all of the options for configuring and using it.
To get ourico to launch at startup, just put it in your .xinitrc directly before echinus. Something along the lines of:
ourico &
exec echinus
See my start script for details: http://beta.intuxication.org/jasonwryan … inus-start
Offline
My apologies. I wasn't trying to bump this thread, but I am guilty of not using my head.
The readme file was much more understandable for a beginner during subsequent reads and most of my issues have been taken care of. I do have a few questions if you have the time to help:
1. I'm not sure how to tell which window is focused.
2. Is there a way to change the "master" window as in scrotwm?
3. I can start tint2 and fbpanel in .xinitrc, but not ourico. When I ran it in a terminal, I got an error along the line of "echinus is not configured."
4. If a panel can be started using .xinitrc, then can I assume that conky and feh (to set the background) could be added as well?
Also, I have followed some of your links and your scripts are very helpful. Being new to arch, I'm not sure where to put them. I've done some research and it looks like they can go ~/scripts. Not sure how to implement them though. A hint perhaps?
Thanks.
john
Offline
4. If a panel can be started using .xinitrc, then can I assume that conky and feh (to set the background) could be added as well?
Correct.
Also, I have followed some of your links and your scripts are very helpful. Being new to arch, I'm not sure where to put them. I've done some research and it looks like they can go ~/scripts. Not sure how to implement them though. A hint perhaps?
If you call the scripts with the full path then it won't matter where you place them. However if you want to run them by just specifying the name, you have to place them in a folder in your $PATH such as /usr/bin/. What I do is create a ~/bin folder and then add it to $PATH by having "export PATH=$PATH:$HOME/bin" in ~/.bash_profile
Last edited by anonymous_user (2011-01-09 05:05:30)
Offline
1. In your echinusrc, there is an option for selected border:
Echinus*selected.border: #404040
Just make sure you have sufficient contrast to highlight the selected window.
2. You can set keybinds to do all that sort of thing. Use my rc as an example and the README will get you there...
3. You need to give echinus a second to start before ourico (that's why I start ourico with sleep 1) - it will then paint across the top of the screen once echinus has started.
Offline
@anonymous_user
Thanks for that. I've always wondered what that was all about.
@jasonwryan
I'm in the process of adding your ourico start script and echinus scripts/configs to my system. I noticed something in your ourico script that I was curious about:
7 # Log stderror to a file
8 #echinus 2> ~/.echinus/log;
Is line 8 meant to be commented?
Thanks.
john
Offline
It depends. As the comment notes, if you want to log any errors when launching or running echinus, uncomment that line and comment out the other line
echinus > /dev/null;
or, as I posted above, you can just start it with
exec echinus
Offline
Thanks.
I still can't launch ourico at startup. I even used sleep for 2s. When launched from a terminal, I get:
echinus: cannot open configuration file
How do I get past this? Thanks.
john
Offline
Does your ouricorc have the correct permissions?
Paste your echinusrc and ouricorc.
Offline
I'm using your echinusrc copied from the link in the echinus arch wiki. I copied it to ~/.echinus. The only modification I've made so far is to swap urxvt with lxterminal.
The ouricorc file is still the stock one upon installation (using aur). It is still stored in /etc/xdg/ourico. After reading your post, I thought I may need to copy it somewhere. I tried to google for an answer and found a link:
https://bitbucket.org/jasonwryan/eeepc/ … /.ouricorc
But I don't know where to save your ouricorc.
I checked permissions and both files seem to have appropriate read permissions. Neither are set to be executable. Both have write permission for owner only.
Thanks.
john
Offline
The wiki page makes it clear where echinusrc should go and the second line of each of my config files gives you the path for the respective file:
echinusrc need to be in ~/.echinus/echinusrc
ouricorc should be in home: ~/.ouricorc
Offline
@jasonwryan
I think better ask in this thread instead opening a new similliar one , i've got a question regarding ouricorc which is hog a processor usage. Here's the example
in my xinitrc which causing Memory + Processor Hog. I already try to disable clock and xcompmgr but in Htop show that ouricorc & X is use a lot of resource.
ourico &
exec echinus
The other things is
ourico &
exec ck-launch-session echinus
Didn't bring ourico at startup but there's no memory hog when i exec the ourico after echinus start.
This is ourico issue or something wrong with my config? I like echinus style.
Offline
Apparently there is an issue with ourico. I don't see it myself, but see this post:
https://bbs.archlinux.org/viewtopic.php … 43#p867343
You could always run it without ourico and use tint2
Offline
echinusrc need to be in ~/.echinus/echinusrc
ouricorc should be in home: ~/.ouricorc
Oops. I meant ~/.echinus/ the directory. Sorry I didn't read the ourciorc header carefully, otherwise I could have figured this all out myself. Sheesh.
Ourico works fine now. Thanks for your help and patience.
john
Offline
Glad you got it sorted. Please prepend [Solved] to the thread title.
Offline
Sorry about that. I wanted to wait a bit in case hellnest needed to post again.
john
Offline
Pages: 1