Konstantin Osipov <[EMAIL PROTECTED]> writes: > I don't use IonWS as a primary WS because of relatively small screen > and low resolution - it's 15 inch Sony flat screen in 1024x768 > resolution. With my vision I can have maximum one full-size 80x37 > xterm per workspace, and I need to have a lot of xterms - mutt, irssi, > a few vi windows, a window to run MySQL server and another one for the > client. > > I wonder what's the best ION setup in my case.
I'd say that IonWS works exceptionally well with small or single-window setups. My main workspace is a single full-sized frame. I run a single xterm with screen (run via ssh-agent) inside it which gives me access to any number of shells or other tty apps. Screen has its own set of bindings and windows, and you can use those to start, stop, and navigate text windows. Besides that I sometimes have a web browser and an emacs[1] window, but with so few windows (only possible through screen) I never have to use the mouse to navigate. Occasionally I'll run a multi-windowed app (e.g., gnucash) and I have a special workspace set up just for that application. > PS If experienced ION users could share their ION config files with me, it > will be highly appreciated. I still haven't figured out how to switch > from keyboard between two IonWSs created as windows inside FloatWS. I tend not to use the default bindings much at all (I use a dvorak layout, and few of them make sense). I have query_lua bound to super-M, and I often use that until I find myself typing the same command over & over again, at which point I bind it to something sensible. [1] Fortunately, emacs has its own vi clone. :) -- Jeremy Hankins <[EMAIL PROTECTED]> PGP fingerprint: 748F 4D16 538E 75D6 8333 9E10 D212 B5ED 37D0 0A03
