February 1999 - XEmacs-Beta - XEmacs Mailing List Archives

help with bit stealing from address 25 years, 1 month

Michael Kifer

Could somebody point me to the part of code where XEmacs decides, depending on the OS, which bits can be stolen from address space to tagging? thanks much --michael

1 participants
0 comments

Re: More on tar problems 25 years, 1 month

Adrian Aichner

>>>>> "John" == John Whitley <whitley(a)cse.Buffalo.EDU> writes: Hi John, I can contribute some more problems :-) The test-case I'm using is this: ftp://ftp.gnus.org/pub/gnus/pgnus-0.69.tar.gz The XEmacs I'm using is (emacs-version) "XEmacs 21.0 \"Pyrenean63\" [Lucid] (i386-pc-win32) of Sat Feb 06 1999 on ZJ75T" running on WinNT4sp3. After downloading the file with Netscape Navigator 4.08 (making sure WinNT doesn't save the file as pgnus-0.69_tar.gz but rather as pgnus-0.69.tar.gz) I see these problems: Hitting e runs the command dired-find-file on the file leads this (M-x show-message-log): parsing tar file... parsing tar file...0% parsing tar file...0% +¼Ó\u2Ím×21#Ñd!¥Ä(>³$lào"¸\2vtB¬!ÙºfÓLÎÊR³_âl·×°óÉ$3LÖv¾±Àd 1aÞb¾ý:?èZ3¯ÞD has size -740605235 - corrupted. After uncompressing the file with Z runs the command dired-do-compress I can open pgnus-0.69.tar just fine with e runs the command dired-find-file and see all the files in the tar. However, when I first saved as pgnus-0.69_tar.gz, uncompressed to pgnus-0.69_tar extended auto-mode-alist's tar regexp from "\\.\$tar\\|tgz\\|tar\\.gz\$\\'" to "\\.\$tar\\|tgz\\|tar\\.gz\$\\'\\|_tar$" I could only see the first two tar entries when I opened pgnus-0.69_tar: drwxrwxr-x larsi/larsi 0 Jan 03 14:37 pgnus-0.69/ -rw-rw-r-- larsi/larsi 2063 Nov 19 1998 pgnus-0.69/make.bat There where no errors. Regards, Adrian John> In reviewing the few recent notes on tar-mode problems, I John> thought that I'd try a few experiments and post the results. John> I'm using XEmacs 21.0-b63 on an SGI O2 running IRIX 6.5 John> under X11R6.3, having built using SGI's cc. John> Regardless of whether '-vanilla' is used or not, or whether John> I specifically (require 'crypt) and (require 'tar-mode) the John> following sequence of events occurs: John> 1) parsing tar file ... (gets through a few percent) John> 2) File mode specification error: (error "<long binary garbage> John> OR John> <binary garbage> John> I'm prepared to dig a deeper into this, but can't make any John> guarantees as to when I'll get to it. Any suggestions in John> the meantime would be appreciated. As a start, I'll John> probably step through some of the following alternative John> build choices in a grey-code ordering: John> 1) optimizations on/off (this build: on) John> 2) --gung-ho on/off (this build: on) John> 3) gcc instead of cc (this build: SGI cc) John> More information as it becomes available. John> (FWIW, I'm using the Feb 2 xemacs-sumo packages John> distribution.) John> -- John -- Adrian Aichner Teradyne GmbH, European Design Center Integra Test Division Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

1 participants
0 comments

Re: [gnu.emacs.sources] Re: emacs and templates 25 years, 1 month

Karl M. Hegbloom

>>>>> "SL" == SL Baur <steve(a)xemacs.org> writes: SL> Is this a rewrite of autoinsert.el (which is currently synched SL> with Emacs 19.34), or an update? I don't know, Steve. I was reading Usenet and forwarded it... <actually looking...> Hmmm. Both are based on one by Charlie Martin... This one comes with a set of templates yous might like to have. Perhaps if there's time, someone could grab a copy and have a look at it. I've got tons to do and read; I'll put it in my todo list, but don't expect me to get after it for a while; it's necessarily of lower priority than other projects right now. XEmacs is looking great, and feels much faster!!

1 participants
0 comments

More on tar problems 25 years, 1 month

John Whitley

In reviewing the few recent notes on tar-mode problems, I thought that I'd try a few experiments and post the results. I'm using XEmacs 21.0-b63 on an SGI O2 running IRIX 6.5 under X11R6.3, having built using SGI's cc. Regardless of whether '-vanilla' is used or not, or whether I specifically (require 'crypt) and (require 'tar-mode) the following sequence of events occurs: 1) parsing tar file ... (gets through a few percent) 2) File mode specification error: (error "<long binary garbage> OR <binary garbage> I'm prepared to dig a deeper into this, but can't make any guarantees as to when I'll get to it. Any suggestions in the meantime would be appreciated. As a start, I'll probably step through some of the following alternative build choices in a grey-code ordering: 1) optimizations on/off (this build: on) 2) --gung-ho on/off (this build: on) 3) gcc instead of cc (this build: SGI cc) More information as it becomes available. (FWIW, I'm using the Feb 2 xemacs-sumo packages distribution.) -- John

1 participants
0 comments

Successful XEmacs 21.0-b63 build on IRIX 6.5 25 years, 1 month

John Whitley

XEmacs 21.0-b63 was successfully built on: SGI O2 R5k workstation running IRIX 6.5 SGI X11R6.3 server libraries as listed in the Installation file, included below (tried compiling with neXtaw 0.5.1, but was strangely ugly...?) otherwise compiled out of the box using SGI's cc compiler (optimization and debugging flags turned on as below) I've been using it daily for about a week, including Calc, Calendar, Tuareg mode (mode for Objective Caml/Objective Labl programming languages) among other things. Only major problem is that tar-mode is wholly and utterly broken for all tar files (all known good tars), as previously cited by another report. -- John the 'Installation' file from the build follows: -- cut here ---------------------------------------- uname -a: IRIX gaia 6.5 05190004 IP32 ./configure '--without-gcc' '--with-gnu-make' '--cflags=-O2 -OPT:Olimit=0 -g3 -I/usr/local/include' '--site-runtime-libraries=/usr/local/lib32:/usr/lib32:/lib32' '-ldflags=-woff 84,85 -L/usr/local/lib32' '--dynamic=yes' '--gung-ho' XEmacs 21.0-b63 "Pyrenean63" configured for `mips-sgi-irix6.5'. Where should the build process find the source code? /src/text/xemacs-21.0.63 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/irix6-0.h' and `m/iris4d.h' What compiler should XEmacs be built with? cc -O2 -OPT:Olimit=0 -g3 -I/usr/local/include Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? Where do we find X Windows libraries? Runtime library search path: /usr/local/lib32:/usr/lib32:/lib32 Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in support for TIFF image handling. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for DBM. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support.

1 participants
0 comments

Re: [gnu.emacs.sources] Re: emacs and templates 25 years, 1 month

SL Baur

Is this a rewrite of autoinsert.el (which is currently synched with Emacs 19.34), or an update? Karl M Hegbloom <karl(a)cathcart.sysc.pdx.edu> writes in xemacs-beta(a)xemacs.org: > Thought this might be of interest. ... ville> ;; LCD Archive Entry: ville> ;; auto-insert-tkld|Kevin Davidson|tkld(a)cogsci.ed.ac.uk| ville> ;; An automatic file template package with keyword expansion for Emacs.| ville> ;; $Date: 1994/12/02 17:42:59 $|$Revision: 1.23 $|~/packages/auto-insert.tar.Z| > Available from here: > http://www.geocities.com/SiliconValley/Foothills/9093/files/auto-insert-t... > When I get time[1] I'll tidy up those web pages...

1 participants
0 comments

[gnu.emacs.sources] Re: emacs and templates 25 years, 1 month

Karl M. Hegbloom

Thought this might be of interest.

1 participants
0 comments

Xemacs - Mule and VM 25 years, 1 month

Andrew S. Howell

Hello, I have been trying out VM with Xemacs 21.63b, and am having a couple problems. First, I get garbage when I try to look at a particular Japanese message. The headers say its: Content-Type: text/plain;charset="iso-2022-jp" Content-Transfer-Encoding: 7bit The same message is viewable in with Mew version 1.93 on Emacs 20.2 / Mule 3.0 (MOMIJINOGA). Actually, I forwarded to mail to a test account, so it is not exactly the same mail. Forwarding it mew does work though. jcode on the message says: Detected input code: New-JIS I'm don't trust jcode though, in that for another message, which displays fine, it says: Detected input code: ASCII (no Japanese) If I save the message to a file and read it back in, it displays just fine. So, my guess is that I need to tell vm how to work out the encoding/font. The second problem I'm having is that I can not display japanese mail with xemacs in a kterm. I just get the option to display it with an external viewer, or save it. Thanks, Andy

1 participants
0 comments

Re: pcl-cvs won't start 25 years, 1 month

Jan Vroonhof

Marco-misarc.BRAMBILLA(a)st.com writes: > I have Xemacs 20.4, not 21.x > > I installed the package > > pcl-cvs-1-38-2-pkg.tar.gz The packages are for 21.x and up only. > Is this behaviour because ofmy Xemacs being 20 instead than 21 ? Yes. > Is it sure using the old cookie.el, until Xemacs 21 is released ? It is better to recompile all the .el files using XEmacs 20. Jan

1 participants
0 comments

pcl-cvs won't start 25 years, 1 month

Marco-misarc.BRAMBILLA＠st.com

Dear Sirs, I have Xemacs 20.4, not 21.x I installed the package pcl-cvs-1-38-2-pkg.tar.gz If I install it over the old (I think 1.5) pcl-cvs it works OK, because it finds the cookie.el that was provided with that version od pcl-cvs. If I delete cookie.el, leaving only the files of the new distribution (and of course install Elib - elib-1.04-pkg.tar.gz), it will stop working. The message, when trying to launch update-directory, will be: "#": wrong file mode. Is this behaviour because ofmy Xemacs being 20 instead than 21 ? Is it sure using the old cookie.el, until Xemacs 21 is released ? Thank you for any help. Marco Brambilla

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 1999