From: Joe(theWordy)Philbrook <jt...@tt...> - 2009-02-17 05:30:34
|
It would appear that on Feb 15, P Purkayastha did say: > At 11:27am, Joe(theWordy)Philbrook wrote: > > > Since I'm one who likes to edit my ~/.e16/bindings.cfg by hand it > > doesn't hurt much that "eesh help full" says: > > > > ---------------------------------------- > > set_keybindings : Set keybindings (deprecated) > > ---------------------------------------- > > > > At least not with e16. But if e17 has eesh then I'm saddened by this > > as it means I will be stuck with that annoying gui. (since as far as I > > can see they moved away from using human editable .cfg files...) > > > > On the other hand: > > ---------------------------------------- > > get_keybindings : List keybindings (deprecated) > > ---------------------------------------- > > > > doesn't bother me at all because: IF e17 has eesh then these > > aren't depreciated yet: > > aclass kb List key bindings > > aclass list [name/all] List action class[es] > > aclass load [name] Reload action classes (default is bindings.cfg) > > > > Unfortunately the "aclass load [name]" wouldn't help much if I can't > > manually edit whatever e17 is using for a "bindings.cfg" (which cfg file I > > can't locate on e17...) > > > > Speaking of which. I just booted my laptop into e17 and it has > > something that answers to "eesh --help" with a short list > > of options -e, -ewait, and "" interactive. All of which just sit there > > waiting for eesh to do something... So I think it just might currently > > be broken. <sigh> I hates "gui setup tools" more than Yosemite Sam ever > > hated "rabbits" And like Bugs, to me they are "real stinkers"... > > > > > You need to look into enlightenment_remote in e17. It has got command line > logout and keybinding settings. I thank you... enlightenment_remote looks to be as close to what I'm looking for in e17 as I'm ever going to get. It's going to take a bit to figure out how to use some of it's features though. I don't suppose there's a good tutorial or How-To around that doesn't assume the user understands the syntax or terminology used... (looking at "enlightenment_remote --help" it took me at least five minutes to get the idea that "OPT1" wasn't the literal name of some options file) I did find the the -logout, -shutdown, & -reboot options interesting. I did a partial test. I was disappointed two learn that these options don't bypass the confirmation pop-ups That still don't listen to the keyboard... Though actually I "LIKE" a confirmation that I hadn't just fat-fingered a keybinding... I just want a KEYbinding for confirming that I want to logout... On the other hand as a startx user I was pleased to learn that the -shutdown will actually get the 'puter to poweroff (after I "click" on the confirmation box of course...) It usually seams that this is only available for normal users when they logged in via something like kdm or gdm... Or when they have the time to enter a password for su or sudo. > If you use zsh, then put the following lines in your ~/.zshrc (I don't > know if there is an equivalent setting for bash shell): > > # Completion for enlightenment_remote > compdef _gnu_generic enlightenment_remote > > The above will provide you with basic command completion of > enlightenment_remote's options :) I'm not so wild about command completion I'm more likely to open two xterms. Run "enlightenment_remote --help|less" on one and run specific configuration commands on the other... > Once you have setup your key, mouse, etc bindings you can use this script > to store them as a bash executable file (a lot of other settings are also > stored): > http://ppurka.googlepages.com/e17_setup.sh Thanks again! does this mean I can save the setup to a file and then load that file into an e17 installation on another linux install to "clone" the environment. Heck even if "enlightenment_remote" didn't offer hope of eventually knowing enough to bypass the gui tools, the ability to only have to do it once. . . . (wow!) -- | ^^^ ^^^ | <O> <O> Joe (theWordy) Philbrook | ^ J(tWdy)P | \___/ <<jt...@tt...>> |