I tried searching the archives for a couple of things I'd like to do.
I wasn't able to find anything relevant, so I figured I'd ask politely.
Maybe someone can give me an easy answer.
I'm a recent convert, having been an AfterStep user for something like
10 years. Unfortunately, AfterStep develop
[EMAIL PROTECTED] said:
> One of those features was the ability to force a window to always be at the
> back relative to all of the other windows.
Duh.
I found the "Stacking" window attribute in the window menus. I don't know
why my brain didn't register that before. :-(
Still it would be nice
[EMAIL PROTECTED] said:
> we could tell you - but that wouldn't be as much fun :)
:-)
The fastest way to figure something out is to open your mouth and say
you can't figure it out. I swear I looked at that menu,... really.
So where is the iconbox position defined?
Thanks.
john-
--
Is there a way to move the mouse cursor via keyboard? I haven't found
a keymapping to do that.
Also I'd like to be able to move/resize windows via keyboard. For instance,
map a keystroke to Window Move, which would cause the active window's
position to follow cursor movement (see above) until I
[EMAIL PROTECTED] said:
> e16 has a nifty feature which allows regular bash scripts to be run on
> startup, restart, and shutdown. This differs from e17 in that you don't need
> to create eap files.
> I have an script in .e16/Init that reads:
Peter,
If I may ask, what version of E are you run
A long time, in a version far, far away (circa 2001), I could use
esdctl to pause/resume esd and it didn't matter what user I was.
Fast-forward to a more recent version (Mandrake 10.0 release), and
even though the permissions on the socket are 777 I can only talk
to the server if I'm the user th
[EMAIL PROTECTED] said:
> John Meissen said:
> >I can only talk to the server if I'm the user that started it.
> >
> The user who launched esd must type 'esdctl unlock' to let other user
> use this daemon, I think. Does it solve the problem ?
I swear I t
[EMAIL PROTECTED] said:
> John Meissen said:
> >I can only talk to the server if I'm the user that started it.
> >
> The user who launched esd must type 'esdctl unlock' to let other user
> use this daemon, I think. Does it solve the problem ?
Actually, I re
I said:
> What I need is for the -promiscuous option to work as documented. I added
> it to /etc/esd.conf, and I can see it in the process command-line. But it
> doesn't work.
In fact, it's even worse - it appears to have exactly the opposite effect.
Am I reading the man page wrong?
If I start
