June 1999 - XEmacs-Beta - XEmacs Mailing List Archives

anyone to post NT binaries for 21.1.2 ??? 25 years, 6 months

Guido Van Hoecke

Hi, I read that 21.1.2 is now the official version. I am still using the version 'XEmacs 21.0 "20 minutes to Nikko" [Lucid] (i386-pc-win32) of Fri Mar 26 1999 on BLACKBIRD' that was posted before. Please, is any one willing / capable of providing an installable 21.1.2 for NT4? It doesn't help much to have the best of all editors, if it is just not available for the platform being used... TIA, Guido.

1 participants
0 comments

restarting my wm pops up Emacs.xemacs.xemacs window 25 years, 6 months

Giacomo Boffi

i'm using 21.2 "Dionysos" and gwm-1.8c (btw, are there any gwm'ers?) whenever i restart gwm while XEmacs is running, an emacs window is popped, as large as the whole screen, the info that gwm gives back says Window: Emacs.xemacs.xemacs＠boffi95 the window accepts no events, and if i kill it, XEmacs dies the above is probably a gwm's problem, but i ask because i'd like to know what changed with respect to 20.4 regarding this area, so that i can be somehow informative when reporting to gwm's mailing list tia gb

1 participants
0 comments

Re: 21.2 font menu for mswindows 25 years, 6 months

Mike McEwan

Andy Piper <andy(a)xemacs.org> writes: > As always I have split out the generic parts. This also includes the > expand-file-name usage changes suggested by Hrvoje. > I will apply this to cvs. > > andy > You missed one :-). --- x-font-menu.el~ Mon May 31 03:16:50 1999 +++ x-font-menu.el Tue Jun 1 19:16:51 1999 ＠＠ -237,7 +237,7 ＠＠ (make-font-instance (concat "-*-" family "-" weight "-" slant "-*-*-*-" size "-" resolution "-*-*-" - font-menu-registry-encoding) + x-font-menu-registry-encoding) nil t)) (throw 'got-font font)))))))) -- Mike.

2 participants
1 comments

Re: [Markus Kuhn <Markus.Kuhn@cl.cam.ac.uk>] UTF-8 support in xemacs 25 years, 6 months

Jan Vroonhof

Didier Verna <didier(a)xemacs.org> writes: > Markus, some other people on the list will probably give you a more > precise answer, so I'm forwarding this to them. Forwarding it to xemacs-mule would probably have been more appropriate. I don't know what you already told Markus, so I give him an imprecise answer anyway. Hi Markus, > I have recently extended the X11 "fixed" font to a repertoire > of over 2800 ISO 10646-1 characters, which is now available from > > http://www.cl.cam.ac.uk/~mgk25/ucs-fonts.html OK Nice. > have already added it. More information about using Unicode > and the ASCII compatible UTF-8 encoding are on the above > web page, and it would be really nice if xemacs would one day > decide to join the ISO 10646-1 club. Well 21.2.x (the development series) contains support (in theory) of UTF8, (maybe UTF7), UCS16 and full ISO 10646-1, both on input, displaz and output. In theory it should be complete (it is just another coding system as far as Emacs is concerned). For me it works on simple stuff (I can read in an UTF8 encoded file and have it display correctly even using non unicoded fonts). There still are some problems with it 1. It needs to load some huge conversions tables and that is a torture test for the lisp loading code in itself. 2. AFAIK it is untested for real work. This is mostly because there is an extreme scarcity of real world unicode/UTF8 encode files. I also am not sure the display side has been tested, something for you? Jan

1 participants
0 comments

Re: pgp key for the package list 25 years, 6 months

Jan Vroonhof

Earl Stutes <estutes(a)eas.san-jose.ca.us> writes: > pgpv package-index-1999-05-27.sig > Opening file "package-index-1999-05-27" type text. > unknown hash: unable to verify signature This is bad. Aren't PGP5 and gpg supposed to be compatible. Jan

1 participants
0 comments

[Markus Kuhn <Markus.Kuhn@cl.cam.ac.uk>] UTF-8 support in xemacs 25 years, 6 months

Didier Verna

Markus, some other people on the list will probably give you a more precise answer, so I'm forwarding this to them. -- Didier Verna <didier(a)xemacs.org> Please visit the XEmacs homepage at http://www.xemacs.org !

1 participants
0 comments

The backspace key deletes forward in cc-mode in 21.2, grrr 25 years, 6 months

SL Baur

1 participants
0 comments

Re: Build failure for CVS 21.2 of 19990531 (with mule) 25 years, 6 months

Daniel Pittman

Regarding Re: Build failure for CVS 21.2 of 19990531 (with mule); "Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: >>>>>> "sb" == SL Baur <steve(a)xemacs.org> writes: sb> Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes in sb> xemacs-beta(a)xemacs.org: >> You moved mule-misc.el to <core>/lisp/mule/ from >> <packages>/lisp/mule-base/. sb> That was some time ago. > Good point. Thing is, it's true I didn't keep up with recent changes, > and I didn't use correct procedure in updating packages. The first is > no sin, and the second is still all too easy a mistake to make---eg, > people who use the SUMO tarbabies. Ouch. The problem that bit me was, after all, the presence of mule-misc.el in mu /usr/.../mule-packages path. Having removed the offending mule-base package and added the latest wersion by hand, things are once more on an even keel. Thanks for the help. It's very much apreciated by those of us with insufficient time to understand the underneath of this wonderful package... Daniel

1 participants
0 comments

Re: Build failure for CVS 21.2 of 19990531 (with mule) 25 years, 6 months

SL Baur

Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes in xemacs-beta(a)xemacs.org: >>>>>> "sb" == SL Baur <steve(a)xemacs.org> writes: >>> Attached is a log of the failed build. >>> ... Loading cyrillic.el...*** Error in XEmacs initialization >>> (void-function split-char-or-char-int) sb> This function is defined in mule-misc.el, which got loaded. I sb> cannot duplicate this specific failure. > OK, I'll own up. This happened to me, too. > You moved mule-misc.el to <core>/lisp/mule/ from > <packages>/lisp/mule-base/. That was some time ago. > I update packages by untarring them (I've done something stupid and > package-ui doesn't work well for me, it's my fault though, not > pui's); this doesn't remove the old ones. $ rm -f `cat pkginfo/MANIFEST.mule-base` $ tar zxf /path/to/mule-base-X.YY-pkg.tar.gz > So I got hosed. I really didn't want to admit that :-) :-) -- I protest the NATO war in Yugoslavia.

2 participants
1 comments

Re: Build failure for CVS 21.2 of 19990531 (with mule) 25 years, 6 months

SL Baur

NB: The mailing lists look completely hosed as of 07:27 UT 31-May so I have no idea what has gone into the 21.2 in the last 12 hours. Daniel Pittman <daniel(a)danann.net> writes in xemacs-beta(a)xemacs.org: > --=-=-= > Hi. > Trying to build the latest XEmacs 21.2 from CVS fails for me when > --with-mule is used. The same configure sans mule works fine. > Suggestions? > Daniel > System details: > * Debian unstable > * i586 architecture > * kernel 2.2.6 > * glibc 2.1.1 final > * egcs 2.91.66 (1.1.2) > * X11R6, by XFree86 3.3.3.1 > Attached is a log of the failed build. > ... > Loading cyrillic.el...*** Error in XEmacs initialization > (void-function split-char-or-char-int) This function is defined in mule-misc.el, which got loaded. I cannot duplicate this specific failure. There is a strange bug in cyrillic.el-21.2 that manifests itself by failing to bytecompile (max lisp eval depth exceeded) the very first time .elcs are built. On a subsequent pass, cyrillic.elc gets built. I have no idea whether or not this is related to my other problems. At the moment I don't have a clean build of XEmacs, either 21.1 or 21.2, on *any* platform. -- I protest the NATO war in Yugoslavia.

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 June 1999