Seiji Zenitani
zenit****@mac*****
Wed Sep 20 06:18:00 JST 2006
Hi, An updated patch arrived just now! Could you try the new one? Reportedly "unexpected async reply" has gone. http://macemacsjp.sourceforge.jp/package/test/ transparency2-20060920.patch In our environment (Gentoo AMD64), transparency excellently works on XGL. On X.org, emacs works without throwing critical errors, but transparency does not work. It still needs a way to go. -- Seiji > Hello! > > I integrated the patch into the GNU Emacs 22.0.50 sources. Now my > Carbon Emacs shows transparency. The X client regularly fails at > launch with: > > Xlib: unexpected async reply (sequence 0x1a7)! > > Nothing else happens, no core, no crash log. I think what's missing > is some code that determines whether the X server can handle > transparency. If not, no such calls are emitted, so that default- > frame-alist and initial-frame-alist need not be changed to just just > accept the transparency settings. > > > In case of Unicode Emacs 23.0.0 three patches could not be applied, > because there was code for the font-backend extension in place. By > hand they could be added. The X client has a slightly different > problem: > > Xlib: unexpected async reply (sequence 0x19a)! > > Again nothing else happens. > > Creating Carbon Emacs 23.0.0 did not succeed yet for me: macterm.c > does not compile with CFLAGS like -DUSE_MAC_FONT_PANEL or - > DUSE_ATSUI, which is really hard to understand! > > > I have no idea how to trace the reason for the Xlib errors. Could be > I try to install Xorg 6.8 some day with Fink – the problem is that > this install can again change some things in Fink that cannot be > undone so easily ... > > -- > Greetings > > Pete > > Globalisation -- communism from above. > > > > _______________________________________________ > macemacsjp-english mailing list > macem****@lists***** > http://lists.sourceforge.jp/mailman/listinfo/macemacsjp-english
