X11 2.3.1 on Macbook Pro, Enlightenment, request for feedback on issues
X11 2.3.1 on Macbook Pro, Enlightenment, request for feedback on issues
- Subject: X11 2.3.1 on Macbook Pro, Enlightenment, request for feedback on issues
- From: Dave Ray <email@hidden>
- Date: Wed, 24 Sep 2008 12:07:22 -0700
My first post to this list.
Summary: Seasoned X11 & OS-X user. Just upgraded from 10.5.5 Apple X11
to 2.3.1 for the first time, using Enlightenment WM. Wanted to share
experiences and request feedback on issues. Please help me determine
if my issues are already reported, known workarounds, or if there is
new information I should send as a bug report.
Environment: OS-X 10.5.5, XCode 3.1.1, X11 2.3.1, Macbook Pro 2.4 GHz,
2GB RAM
OS-X preferences: Input - all options checked; Output - colors from
display, options not checked; Windows - focus on new windows; Security
- authenticate connections
X environment: Enlightenment 0.16.8.14, Eterm 0.9.5
Enlightenment and Eterm run well under X11. These were natively
compiled into /usr/local, not part of darwinports or fink. Most major
features work as well under the development X11 2.3.1 as they did
under the stock X11 from 10.5.5 and 10.5.4, although there are some
issues. I have not attempted to run esd or sound support yet.
I compiled these with tools from Xcode 3.1.1, at a time when I was
still running OS-X 10.5.4 and the previous Apple X11 environment.
Enlightenment and ETerm worked well under that environment. I upgraded
to 10.5.5 and had some of the same problems people reported here, with
X11 not initially running after the upgrade. I managed to get my X11
system working again, and then upgraded to the X11 2.3.1 development
release. So I was able to compare a known working Enlightenment window
manager setup between 3 different X11 distributions (both Apple
distros + 2.3.1). Here are some issues affecting the usability of
Enlightenment as follows:
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?
2. Fullscreen option is greyed out in the preferences, not available.
Is this a known issue? Is there a trick to activating it?
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.
It doesn't get launched when I type "startx" in the terminal.
There are several undesirable side effects of this unwanted xterminal:
(a) it prevents X11.app from quitting automatically when the window
manager is exited through its own X11-based menu, since it is launched
before the window manager
(b) it is unusable anyway because of problem #1 above - the top of the
terminal window, where the prompt is, is under the OS-X menu!
(c) it is ugly
(d) every time I start X11 I have to click on that window and type
control-d
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.
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?
5. There may be some differences in keybindings, I'm still trying to
check this.
Thanks in advance,
-Dave
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden