November 2012 - XEmacs-Beta - XEmacs Mailing List Archives

Re: XEmacs-Beta Digest, Vol 74, Issue 10 12 years

steven Mitchell

Stephen Turnbull writes: Maybe most people wouldn't notice. I suppose we could try enabling Mule, and see if anybody screams in pain. Unfortunately, Xft requires a lot of work before that's a reasonable thing to do IMO, because I see no good reason to expect that bug reports will be addressed in a timely fashion (except for an automatic "patches welcome" from me ). Steve I assume you are saying make --with-mule the default for the ./configure line. Either way is fine, just so I can still specify --with-mule=no to disable it. I don't know, I maybe the last guy on earth who doesn't use it, but I would still like to disable it. Steve Mitchell _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Re: XEmacs-Beta Digest, Vol 74, Issue 10 12 years

Stephen J. Turnbull

steven Mitchell writes: > I assume you are saying make --with-mule the default for the > ./configure line. Either way is fine, just so I can still specify > --with-mule=no to disable it. Yes. Backward compatibility and user choice is important to us (unlike that other Emacs, which apparently is in the process of partially obsoleting `lambda' -- I am not kidding). As a matter of personal advice, I think you're probably being short-sighted though -- all the actual issues with Mule have to do with internationalized text. I've never had a problem with all-ISO-8859 files. Yes you could run into performance issues in extreme cases like large VM mailboxes. Nevertheless, the choice is yours, and that's the way it should be. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

21.5 unsupported unicode code point 956 12 years

Vin Shelton

Aidan et al - I'm seeing the following error when running "make check": Testing Interpreted Lisp Unexpected error (syntax-error "Unsupported Unicode code point" 956) while reading forms from buffer backtrace(nil t) # bind (print-escape-newlines print-length error-info error-info context-msg error-info) #<compiled-function (from "/opt/src/xemacs-21.5-min/lisp/test-harness.elc") (error-info) "...(64)" [test-harness-unexpected-error-enter-debugger noninteractive test-harness-bug-expected unexpected-test-file-failures context-msg error-info end-of-file "reading forms from buffer" princ format "Unexpected error %S while %s\n" message "Unexpected error %S while %s." error t 50 backtrace nil debugger test-harness-unexpected-error-show-backtrace print-length print-escape-newlines] 5 0xbea>((syntax-error "Unsupported Unicode code point" 956)) read(#<buffer " *Test Input*">) #<compiled-function (from "/opt/src/xemacs-21.5-min/lisp/test-harness.elc") nil "...(8)" [buffer body read] 2 0xbeb>() # (unwind-protect ...) call-with-condition-handler(#<compiled-function (from "/opt/src/xemacs-21.5-min/lisp/test-harness.elc") (error-info) "...(64)" [test-harness-unexpected-error-enter-debugger noninteractive test-harness-bug-expected unexpected-test-file-failures context-msg error-info end-of-file "reading forms from buffer" princ format "Unexpected error %S while %s\n" message "Unexpected error %S while %s." error t 50 backtrace nil debugger test-harness-unexpected-error-show-backtrace print-length print-escape-newlines] 5 0xbea> #<compiled-function (from "/opt/src/xemacs-21.5-min/lisp/test-harness.elc") nil "...(8)" [buffer body read] 2 0xbeb>) # (condition-case ... . ((error))) # bind (body buffer) test-harness-read-from-buffer(#<buffer " *Test Input*">) #<compiled-function (from "/opt/src/xemacs-21.5-min/lisp/test-harness.elc") nil "...(5)" [inbuffer test-harness-read-from-buffer] 2 0xbfc>() # (unwind-protect ...) call-with-condition-handler(#<compiled-function (from "/opt/src/xemacs-21.5-min/lisp/test-harness.elc") (error-info) "...(57)" [test-harness-unexpected-error-enter-debugger noninteractive test-harness-bug-expected unexpected-test-file-failures context-msg error-info "executing interpreted code" princ format "Unexpected error %S while %s\n" message "Unexpected error %S while %s." error t 50 backtrace nil debugger test-harness-unexpected-error-show-backtrace print-length print-escape-newlines] 5 0xbfb> #<compiled-function (from "/opt/src/xemacs-21.5-min/lisp/test-harness.elc") nil "...(5)" [inbuffer test-harness-read-from-buffer] 2 0xbfc>) # (condition-case ... . ((error (message "Test suite execution aborted.")))) # bind (standard-output skipped-test-reasons passes assertion-failures no-error-failures wrong-error-failures missing-message-failures other-failures unexpected-test-file-failures debug-on-error trick-optimizer filename inbuffer) test-harness-from-buffer(#<buffer " *Test Input*"> "/opt/src/xemacs-21.5-min/tests/automated/case-tests.el") # bind (test-harness-current-file input-buffer filename) test-emacs-test-file("/opt/src/xemacs-21.5-min/tests/automated/case-tests.el") byte-code("..." [file test-emacs-test-file t] 2) # (condition-case ... . ((error (byte-code "<C2><C3>!<88><C2> !<88><C2><C4>!<88><C5>^H<C6>\"<88> <C7> <88>Ƈ" [error-info file princ ">>Error occurred processing " ": " display-error nil terpri] 3)))) # bind (file) batch-test-emacs-1("/opt/src/xemacs-21.5-min/tests/automated/case-tests.el") # bind (#:G63506 file-in-dir #:G63505 file error) batch-test-emacs() # bind (arg) command-line-do-funcall("-f") # bind (dir file-count line end-of-options file-p arg tem) command-line-1() # bind (command-line-args-left) command-line() # bind (error-data) normal-top-level() # (condition-case ... . error) # (catch top-level ...) This is on my fedora 17 x86_64 system. What does this mean? Thanks, Vin _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

2 participants
1 comments

XFT fonts [was: build failure on Ubuntu 12.04.1] 12 years

Charles Waldman

> Everything is just that one font, which I think is DejaVu Sans Mono. Actually, it's (face-font-name 'default) "Monospace-12" which isn't even one of the fonts listed in the options menu! _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

2 participants
1 comments

XFT fonts [was: build failure on Ubuntu 12.04.1] 12 years

Charles Waldman

Raymond Toy writes: > This is what I see on my personal build on Ubuntu as well. Well, I guess I'm glad to know that it's not just me! > The screen shot looks pretty nice so it seems as if xft fonts are being used. I think it looks pretty nice too. But, I can't change the fonts: tried using -font, the Options menu, and Customize. Everything is just that one font, which I think is DejaVu Sans Mono. It's like the old Ford Model-T: you could get it in any color you want, as long as you want black! - Charles _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

3 participants
2 comments

build failure on Ubuntu 12.04.1 12 years

Charles Waldman

Building XEmacs from hg sources on a brand-new Ubuntu box, fails with termcap.c:236:1: error: unknown type name 'speed_t' Looks like this type is defined in /usr/include/termios.h but that header isn't getting pulled in. The configure test is finding this header file and reporting: configure:18681: checking for termios.h ac_cv_header_termios_h=yes Full config and make output attached, if anyone wants that level of detail. The problem is solved by the following trivial patch: diff -r 7b5f88e5b456 src/termcap.c --- a/src/termcap.c Mon Oct 15 20:47:00 2012 +0200 +++ b/src/termcap.c Thu Nov 01 10:49:51 2012 -0500 ＠＠ -26,6 +26,7 ＠＠ #include "device.h" #include "device-impl.h" /* For DEVICE_BAUD_RATE */ #include "sysfile.h" +#include "systty.h" #include "process.h" #else /* not emacs */ _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

6 participants
14 comments

build failure on Ubuntu 12.04.1 12 years

Charles Waldman

Vin Shelton writes: > You don't have the default font; see the warning message. > Try either installing the default helvetica font or specifying a font with the -fn option. I don't think the problem is that trivial (but I would be glad to be wrong!) I've got a whole bunch of fonts installed, including Helvetica. I get the same flavor of warning message no matter what I pass in for -font (including leaving the argument off) GNU Emacs (which I did not build from source) has no problem accessing fonts, eg: $ emacs -q -font Mono-8 works, but $ ./src/xemacs -font Mono-8 prints: Warning: Cannot convert string "Mono-8" to type FontStruct and gives me a corrupted display. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

3 participants
2 comments

build failure on Ubuntu 12.04.1 12 years

Charles Waldman

Thanks for the "apt-get build-deps xemacs21" suggestion - that pulled in a few packages and now at least the tty console works. However it's still not usable, instead of seeing character glyphs I just have red rectangles. Here's a screenshot of what the scratch buffer looks like after I've typed a few characters: http://cgw.placeholderdomains.net/xemacs-ubuntu.png _______________________________________________ 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 12 years

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2012-10-30 - 2012-11-06) 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. 553 open ( +1) / 290 closed ( +0) / 843 total ( +1) Open issues with patches: 13 Average duration of open issues: 1274 days. Median duration of open issues: 1350 days. Open Issues Breakdown new 226 ( +1) deferred 6 ( +0) napping 3 ( +0) verified 56 ( +0) assigned 153 ( +0) committed 19 ( +0) documented 3 ( +0) done/needs work 18 ( +0) Issues Created Or Reopened (1) ______________________________ Termcap support is broken 2012-11-01 http://tracker.xemacs.org/XEmacs/its/issue845 created matsl Issues Now Closed (1) _____________________ configure in modules/ldap is not used 54 days http://tracker.xemacs.org/XEmacs/its/issue843 matsl _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Fwd: Re: install instructions 12 years

steven Mitchell

Stephen, I would be sad if you did remove that page. I was not trying to be critical of XEmacs, or the fellows who maintain it. I was just trying to show the extent of the problem, or what I am thinking is the problem (I could be wrong). I have trouble following these directions and I think that other new people might too. And I think that some people who are expert lisp coders and have been doing this for so long are so far removed from being a beginner, that they can not clearly see what trips a beginner up, because they *know* the answers to some of my questions instinctively. (and yeah, I'm still a rank beginner compared to others here). I spent three hours writing that post because I want things to be better, and I am willing to be part of the solution--I'm willing to re-write that page, but cannot do it alone because I don't *know* enough yet. Even if I got some help, ie someone who, once I rewrite it, can correct it and pass it back, I would still have to figure out how to upload it to the website which is on mercurial if I recall correctly. The website seems so interconnected with the links on each page pointing to other pages that I would be afraid of getting all the links hooked back up and working again after replacing a page. Maybe that would work itself out someway. There are so few developers on XEmacs, that I cannot complain that the website needs their attention, instead of the coding they do. I'm willing to help. There are a lot of things wrong with the website that a person does not need to know XEmacs architecture to fix. On the "http://www.xemacs.org/Download/win32 /index.html#InnoSetup-Beta-Download" page, about 1/4 of the links are no longer working. They need explored to see if the page has moved or if it is not there at all at this time. I can explore things like that and report what needs changed. But I would not like to report such things if it meant there was a chance the page would be taken down. Would you consider, instead of deleting the page, putting a statement at the top of it, something like: "The definitive install instructions for each version of XEmacs is the INSTALL file in the top directory of the source code for that version. What follows is general directions written some time ago that may need updated when there is time and people to do so." Steve Mitchell On 11/03/2012 01:02 PM, Stephen J. Turnbull wrote: > steven Mitchell writes: > > > Feedback from > > /Install/index.html > > The definitive instructions are in the file INSTALL in the top > directory of the sources. I think for now I'm just going to remove > this page, or make it point to the INSTALL file. > > > > _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

4 participants
4 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 November 2012