February 2001 - XEmacs-Beta - XEmacs Mailing List Archives

Latest Speedbar-0.13 doesn't show images 23 years, 1 month

Dr. Volker Zell

Hi Steve The latest imported speedbar package 0.13 doesn't show any images when requested. I think this is because the package system installs the xpm files under the etc directory but sb-image.el is searching for them in the load-path. Putting them under the lisp/speedbar directory fixes. Ciao Volker

2 participants
1 comments

Problem with Gnus using 21.2.4x 23 years, 1 month

Nevin Kapur

I've been using the beta XEmacs since Jan 25 (21.2.42). The following problem is repeatable for me: 1. Start gnuserv on an X XEmacs. 2. Start gnus. Quit it. 3. Start a tty gnuclient. 4 Start gnus and enter any group. The SPC key which runs `gnus-summary-next-page' does not work, i.e. it does not scroll the article as is supposed to. This problem does not exist in 21.1.12. I cannot test it on 21.1.13, 21.1.14 as tty gnuclients on these versions crash too often for me. (I've submitted a bug report.) I don't know how to debug this and the folks on the ding list suggested that I post this here. -- Nevin

1 participants
1 comments

Problems with mswindows-shell-execute 23 years, 1 month

Dr. Volker Zell

Hi I'm using o XEmacs 21.2 (beta41) "Polyhymnia" [Lucid] (i686-pc-cygwin, Mule) of Wed Jan 17 2001 on VZELL My cygwin mount table: Device Directory Type Flags D:\bin /usr/bin system binmode D:\lib /usr/lib system binmode C: /dev/c system binmode D: / system binmode Please take a look at the following lisp expressions: (mswindows-shell-execute nil "/tmp/inst_notes_ias102.html") This works (mswindows-shell-execute nil "/dev/c/tmp/FAQ.html") This works (mswindows-shell-execute nil "file///tmp//inst_notes_ias102.html") file not found: "file///tmp//inst_notes_ias102.html" (X) (mswindows-shell-execute nil "file//D:/tmp//inst_notes_ias102.html") file not found: "file//D:/tmp//inst_notes_ias102.html" (mswindows-shell-execute nil "file///D|/tmp//inst_notes_ias102.html") file not found: "file///D|/tmp//inst_notes_ias102.html" (mswindows-shell-execute nil "http://vzell/") file not found: "http://vzell/" Are the file:// and http:// type URL's supposed to work ? I'm asking because lots of lisp code uses code like the following. This is from jde: (browse-url (concat "file://" (jde-convert-cygwin-path jde-help)) In my case I try to use in browse-url, browse-url-default-windows-browser for it's browse-url-browser-function. So I end up with URL's of type (X), but this gives the error above. Any hints ? Ciao Volker

2 participants
1 comments

GTK: In or out? I need more non-Linux build reports!! 23 years, 1 month

Stephen J. Turnbull

Please do builds of the gtk-xemacs sources --with-gtk=no. Basically what I would like, as soon as possible, is lots of build reports based on a cvs checkout of gtk-xemacs-21-2 ./configure --with-gtk=no make beta >beta.err 2>&1 src/xemacs M-x build-report It is important to do the explicit --with-gtk=no, even though that's the default. The problem is there doesn't seem to be any other way to recognize gtk-xemacs-21-2 sources in a build report, except for the tester to put it in explicitly. --with-gtk=yes reports are of course useful, but they are irrelevant to whether GTK will be in the release since it will default to OFF. -BP> "Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: >> So the basic technical hurdle has been met. I would like to go >> through the build reports and see how many --with-gtk=no builds >> have actually been done, and for what platforms. There seem to be about 10 on Linux, one on OpenBSD, and no others. -BP> If anybody wants my insane makefile, let me know. Basic -BP> status right now is that for solaris, linux, and FreeBSD (and -BP> I did a few variant builds on cygwin the other day, but not -BP> my full suite), 48 different variants per platform get built -BP> at my house almost daily. -BP> gtk & x11 & tty, with/without union type, with/without MULE, -BP> pdump/unexec, and debug/release in all their variations build -BP> & run. If you could run your insane make and submit them all to xemacs-build-reports, it would be very useful. Then do it again with warnings cranked far past any sane level, just for kicks. (I doubt I would be able to interpret them, but it would be very useful in a post-mortem kind of analysis.) Doing the "submit the whole bunch" on a regular basis (say, every couple of weeks) seems like a good idea to me. -BP> If there is an r21-2-45 tag that I could use as the target of -BP> the 'cvs diff', that would make life much easier. There is as of a few hours ago. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."

6 participants
7 comments

W3 problems 23 years, 1 month

Norbert Koch

Hi! I've destroyed part of my installation. Whenever I try to run w3, I get the following bunch of warnings: Any pointers? TIA, norbert. (1) (style/warning) No stylesheets found! Check configuration! DANGER DANGER! Emacs-W3 checked for its stylesheet in the following places and did not find one. This means that some formatting will be wrong, and most colors and fonts will not be set up correctly. ------ /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/etc/w3/light.css /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/etc/w3/stylesheet-light /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/etc/w3/stylesheet /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/etc/w3/default.css /sw/i386_fbsd3/xemacs-21.2/lib/xemacs-21.2-b45/etc/light.css /sw/i386_fbsd3/xemacs-21.2/lib/xemacs-21.2-b45/etc/stylesheet-light /sw/i386_fbsd3/xemacs-21.2/lib/xemacs-21.2-b45/etc/stylesheet /sw/i386_fbsd3/xemacs-21.2/lib/xemacs-21.2-b45/etc/default.css /sw/i386_fbsd3/xemacs-21.2/lib/xemacs-21.2-b45/etc/w3/light.css /sw/i386_fbsd3/xemacs-21.2/lib/xemacs-21.2-b45/etc/w3/stylesheet-light /sw/i386_fbsd3/xemacs-21.2/lib/xemacs-21.2-b45/etc/w3/stylesheet /sw/i386_fbsd3/xemacs-21.2/lib/xemacs-21.2-b45/etc/w3/default.css /sw/i386_fbsd3/xemacs-21.2/lib/w3/light.css /sw/i386_fbsd3/xemacs-21.2/lib/w3/stylesheet-light /sw/i386_fbsd3/xemacs-21.2/lib/w3/stylesheet /sw/i386_fbsd3/xemacs-21.2/lib/w3/default.css /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/lisp/w3/light.css /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/lisp/w3/stylesheet-light /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/lisp/w3/stylesheet /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/lisp/w3/default.css /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/light.css /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/stylesheet-light /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/stylesheet /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/default.css /tmp/staging/w3/etc/w3/light.css /tmp/staging/w3/etc/w3/stylesheet-light /tmp/staging/w3/etc/w3/stylesheet /tmp/staging/w3/etc/w3/default.css /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/w3/light.css /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/w3/stylesheet-light /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/w3/stylesheet /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/w3/default.css /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/etc/light.css /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/etc/stylesheet-light /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/etc/stylesheet /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/etc/default.css /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/etc/w3/light.css /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/etc/w3/stylesheet-light /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/etc/w3/stylesheet /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/etc/w3/default.css /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/lisp/light.css /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/lisp/stylesheet-light /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/lisp/stylesheet /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/lisp/default.css /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/lisp/w3/light.css /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/lisp/w3/stylesheet-light /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/lisp/w3/stylesheet /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/lisp/w3/default.css /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/lisp/etc/light.css /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/lisp/etc/stylesheet-light /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/lisp/etc/stylesheet /sw/i386_fbsd3/xemacs-21.2/lib/xemacs/xemacs-packages/lisp/etc/default.css /usr/users/support/nk/.xemacs/w3/light.css /usr/users/support/nk/.xemacs/w3/stylesheet-light /usr/users/support/nk/.xemacs/w3/stylesheet /usr/users/support/nk/.xemacs/w3/default.css ------

1 participants
0 comments

Re: any reason that lisp/ui would no longer be in the dump-time load-path? 23 years, 1 month

Michael Sperber

>>>>> "BP" == William M Perry <wmperry(a)aventail.com> writes: BP> "Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: >> >>>>> "-BP" == William M Perry <wmperry(a)aventail.com> writes: >> -BP> I don't have time to dig into this deeply today, but I did a -BP> synch up to r21-2-45 in my local workspace for XEmacs/GTK and -BP> when it goes to dump, it cannot (require 'gtk-ffi), but that -BP> file is in lisp/ui/gtk-ffi.elc* >> -BP> Martin, could any of the changes you made to the make process -BP> recently be causing this? >> >> Michael Sperber made some adjustments, and I think (I'd have to dig up >> the thread and patch) except for lisp/mule and lisp/term, which are >> special-cased, the code doesn't search subdirectories of lisp. This is >> something we've been aiming for about a while; it reduces startup time >> noticably to get rid of the stats (especially on MS systems). Yes. Well, almost: lisp/mule is special-cased, files in lisp/term are loaded via an explicit prefix. >> Why do you need a subdirectory there? BP> I don't really, there were just 50 or so files in there at one point, but I BP> combined a lot of them before the final release, and it is now down to 13, BP> so it is probably ok to move them up a level. I think so, too, at least for now. For post-21.2, I'd like to move to a structure like this: lisp/xemacs lisp/mule lisp/gtk ... which avoids the problems (conceptual and technical) we've been having. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

any reason that lisp/ui would no longer be in the dump-time load-path? 23 years, 1 month

William M. Perry

I don't have time to dig into this deeply today, but I did a synch up to r21-2-45 in my local workspace for XEmacs/GTK and when it goes to dump, it cannot (require 'gtk-ffi), but that file is in lisp/ui/gtk-ffi.elc* Martin, could any of the changes you made to the make process recently be causing this? Sorry I don't have time to debug this, just bought a playstation 2 for liam's birthday, and I've got to figure out what accessories I (errr, he) needs before I wrap it all up. :) -Bill P.

2 participants
2 comments

Re: Problem XEmacs 21.1.9 23 years, 1 month

Martin Buchholz

>>>>> "A" == Alex Brito <abrito(a)tvirtual.com.mx> writes: A> Hi, A> I'm trying to install xEmacs 21.1.9 on Solaris 2.6 and I had the next A> error while running 'make' A> Does anybody can help me with this issue? This has always worked. (martin＠mule) ~ $ syshgrep RTLD_MEMORY /usr/include/dlfcn.h:112:#define RTLD_MEMORY 0x01000 /* use memory sections */ (martin＠mule) ~ $ uname -a SunOS mule.m17n.org 5.6 Generic_105181-11 sun4u sparc SUNW,Ultra-60 Something must be wrong with your header files. Probably your gcc is built for the wrong version of the os. Build a new gcc and all should be well (this is only a guess, of course).

1 participants
0 comments

Re: syntax-table / autoload issues 23 years, 1 month

Jan Vroonhof

Matt Tucker <tuck(a)whistlingfish.net> writes: > diff -u -r1.10.2.7 lisp-mode.el > --- lisp-mode.el 2000/11/23 06:27:36 1.10.2.7 > +++ lisp-mode.el 2001/02/17 09:45:14 > ＠＠ -170,19 +170,11 ＠＠ > (if (not lisp-mode-syntax-table) > (progn (setq lisp-mode-syntax-table > (copy-syntax-table emacs-lisp-mode-syntax-table)) > - (modify-syntax-entry ?\| "\" " lisp-mode-syntax-table) > (modify-syntax-entry ?\[ "_ " lisp-mode-syntax-table) > ;; XEmacs changes > (modify-syntax-entry ?\] "_ " lisp-mode-syntax-table) > - ;; > - ;; If emacs was compiled with NEW_SYNTAX, then do > - ;; CL's #| |# block comments. > - (if (= 8 (length (parse-partial-sexp (point) (point)))) > - (progn > - (modify-syntax-entry ?# "' 58" > lisp-mode-syntax-table) > - (modify-syntax-entry ?| ". 67" > lisp-mode-syntax-table)) > - ;; else, old style > - (modify-syntax-entry ?\| "\" " lisp-mode-syntax-table)))) > + (modify-syntax-entry ?# "' 58" lisp-mode-syntax-table) > + (modify-syntax-entry ?| "\" 67" lisp-mode-syntax-table))) > > (define-abbrev-table 'lisp-mode-abbrev-table ()) Removing this cruft seems like a very good idea. > This fixes both autoload.el and lisp-mode-syntax-table properly. Any > objections? Looks fine. Jan

2 participants
1 comments

Re: The colors are back (was: XEmacs' desktop icon greyed out) 23 years, 1 month

Markus Alt

Markus Alt wrote: > [snip] > So, sorry again; I thought I had to set this right, although it's > something I'm very proud of ... :-/ Sh*#＠, I mean it's something I'm *NOT* very proud of, of course! Markus

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 February 2001