April 2011 - XEmacs-Beta - XEmacs Mailing List Archives

Raymond Toy

Finally got around to building the latest version of xemacs. Basically the version before the gplv3 release on Friday. Everything went smoothly (except that I forgot to reconfigure so I was getting a splash screen that kept saying 21.5.29 instead of 30). It's been working fine after a few hours of normal usage, so I thought I'd do M-x build-report. That works until it tries to fill in the message buffer with the build information. The lisp backtrace is appended below. I ran src/xemacs to get this. If I try to run build-report using the my locally installed version, it's a bit worse. Same backtrace, but the subject line is [OK] XEmacs nil.nil "nil" nili386-apple-darwin10.7.0 When running from the build directory, the subject line is [OK] XEmacs 21.5-b30 "garlic" f2881cb841b4+ i386-apple-darwin10.7.0 Ray Debugger entered--Lisp error: (wrong-type-argument stringp nil) file-name-as-directory(nil) #<compiled-function (from "/Volumes/share2/darwin10.6/share/xemacs/xemacs-packages/lisp/build/build-report.elc") (f) "...(11)" [f expand-file-name file-name-as-directory gethash blddir config-value-hash-table] 6 0x1879>("beta.err") mapcar(#<compiled-function (from "/Volumes/share2/darwin10.6/share/xemacs/xemacs-packages/lisp/build/build-report.elc") (f) "...(11)" [f expand-file-name file-name-as-directory gethash blddir config-value-hash-table] 6 0x1879> ("beta.err" "xemacs-make-all.err" "xemacs-make-check-temacs.err" "xemacs-make-check.err" "xemacs-make-install.err")) build-report-make-output-get() #<compiled-function (from build-report) (&rest args) "...(220)" [major build-report-installation-file file report-begin G38203 G38202 file-exists-p build-report-installation-data 2 3 4 5 format "[%%s] XEmacs %s.%s%s \"%s\" %s%s" build-report-version-file-data compose-mail read-string "Build Report Destination: " build-report-destination apply nil reverse build-report-make-output-get build-report-insert-make-output "%s not found!\n" "\n" build-report-insert-installation-file build-report-insert-header minor beta codename extraname build-report-subject files configuration build-report-version-file system-configuration args build-report-installation-insert-all] 9 ("/Volumes/share2/darwin10.6/share/xemacs/xemacs-packages/lisp/build/build-report.elc" . 6656) (byte-code "Å«＠＠＠A＠<«\n＠AÆ ÇÂ#Bª`," [build-report-prompts prompt hist arg prompts nil read-string ""] 5) 0x187c>("OK") call-interactively(build-report) command-execute(build-report t) execute-extended-command(nil) call-interactively(execute-extended-command) (dispatch-event "[internal]") _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

cooking with cygwin 13 years, 8 months

Eric S. Johansson

I've started tricking out my cygwin environment to build xemacs under with X. is complaining about missing libraries and I don't know what packages I will need in order to complete the build. A few pointers please? _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

2 participants
1 comments

Re: XEmacs 21.5.30 "garlic" is released. 13 years, 8 months

Stephen J. Turnbull

Didier Verna writes: > BTW, the website is down so I cannot check if it has been updated :-) Which website? www.xemacs.org works fine for me. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

2 participants
1 comments

Summary of XEmacs Issue Tracking System Issues 13 years, 8 months

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2011-04-19 - 2011-04-26) 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. 517 open ( +0) / 242 closed ( +0) / 759 total ( +0) Open issues with patches: 11 Average duration of open issues: 842 days. Median duration of open issues: 878 days. Open Issues Breakdown new 184 ( +0) deferred 6 ( +0) napping 4 ( +0) verified 52 ( +0) assigned 155 ( +0) committed 26 ( +0) documented 2 ( +0) done/needs work 24 ( +0) _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Re: [RFC,CFT] mxedruli for xemacs/quail 13 years, 8 months

Aidan Kehoe

Hi Richard, Ar an dara lá is fiche de mí Aibréan, scríobh Richard: > could not find any package doing mxedruli input using latin keyboards so > I have created one. > > The input method is the same (except possibly for my bugs) like that of the > LaTeX packages described here: > http://heinecke.pagesperso-orange.fr/mxedruli/ > > Btw I have noticed that the "ლ" looks pretty poor when rendered by > Xemacs/XFT but exactly the same like when rendered by gedit (presumably > pango). Seems to be a font issue on my system, Firefox does it right > except for text area entry. This looks good; I’ve cross-checked for reasonableness with Wikipedia, and will cross-check with my copy of The World’s Writing Systems next weekend. Now, it would be useful to check with an actual Georgian as to what would be the most intuitive input method for them, but I don’t know any, even online. “ლ” also looks pretty poor when rendered by PuTTY on this Windows XP machine, for what that’s worth. Best, Aidan -- “Apart from the nine-banded armadillo, man is the only natural host of Mycobacterium leprae, although it can be grown in the footpads of mice.” -- Kumar & Clark, Clinical Medicine, summarising improbable leprosy research _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Re: xemacs-gtk now displaying unicode 13 years, 8 months

Stephen J. Turnbull

Marcus Harnisch writes: > I guess in the dicussion it is not entirely clear what people refer to > when they claim GTK wasn't as good, the toolkit or our current port. My > point is that GTK itself (versions 2 or 3) probably *is* already as good > and offers many advantages already. We just have to get started :-) My claim is the latter, ie, that GTK v1's time is almost 10 years past, and the port needs to be updated before any proposal to make GTK default for X windows deserves a response more serious than "Are you kidding?" I consider Jeff's Pango work to be a useful incentive for somebody to do that upgrade, but not at all a substitute for it. As far as GTK being as good across the board, and offering advantages in some areas, that depends on who you are. I really don't see any obvious advantages *to me*, only IAGNIs and disadvantages. So any work I do towards the GTK port in the near future will be at the expense of stuff I can use myself. > can't even be bothered checking the facts. Well, that's true to some extent. It's certainly true that I've never done what Jeff just did, and actually code things up. However, for any number of projects I've had to investigate GTK/GNOME-related stuff, and (maybe I'm just old, but) GTK programming, *especially* that parts implementing the kind of desktop integration you are talking about, never really made sense to me. My impression was that it's going to be nontrivial to get most of that stuff to work. And the configuration stuff is worse. I don't think it's really going to do XEmacs a lot of good with people who actually like GTK and GNOME if the configuration and skinning stuff is not integrated with other apps based on that TK/DE combo. > > BTW, I do work with XEmacs displaying windows on workstations with > > very different displays *simultaneously* about once a week, maybe > > every other week. > > And both of us believe that this would probably work just fine with GTK > (2 and later). Well, no, I don't believe that. I believe recent GTK is capable of putting up windows on multiple displays, but I don't know about the user preference stuff (ie, xrdb). DPI it probably will get OK, and client-side rendering means that you'll have a consistent set of fonts available to the client (which is unfortunate when the client is Linux and the server is a Mac, but oh, well :-). Still, I'll believe that it works with a reasonably small number of gotchas when I see it. As Richard points out, there are a lot of senior developers at GNOME/GTK who clearly don't see "network transparency" as a goal. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Fix compile issues for C89 compilers. 13 years, 8 months

Stephen J. Turnbull

Jeff Sparkes writes: > Fix compile issues for C89 compilers. Use log() instead of log2(). GCC has a -C89 switch or something like that that either enforces or warns about C89 compatibility. Perhaps beta builds should use that switch? _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

5 participants
10 comments

xemacs-gtk now displaying unicode 13 years, 8 months

Jeff Sparkes

I have the internal char to utf-8 decoding function done, and now xemacs-gtk can use pango to display well rendered unicode characters. There are still some problems with descenders, see Khmer, but most other combining marks are displayed correctly. Some of them are showing up as extra spaces. I have a screenshot at http://i.imgur.com/PfcSP.png On the left is xemacs, on the right is gedit, which also uses pango. Some of the characters require a taller line, like Khmer. Down near the bottom you can see Shavian, which isn't on the BMP, which xemacs can't currently handle. Here's a second screenshot, which shows right to left languages. Anywhere there's a box with hexadecimal digits is character that's not in the default Monospace font under Gnome, DejaVu Sans Mono. I haven't dealt with alternate fonts yet. The file is one I saved from the gmane.emacs.devel list, which I've attached. Our etc/HELLO also displays well.

10 participants
29 comments

Re: Fix compile issues for C89 compilers. 13 years, 8 months

François Revol

>>>>>> Stephen J Turnbull <stephen(a)xemacs.org> writes: > > Stephen> GCC has a -C89 switch or something like that that either > Stephen> enforces or warns about C89 compatibility. Perhaps beta > Stephen> builds should use that switch? > > Which C89 compiler do we support? Btw... The BeOS port requires gcc 2.95 due to the C++ API... Haiku OTH can be built with gcc4 but then we loose binary compatibility that is the target for R1. François. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

2 participants
1 comments

Summary of XEmacs Issue Tracking System Issues 13 years, 8 months

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2011-04-12 - 2011-04-19) 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. 517 open ( +0) / 242 closed ( +0) / 759 total ( +0) Open issues with patches: 11 Average duration of open issues: 835 days. Median duration of open issues: 871 days. Open Issues Breakdown new 184 ( +0) deferred 6 ( +0) napping 4 ( +0) verified 52 ( +0) assigned 155 ( +0) committed 26 ( +0) documented 2 ( +0) done/needs work 24 ( +0) _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 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 April 2011