July 2010 - XEmacs-Beta - XEmacs Mailing List Archives

state of "prerelease" packages? 14 years, 4 months

Richard Cook

So would it be a nightmare for me to choose the prerelease packages under the Packages menu? Any advantage/disadvantage to that? -- ✐Richard Cook ✇ Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ☎ (office) (925) 423-9605 ☎ (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/mailman/listinfo/xemacs-beta

2 participants
2 comments

RE: query - help 14 years, 4 months

Mike Kupfer

----- Message from anand.g.shanmugam(a)alcatel-lucent.com --------- > Yes, you are correct , We just keep our solaris (workshop, teamware) > as it is , only users will be moved to windows Desktop , we don't > prefer to use cygwin , xmanager to connect solaris from Desktop, > > Just we need a Xemacs in Desktop, through which we can access > solaris (workshop, teamware ) from Desktop. Alas, I suspect that what you're looking for doesn't exist. While I'm not familiar with the Teamware package for Emacs, I strongly suspect that it's just a wrapper over the Teamware command-line interface (bringover, putback, workspace, etc). So if you don't want to connect to the Solaris systems using X, I don't know that there are any other options available. Sorry I couldn't be of more help. mike _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Was: VS-2008 files and patch to make it build 14 years, 4 months

Robin Paterson

Guys, Sorry I'm coming to this discussion a bit late. Win XPx64 SP2, VS2008 Pro, XEmacs-21.5.29, native build without cygwin I've struggled with this for a while, but I made a good go of it last night and I've a couple of observations I'd like to share before I do anything else. [1] unicode-encapsulate. The only way I could get this to run properly was to go to the Windows SDK dir (I'm using v6.0A) and remove all the decorations from a load of functions in 14 header files. I'm referring here to __in, __out_, __in_opt, etc. I'm sure with some tweaking of make-mswin-unicode.pl a more elegant solution could be achieved. Or have I missed something? [2] In order to make the SHQUERYRBINFO struct visible from ShellAPI.h, I had to add a couple of defs to xemacs.mak (these were mentioned earlier in this thread). -DNTDDI_VERSION=NTDDI_WINXPSP2 -D_WIN32_WINNT=_WIN32_WINNT_WINXP [3] dumper.c (2648) qxeGetModuleFileName had an unwanted cast. /* cchpathsize = qxeGetModuleFileName (NULL, (Extbyte *) exe_path, bufsize); */ cchpathsize = qxeGetModuleFileName (NULL, exe_path, bufsize); [4] intl-auto-encap-win32.c had a few wrapper functions which used a wide type in the interface and then tried to use this wide type in a narrow call. Nasty hack used to get this to limp along. int qxeMessageBoxIndirect (CONST MSGBOXPARAMSW * lpmbp) { if (XEUNICODE_P) return MessageBoxIndirectW (lpmbp); else return -1; /* MessageBoxIndirectA (lpmbp); */ } As this file is autogened by make-mswin-unicode.pl, my hacks are plain nasty. [5] win32.c (165) qxeGetModuleFileName was missing a cast. (TBH, I've not type checked this :-( - there's clearly a type issue here though between Extbyte and WCH) [6] The optional jpeg lib wouldn't link. I took the easy option and downloaded another prebuilt one for VS2008. This got things to compile and link, but I've still to resolve the makeinfo stage (not a big worry). Firstly, have I missed something? Is there something I could do which would resolve these issues or, as seems, is building using MS tools waaay down the list of things to do? It looks like a config step is needed to set the NTDDI_VERSION and _WIN32_WINNT. make-mswin-unicode.pl needs a hand filtering some of those header files however, I'm not 100% on the types used and interfaces generated, so there may be some other work required here involving dumper.c, win32.c (and intl-auto-encap-win32.c). Questions? Comments? Education & instruction? ;-) Thanks. -R. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/mailman/listinfo/xemacs-beta

3 participants
2 comments

Re: Was: VS-2008 files and patch to make it build 14 years, 4 months

Adrian Aichner

Hi Robin, I have a version of the perl Script which can handle these annotation. I'll send Adrian Aichner Am 27.07.2010 17:30 schrieb "Robin Paterson" <scot_paro(a)yahoo.co.uk>: Guys, Sorry I'm coming to this discussion a bit late. Win XPx64 SP2, VS2008 Pro, XEmacs-21.5.29, native build without cygwin I've struggled with this for a while, but I made a good go of it last night and I've a couple of observations I'd like to share before I do anything else. [1] unicode-encapsulate. The only way I could get this to run properly was to go to the Windows SDK dir (I'm using v6.0A) and remove all the decorations from a load of functions in 14 header files. I'm referring here to __in, __out_, __in_opt, etc. I'm sure with some tweaking of make-mswin-unicode.pl a more elegant solution could be achieved. Or have I missed something? [2] In order to make the SHQUERYRBINFO struct visible from ShellAPI.h, I had to add a couple of defs to xemacs.mak (these were mentioned earlier in this thread). -DNTDDI_VERSION=NTDDI_WINXPSP2 -D_WIN32_WINNT=_WIN32_WINNT_WINXP [3] dumper.c (2648) qxeGetModuleFileName had an unwanted cast. /* cchpathsize = qxeGetModuleFileName (NULL, (Extbyte *) exe_path, bufsize); */ cchpathsize = qxeGetModuleFileName (NULL, exe_path, bufsize); [4] intl-auto-encap-win32.c had a few wrapper functions which used a wide type in the interface and then tried to use this wide type in a narrow call. Nasty hack used to get this to limp along. int qxeMessageBoxIndirect (CONST MSGBOXPARAMSW * lpmbp) { if (XEUNICODE_P) return MessageBoxIndirectW (lpmbp); else return -1; /* MessageBoxIndirectA (lpmbp); */ } As this file is autogened by make-mswin-unicode.pl, my hacks are plain nasty. [5] win32.c (165) qxeGetModuleFileName was missing a cast. (TBH, I've not type checked this :-( - there's clearly a type issue here though between Extbyte and WCH) [6] The optional jpeg lib wouldn't link. I took the easy option and downloaded another prebuilt one for VS2008. This got things to compile and link, but I've still to resolve the makeinfo stage (not a big worry). Firstly, have I missed something? Is there something I could do which would resolve these issues or, as seems, is building using MS tools waaay down the list of things to do? It looks like a config step is needed to set the NTDDI_VERSION and _WIN32_WINNT. make-mswin-unicode.pl needs a hand filtering some of those header files however, I'm not 100% on the types used and interfaces generated, so there may be some other work required here involving dumper.c, win32.c (and intl-auto-encap-win32.c). Questions? Comments? Education & instruction? ;-) Thanks. -R. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/mailman/listinfo/xemacs-beta _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Re: Was: VS-2008 files and patch to make it build 14 years, 4 months

Vin Shelton

I'm currently building with Visual Studio 6. I once made the effort (& checked in the results?) to get the sources to build w/VS2005, but I found the manifest files annoying and went back to VS6. Ben made some significant changes to the sources since I did my VS2005 work. Sorry for any msg formatting difficulties. I'm sending this from my from because I lost external email access at work. Rgds, Vin On Jul 27, 2010 11:28 AM, "Robin Paterson" <scot_paro(a)yahoo.co.uk> wrote: Guys, Sorry I'm coming to this discussion a bit late. Win XPx64 SP2, VS2008 Pro, XEmacs-21.5.29, native build without cygwin I've struggled with this for a while, but I made a good go of it last night and I've a couple of observations I'd like to share before I do anything else. [1] unicode-encapsulate. The only way I could get this to run properly was to go to the Windows SDK dir (I'm using v6.0A) and remove all the decorations from a load of functions in 14 header files. I'm referring here to __in, __out_, __in_opt, etc. I'm sure with some tweaking of make-mswin-unicode.pl a more elegant solution could be achieved. Or have I missed something? [2] In order to make the SHQUERYRBINFO struct visible from ShellAPI.h, I had to add a couple of defs to xemacs.mak (these were mentioned earlier in this thread). -DNTDDI_VERSION=NTDDI_WINXPSP2 -D_WIN32_WINNT=_WIN32_WINNT_WINXP [3] dumper.c (2648) qxeGetModuleFileName had an unwanted cast. /* cchpathsize = qxeGetModuleFileName (NULL, (Extbyte *) exe_path, bufsize); */ cchpathsize = qxeGetModuleFileName (NULL, exe_path, bufsize); [4] intl-auto-encap-win32.c had a few wrapper functions which used a wide type in the interface and then tried to use this wide type in a narrow call. Nasty hack used to get this to limp along. int qxeMessageBoxIndirect (CONST MSGBOXPARAMSW * lpmbp) { if (XEUNICODE_P) return MessageBoxIndirectW (lpmbp); else return -1; /* MessageBoxIndirectA (lpmbp); */ } As this file is autogened by make-mswin-unicode.pl, my hacks are plain nasty. [5] win32.c (165) qxeGetModuleFileName was missing a cast. (TBH, I've not type checked this :-( - there's clearly a type issue here though between Extbyte and WCH) [6] The optional jpeg lib wouldn't link. I took the easy option and downloaded another prebuilt one for VS2008. This got things to compile and link, but I've still to resolve the makeinfo stage (not a big worry). Firstly, have I missed something? Is there something I could do which would resolve these issues or, as seems, is building using MS tools waaay down the list of things to do? It looks like a config step is needed to set the NTDDI_VERSION and _WIN32_WINNT. make-mswin-unicode.pl needs a hand filtering some of those header files however, I'm not 100% on the types used and interfaces generated, so there may be some other work required here involving dumper.c, win32.c (and intl-auto-encap-win32.c). Questions? Comments? Education & instruction? ;-) Thanks. -R. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/mailman/listinfo/xemacs-beta _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Re: [Bug: 21.4.22] windows 7 14 years, 4 months

Vin Shelton

Howard - I had written: >>>> Thanks for the bug report. Can you describe exactly what you did, >>>> and exactly what message you received? >>>> >>>> My guess would be that the name of the directory XEmacs should be >>>> looking in has spaces in it. Under native Windows this can present >>>> a problem. Howard had written: >>> I tried uninstalling and reinstalling in a directory with no >>> spaces, but that did not help. More recently, he wrote again: >> Any other thoughts? This is that last piece I need to make my new >> machine fully functional for me, so I would love to get it done. My reply: > I was actually thinking along the same lines as Rodney Sparapani. > I was thinking about the value of your HOME directory, not the > installed directory. What does: > > (find-user-init-file)^J > > report in the *scratch* buffer? On Tue, Jul 27, 2010 at 6:52 AM, Georgi, Howard wrote: > Never did find the (find-user-init-file)^J but got me asking the > right questions. It was looking in a c:/users/hgeorgi/.xemacs and > the directory didn't exist. I created it and was able to save an > init.el file from my old machine and now things seem to be working. > Thanks very much for your help. Good to know. I've copied the list for future reference. - Vin _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/mailman/listinfo/xemacs-beta

2 participants
1 comments

Summary of XEmacs Issue Tracking System Issues 14 years, 4 months

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2010-07-20 - 2010-07-27) XEmacs Issue Tracking System at http://tracker.xemacs.org/XEmacs/its/ To view or respond to any of the issues listed below, click on the issue number. Do NOT respond to this message. 488 open ( +3) / 234 closed ( +0) / 722 total ( +3) Open issues with patches: 12 Average duration of open issues: 617 days. Median duration of open issues: 659 days. Open Issues Breakdown new 163 ( +1) deferred 6 ( +0) napping 4 ( +0) verified 46 ( +0) assigned 154 ( +2) committed 25 ( +0) documented 2 ( +0) done/needs work 24 ( +0) Issues Created Or Reopened (3) ______________________________ The Reason and Superseder fields should be in the same column 2010-07-21 http://tracker.xemacs.org/XEmacs/its/issue722 created stephen Message sent to tracker does not get added to issue 2010-07-23 http://tracker.xemacs.org/XEmacs/its/issue723 created stephen "Selection Aborted" error after clicking in frame with Compiz 2010-07-24 http://tracker.xemacs.org/XEmacs/its/issue724 created mike.kupfer Issues Now Closed (4) _____________________ [Bug: 21.4.21] flyspell does not work with local tables, aucte 158 days http://tracker.xemacs.org/XEmacs/its/issue680 stephen Lock down keyword creation against spammers (solucionesroot)? 148 days http://tracker.xemacs.org/XEmacs/its/issue690 stephen [Bug: 21.4.21] matlab-shell does not start: msg 145 days http://tracker.xemacs.org/XEmacs/its/issue692 stephen [Bug: 21.4.21] Mule+xsymbol: math symbols corrupted 137 days http://tracker.xemacs.org/XEmacs/its/issue694 stephen _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

RE: query - help 14 years, 4 months

SHANMUGAM, ANAND G (ANAND)

Good day Stephen, Thanks for your info, We're using emacs21 0n solaris (workshopp6.2 , teamware ddts ), it works fine and we're using it for a long period, Now, we've decided to migrate our platform & environment to windows OS, to accomplish that we neeed a emacs version in windows which will connect to teamware environment in solaris . Attached screenshot is for your reference , Do the needful. Thanks, Anand -----Original Message----- From: Stephen J. Turnbull [mailto:stephen＠xemacs.org] Sent: Saturday, July 24, 2010 8:19 PM To: SHANMUGAM, ANAND G (ANAND) Cc: xemacs-services(a)xemacs.org Subject: query - help SHANMUGAM, ANAND G (ANAND) writes: > We're using emacs on solaris and also sun Teamware environment . > We had planned to use Xemacs on windows, Pleased to hear it. However, questions on using XEmacs (including installation) are best asked at or in the comp.emacs.xemacs newsgroup. The XEmacs Services team maintains various infrastructure services (such as the web site and mailing lists), and only a small fraction of the people who can answer your questions will see them if addressed to webmaster (and quite likely your question will be answered with the stock answer: ask again on xemacs-beta). > could you tell me the procedure to install on windows Download an installer from http://www.xemacs.org/Download/win32/, and execute it as usual. If you are working in an ASCII or ISO 8859-1 environment, XEmacs 21.4 is probably a little more polished and should work. However, its Unicode support is poor. If you need support for other encodings (not limited to Unicode, but also including encodings like EUC for Japanese or Chinese and KOI8 for Cyrillic scripts), then XEmacs 21.5 is strongly recommended despite its "beta" status. Make sure you install any needed add-on libraries. XEmacs is not big by modern standards; I recommend that you install all available packages in the installer (even though the default configuration has only a fraction of them). This costs only diskspace if you don't use them, since they are demand-loaded. > and to use the teamware using xemacs . I suggest that you ask Sun about their Teamware product. You can try reposting your question about Teamware to xemacs-beta(a)xemacs.org, but I don't think I've ever heard a question about Teamware before; I don't think anybody on that list is using it. Steve for the XEmacs Services team _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/mailman/listinfo/xemacs-beta

2 participants
2 comments

Re: slow startup for xemacs on Darwin 14 years, 4 months

Richard Cook

If I build using your flags it works for me. So it seems that linking in the wrong X11 libs is the problem here and it's a MacPorts issue. On Jul 24, 2010, at 8:06 AM, robert delius royar wrote: > Fri, 23 Jul 2010 (18:00 -0700 UTC) Richard Cook wrote: > >> YES IT WOULD! Hmm. That's likely to be the problem. But why is a text editor checking the network again? Anyhow, I did hack the source of process-unix.c: unix_canonicalize_host_name() >> >> Changed >> >> LISP_STRING_TO_EXTERNAL (host, ext_host, Qnative); >> + if (strstr(ext_host, "/tmp/launch") != NULL) { >> + ext_host = strdup("localhost"); >> + } >> retval = getaddrinfo (ext_host, NULL, &hints, &res); >> >> Yes, it's a hack, but it works. Of course it seems the correct fix is to point at the XQuartz X11 libraries instead of something dragged into /opt/local/lib: > > All of the statements below are about > XEmacs 21.5 (beta29) "garbanzo" fca0cf0971de configured for `powerpc-apple-darwin9.8.0'. > or > XEmacs 21.5-b29 "garbanzo" fca0cf0971de configured for `i386-apple-darwin10.4.0'. > > I believe that the library interference is at the root of your problem. > I use some macports libraries, but I do not switch out the ones that > Xquartz or the system supplies. I compile it for Leopard G5 and i386 > and for SL i386. I use the i386 version from SL at home and work and > the i386 Leopard at work. I run a local DNS at home for my network > (helps the TiVo and iPods). Each machine has a dedicated IP that my two > routers respect. I use host information files in /var/named. At school > all the DNS is handled by my school's network admins. I do not see a > slowdown for starting XEmacs on any of my systems. [I used also to run > XEmacs on an EeePC Linux system with basically the same configuration). > > Here are some outputs (on my Leopard G5) for variables that relate to > x-display DEVICE and hostname: > (system-name) > "grendel.frinabulax.org" > (device-list) > (#<x-device on "/tmp/launch-Z1M232/org.x:0.0" 0x2>) > > Here is the bash routine in my XEmacs build script for use on an Intel > machine (Snow Leopard version): > > WK_ACONFIG () { > if [ "$MACHTYPE" = "powerpc" ] ; then > echo "Will not configure the i386 build for a powerpc," > echo "using the work config instead." > WK_CONFIG > else > export PKG_CONFIG_PATH=/opt/X11/lib/pkgconfig > RM_Installation > if [ "${XEMACS_CONFIGURE}" ] ; then > ./configure "${XEMACS_CONFIGURE}" > else > export CFLAGS="-arch i386" > export LDFLAGS='-L/usr/lib -lncurses -lz -L/opt/X11/lib -lpng -lXpm > -lXft -lXrender -lXt -lXext -lX11 -lSM -lICE -lfontconfig > -L/opt/local/lib -lgmp -ltiff -ljpeg -lesd' > ./configure --with-mule \ > --with-scrollbars=lucid --with-widgets=athena --with-athena=xaw --with-dialogs=athena \ > --without-error-checking --with-bignum=gmp \ > --prefix=${ParentPath} --with-png --with-jpeg --with-tiff \ > --with-xim=no --enable-sound=none,esd --disable-xfs \ > --enable-dump-in-exec --with-compiler=gcc-4.2 \ > --disable-kkcc --without-ipv6-cname --without-ldap \ > --with-xft=emacs,gauges,tabs --with-union-type --enable-optimization > fi > fi > } > > Note that on Leopard, I use a routine that has -L/usr/X11/lib > rather than -L/opt/X11/lib. I compile the source in my home directory > and set $ParentPath to /Users/royar/usr/local > > Here is the output from otool -l on my Snow Leopard MBP: > grendal% otool -L ~/usr/local/bin/xemacs-21.5-b29 > /Users/royar/usr/local/bin/xemacs-21.5-b29: > /usr/lib/libncurses.5.4.dylib (compatibility version 5.4.0, current version 5.4.0) > /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3) > /opt/X11/lib/libpng14.14.dylib (compatibility version 18.0.0, current version 18.0.0) > /opt/X11/lib/libXpm.4.dylib (compatibility version 16.0.0, current version 16.0.0) > /opt/X11/lib/libXft.2.dylib (compatibility version 4.0.0, current version 4.13.0) > /opt/X11/lib/libXrender.1.dylib (compatibility version 5.0.0, current version 5.0.0) > /opt/X11/lib/libXt.6.dylib (compatibility version 7.0.0, current version 7.0.0) > /opt/X11/lib/libXext.6.dylib (compatibility version 11.0.0, current version 11.0.0) > /opt/X11/lib/libX11.6.dylib (compatibility version 10.0.0, current version 10.0.0) > /opt/X11/lib/libSM.6.dylib (compatibility version 7.0.0, current version 7.1.0) > /opt/X11/lib/libICE.6.dylib (compatibility version 10.0.0, current version 10.0.0) > /opt/X11/lib/libfontconfig.1.dylib (compatibility version 6.0.0, current version 6.3.0) > /opt/local/lib/libgmp.10.dylib (compatibility version 11.0.0, current version 11.1.0) > /opt/local/lib/libtiff.3.dylib (compatibility version 13.0.0, current version 13.4.0) > /opt/local/lib/libjpeg.8.dylib (compatibility version 9.0.0, current version 9.2.0) > /opt/local/lib/libesd.0.dylib (compatibility version 3.0.0, current version 3.39.0) > /usr/lib/libexpat.1.dylib (compatibility version 7.0.0, current version 7.2.0) > /usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) > /opt/X11/lib/libfreetype.6.dylib (compatibility version 12.0.0, current version 12.1.0) > /opt/X11/lib/libxcb.1.dylib (compatibility version 3.0.0, current version 3.0.0) > /opt/X11/lib/libXau.6.dylib (compatibility version 7.0.0, current version 7.0.0) > /opt/X11/lib/libXdmcp.6.dylib (compatibility version 7.0.0, current version 7.0.0) > /opt/X11/lib/libXaw.7.dylib (compatibility version 8.0.0, current version 8.0.0) > /opt/X11/lib/libXmu.6.dylib (compatibility version 9.0.0, current version 9.0.0) > /opt/local/lib/libgdbm.3.dylib (compatibility version 4.0.0, current version 4.0.0) > /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio (compatibility version 1.0.0, current version 1.0.0) > /opt/local/lib/libaudiofile.0.dylib (compatibility version 1.0.0, current version 1.2.0) > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.0) > /opt/local/lib/libintl.8.dylib (compatibility version 10.0.0, current version 10.1.0) > > Hope this helps. > >> cook47＠rcmac (xemacs-21.5.29-without-ipv6-cname): otool -L /opt/local/bin/xemacs >> /opt/local/bin/xemacs: >> /opt/local/lib/libXaw3d.8.dylib (compatibility version 8.0.0, current version 8.0.0) >> /opt/local/lib/libtiff.3.dylib (compatibility version 13.0.0, current version 13.4.0) >> /opt/local/lib/libpng12.0.dylib (compatibility version 45.0.0, current version 45.0.0) >> /opt/local/lib/libjpeg.8.dylib (compatibility version 9.0.0, current version 9.2.0) >> /opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5) >> /opt/local/lib/libcompface.0.dylib (compatibility version 1.5.2, current version 1.5.2) >> /opt/local/lib/libXpm.4.dylib (compatibility version 16.0.0, current version 16.0.0) >> /opt/local/lib/libXmu.6.dylib (compatibility version 9.0.0, current version 9.0.0) >> /opt/local/lib/libXt.6.dylib (compatibility version 7.0.0, current version 7.0.0) >> /opt/local/lib/libXext.6.dylib (compatibility version 11.0.0, current version 11.0.0) >> /opt/local/lib/libX11.6.dylib (compatibility version 10.0.0, current version 10.0.0) >> >> I tried setting DYLD_LIBRARY_PATH to /usr/X11/lib but then I get an error when I run /opt/local/bin/xemacs: >> >> dyld: Library not loaded: /opt/local/lib/libpng12.0.dylib >> Referenced from: /opt/local/bin/xemacs >> Reason: Incompatible library version: xemacs requires version 45.0.0 or later, but libpng12.0.dylib provides version 42.0.0 >> Trace/BPT trap >> >> >> >> On Jul 23, 2010, at 5:45 PM, Hamish Macdonald wrote: >> >>> Would the MacPorts version of xemacs be using its own libX11 rather than the one provided by Mac OS X? That would be dumb...... >>> >>> On Fri, Jul 23, 2010 at 8:41 PM, Hamish Macdonald <hamishimac(a)gmail.com> wrote: >>> On Fri, Jul 23, 2010 at 8:09 PM, Richard Cook <rcook(a)llnl.gov> wrote: >>> I actually found out what xemacs is doing. It is calling >>> getaddrinfo("/tmp/launch-gcmVOm/org.macosforge.xquartz", ...); >>> That comes from the DISPLAY name. Why is it doing this, and can I tell it not to? On Mac OS X, this is the weird name that DISPLAY gets set to to get direct rendering. It does not work to set DISPLAY to ":0". I don't want to use DISPLAY="rcmac.llnl.gov:0" because that will cause it to hit the NIC instead of go straight to the card for rendering. >>> >>> Hmm... Just checked on my Mac. The display name is set to "/tmp/launch-TkSI95/org.x:0". That's a really curious format for a "local" display string. On my Mac, when I run "xterm" under X, that file is a local socket. A local transport mechanism like that should really not have a colon in it. This appears to confuse some software into thinking it is a "hostname:0" display variable format, so it tries to lookup "hostname". >>> >>> I still agree with others that your DNS is broken; if it cannot come back and tell you quickly that the hostname "/tmp/launch-gcmVOm/org.macosforge.xquartz" can't be resolved, its broken. >>> >>> However, I wonder why xemacs is trying to resolve this address. Local X applications on my system don't appear to do a DNS lookup when I use a display name like "/tmp/foo/bar/baz:0", so why does xemacs? Is it possible that either XEmacs is not using the locally installed XLIB library? Is XEmacs performing its own interpretation of the DISPLAY environment variable (that would be a bad idea). >>> >>> Regards, >>> Hamish. >>> >> >> > > -- > Dr. Robert Delius Royar Associate Professor of English > Morehead State University Morehead, Kentucky > > _______________________________________________ > XEmacs-Beta mailing list > XEmacs-Beta(a)calypso.tux.org > http://*calypso.tux.org/mailman/listinfo/xemacs-beta > -- ✐Richard Cook ✇ Lawrence Livermore National Laboratory Bldg-453 Rm-4024, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ☎ (office) (925) 423-9605 ☎ (fax) (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL) _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/mailman/listinfo/xemacs-beta

1 participants
1 comments

Re: slow startup for xemacs on Darwin 14 years, 4 months

Stephen J. Turnbull

Richard Cook writes: > Not for me! If I set DISPLAY=:0, it does not display! How messed up is that? > cook47＠rcmac (~): DISPLAY=:0 xterm > xterm Xt error: Can't open display: :0 Oh, are you on Snow Leopard? I'm still on Leopard, although I have Xquartz 2.5 installed (and in use, I think). > I don't understand the LISP side of xemacs at all. But it does > appear from the call stack that LISP is involved here. Maybe there > is something that can be put in the .xemacs file? Right, that's what I'd like. Or better yet, something that gets hooked on Mac OS X at initialization. > I'm definitely weak at xemacs configuration. Er, I have no problem with calling you "highly optimized". :-) If "text editor" is what you want, it should be possible for us to give you one that exceeds expectations in almost all ways (modulo proprietary dehancements... :-). _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/mailman/listinfo/xemacs-beta

2 participants
1 comments

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta July 2010