Re: X11 2.3.1 on Macbook Pro, Enlightenment, request for feedback on issues
Re: X11 2.3.1 on Macbook Pro, Enlightenment, request for feedback on issues
- Subject: Re: X11 2.3.1 on Macbook Pro, Enlightenment, request for feedback on issues
- From: Jeremy Huddleston <email@hidden>
- Date: Wed, 24 Sep 2008 13:04:26 -0700
On Sep 24, 2008, at 12:07, Dave Ray wrote:
1. X11 environment tells X11 apps that screen area's top left corner
is at actual top corner of display, instead of just below the OS-X
menu. This is a showstopper for the Enlightenment window manager.
Enlightenment window manager puts a thin horizontal bar at the top
of the screen, which is a "grab bar" for the different workspaces.
Under Apple's stock X11 implementation, Enlightenment would draw the
grab bar just below OS-X's menu bar. Workspaces could be grabbed,
moved as they were designed. Under the development X11 2.3.1,
Enlightenment draws the grab bars underneath the OS-X menu bar, so
they are invisible and inaccessible. I can switch workspaces other
ways within the window manager, but this is a major impediment. It
would be better if the X11 screen area was below the OS-X menubar.
Is there a setting I am missing, or something I could add to a
config file to take care of this?
Hmm... this is going to be a pickle to deal with. We're reporting the
full screen size because that is what is going to be used when we
enable full screen support in the WM or when we enable rooted mode
(also fullscreen without the mac menu bar)...
I'll probably have to add in some logic for the transition between
these phases much like when a new monitor is plugged in... hmm...
2. Fullscreen option is greyed out in the preferences, not
available. Is this a known issue? Is there a trick to activating it?
No, it's not yet supported (hence why it's greyed out).
3. An xterm is being launched by X11.app, before it is executing
~/.xinitrc. Usually this is the result of a default xinitrc file or
something similar left over from an installer. I have searched and
cannot find any config file telling it to launch an xterm before my
window manager. The xterm command is showing up in the console log
as an argument to the X11 launch command. I can't find where it's
coming from, it's not in~ /Library/Preferences/org.x.X11.plist, not
in /System/Library/LaunchDaemons/org.x.privileged_startx.plist, not
in /usr/X11/lib/X11/xinit/xinitrc, not in ~/.xinitrc. Any
suggestions? If it is compiled in I would suggest taking it out,
anyone using a development release should know how to add their own
~/.xinitrc.
http://xquartz.macosforge.org/trac/wiki/X11-UsersFAQ#Suppressingxtermlaunchingbydefault
Under Apple's X11, when I start X11, only what I have in my .xinitrc
file is launched. When I exit the window manager with its own X11-
based menus, X11.app also exits automatically. This would be the
desirable behavior for the development X11 release.
That is the behavior. We are using xinit, so this behavior is the
same on OSX as it is on Linux.
Is there a file I have missed, or something I could add to a config
file to take care of this?
4. I'm getting some warnings at the console when I start up X11.
Does anybody want to see these?
Not unless they say something to the effect of "Report this bug" or
you actually have a problem. There's a lot of debug spew right now to
help with debugging.
5. There may be some differences in keybindings, I'm still trying to
check this.
Yeah... keymapping sucks in X11 without the headache of OSX on top of
it.
--Jeremy
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden