June 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: XEmacs is not 64-bit clean (was Re: Build failure, xemacs-21.1.2 on rh6-based linux-alpha-unknown) 24 years, 11 months

SL Baur

Greg Badros <gjb(a)cs.washington.edu> writes in xemacs-beta(a)xemacs.org: > SL Baur <steve(a)xemacs.org> writes: ... >> XEmacs is *not* 64 bit clean. On DEC OSF, temacs and dumped xemacs are >> semi-functional, but some internals are broken, definitely including >> the character sets/character category tables. > Do you have any interest in trying to make XEmacs 64bit clean? Yes. It will have to be done eventually. The same way we have to fix the y2038 bug sometime.[1] > I will gladly give you an account on my Alpha box here at the UW if > you're interested in getting XEmacs to work better with GNU/Linux-Alpha. Thanks for the offer, but I will have to decline for the time being. Footnotes: [1] Speaking of which, is it a standard POSIX feature that negative times get treated as being before the epoch? $ cat /usr/tmp/bug.c main() { long int time = 0x7fffffff; long int time2 = 0x80000000; printf("Death at %s", ctime(&time)); printf("Afterlife at %s", ctime(&time2)); } $ /usr/tmp/bug Death at Tue Jan 19 12:14:07 2038 Afterlife at Sat Dec 14 05:45:52 1901 -- 雨が降っています。

1 participants
0 comments

Re: This is the future 24 years, 11 months

SL Baur

Kazuyuki IENAGA <ienaga(a)jsys.co.jp> writes in xemacs-beta(a)xemacs.org: ... > BTW, Steve, >> -- >> 窓番号を入力してください > What this mean? It's the recorded message that comes out of the key machine in the ETL building -- mado bangou o nyuuryokushite kudasai. I believe it means "Though you may listen to this message a thousand times, you will never, ever hear all the sounds." -- 雨が降っています。

1 participants
0 comments

Re: Build failure, xemacs-21.1.2 on rh6-based linux-alpha-unknown 24 years, 11 months

Jan Vroonhof

Valdis.Kletnieks(a)vt.edu writes: > alias=<option> > Specifies the aliasing assertion to be applied to > your compilation unit. > The available options are: > typ Pointers to different types are never aliased. > allp Pointers are never aliased. > addr Variables are disjoint from pointers > unless their address is taken. > ansi Pointers can only point to an object of the > same type. Require -O option. What is the default? No special aliasing assumptions? What does the configure script use? It seems from below that by default it does not use the aliasing stuff so the "it works on other compilers argument" does not apply. > For what it's worth, I did light testing of a 21.2 built with "-O3 > -qansialias" The only "problem" with is that maybe the new gung-ho typing stuff makes it less sensible to this kind of problem. Jan -- Jan Vroonhof http://www.math.ethz.ch/~vroonhof/ Mathematik, vroonhof ＠ math.ethz.ch HG E16, ETH-Zentrum, Tel: +41-1-6325456/25154 Raemistrasse 101, CH-8092 Zuerich. Fax: +41-1-6321085

2 participants
1 comments

Re: prog-modes package and perl mode 24 years, 11 months

Jan Vroonhof

Noah Romer <noah.romer(a)lsil.com> writes: > It says "Library is file > /home/nromer/local/lib/xemacs-21.1-p2/lisp/prog-modes/cperl-mode.elc", which is So it does find it. Are there any warnings at startup? Can you call M-x cperl-mode RET manually? Jan

1 participants
0 comments

Re: prog-modes package and perl mode 24 years, 11 months

Jan Vroonhof

Noah Romer <noah.romer(a)lsil.com> writes: > xemacs-devel, and xemacs-base, as specified by the package index on the ftp > site), xemacs still doesn't recognize my perl code as being perl (it just > uses the fundamental mode). Is their something I have to turn on besides > prog-modes-package? Not really. Are you sure XEmacs can actually find the package? What does M-x locate-library RET cperl-mode RET say? Jan

2 participants
1 comments

Re: prog-modes package and perl mode 24 years, 11 months

Adrian Aichner

>>>>> "Noah" == Noah Romer <noah.romer(a)lsil.com> writes: Noah> I don't know that this is the right place to send Noah> this, but I can't find any mention of this in the FAQ on Noah> www.xemacs.org and this is the only email address I can find Noah> associated w/ the prog-modes package. Noah> I recently installed xemacs 21.1 on a Solaris system Noah> (SunOS 5.6) and am in the process of installing various Noah> packages to get it up to the functionality of the previous Noah> installation (19.x). However, I've run into the problem that Noah> despite having installed prog-modes (and mail-lib, Noah> xemacs-devel, and xemacs-base, as specified by the package Noah> index on the ftp site), xemacs still doesn't recognize my Noah> perl code as being perl (it just uses the fundamental Noah> mode). Is their something I have to turn on besides Noah> prog-modes-package? Noah, I assume you built XEmacs from sources. If so, check out (e:\export\home\tmp\21.1\xemacs\)README.packages Also have a look at Help->Samples->Sample .emacs and search for font-lock and auto-mode-alist. Try starting xemacs -vanilla and visit a perl file (.pl). For me it is displayed in cperl-mode with font-lock-mode turned on. The modeline shows (CPerl Font). If this does not work for you, try M-x cper-mode RET M-x font-lock-mode RET If this still does not work for you, send me your values for late-packages ("c:\\Program Files\\XEmacs\\site-packages\\" "c:\\Program Files\\XEmacs\\site-packages\\pgnus-0.85\\" "c:\\Program Files\\XEmacs\\xemacs-packages\\" "c:\\Program Files\\XEmacs\\xemacs-packages\\man\\") auto-mode-alist (("\\.idl\\b" . TerIDL-mode) ("\\.verilog\\'" . verilog-mode) ("\\.vlog\\'" . verilog-mode) ("\\.f\\'" . verilog-mode) ("\\.dv\\'" . verilog-mode) ("\\.v\\'" . verilog-mode) ("\\.asc$" . asc-mode) ("\\.C$" . c++-mode) ("\\.cc$" . c++-mode) ("\\.hh$" . c++-mode) ("\\.t$" . c++-mode) ("\\.c$" . c-mode) ("\\.h$" . c++-mode) ("\\.s$" . asm-mode) ("\\.n?awk$" . awk-mode) ("\\.csh$" . csh-sh-mode) ("\\.ksh$" . ksh-sh-mode) ("\\.sh$" . sh-sh-mode) ("\\.i[abcg]$" . bib-mode) ("\\.[ce]l$" . lisp-mode) ("\\.m$" . objc-mode) ("\\..*adr$" . lisp-mode) ("\\..*tdl$" . lisp-mode) ("\\.A$" . mim-mode) ("\\.[1-9]$" . nroff-mode) ("\\.p[lm]$" . perl-mode) ("\\.e?ps$" . postscript-mode) ("\\.py$" . python-mode) ("\\.sgml$" . sgml-mode) ("\\.hex" . hexl-mode) ("\\.html$" . html-mode) ("\\.tcl$" . tcl-mode) ("\\.tex$" . tex-mode) ("\\.txt$" . text-mode) ("\\.mk$" . makefile-mode) ("[Mm]akefile" . makefile-mode) ("\\.?\$cshrc\\|login\$\$[^\\/]+\$?$" . csh-sh-mode) ("\\.?\$profile\$\$[^\\/]+\! ! $?$" . sh-sh-mode) ("\\.C$" . c++-mode) ("\\.cc$" . c++-mode) ("\\.hh$" . c++-mode) ("\\.c$" . c-mode) ("\\.h$" . c-mode) ("\\.\$tar\\|tgz\\|tar\\.gz\$\\'" . tar-mode) ("\\.java\\'" . jde-mode) ("\\.te?xt\\'" . text-mode) ("\\.[chi]\\'" . c-mode) ("\\.el\\'" . emacs-lisp-mode) ("\\.\$?:[CH]\\|cc\\|hh\$\\'" . c++-mode) ("\\.[ch]\$pp\\|xx\\|\\+\\+\$\\'" . c++-mode) ("\\.java\\'" . java-mode) ("\\.idl\\'" . idl-mode) ("\\.f\$?:or\$?\\'" . fortran-mode) ("\\.F\$?:OR\$?\\'" . fortran-mode) ("\\.[fF]90\\'" . f90-mode) ("\\.\$[pP][Llm]\\|al\$\\'" . perl-mode) ("\\.py\\'" . python-mode) ("\\.texi\$?:nfo\$?\\'" . texinfo-mode) ("\\.ad[abs]\\'" . ada-mode) ("\\.c?l\$?:i?sp\$?\\'" . lisp-mode) ("\\.p\$?:as\$?\\'" . pascal-mode) ("\\.ltx\\'" . latex-mode) ("\\.[sS]\\'" . asm-mode) ("[Cc]hange.?[Ll]og?\$?:.[0-9]+\$?\\'" . change-log-mode) ("\\$CHANGE_LOG\\$\\.TXT" . change-log-mode) ("\\.scm?\$?:\\.[0-9]*\$?\\'" . scheme-mode) ("\\.e\\'" . eiffel-mode) ("\\.mss\\'" .! ! scribe-mode) ("\\.m\$?:[mes]\\|an\$\\'" . nroff-mode) ("\\.icn\\'" . icon-mode) ("\\.\$?:[ckz]?sh\\|shar\$\\'" . sh-mode) ("/\\.\$?:bash_\\|z\$?\$profile\\|login\\|logout\$\\'" . sh-mode) ("/\\.\$?:[ckz]sh\\|bash\\|tcsh\\|es\\|xinit\\|startx\$rc\\'" . sh-mode) ("/\\.\$?:[kz]shenv\\|xsession\$\\'" . sh-mode) ("\\.[12345678]\\'" . nroff-mode) ("\\.[tT]e[xX]\\'" . tex-mode) ("\\.\$?:sty\\|cls\\|bbl\$\\'" . latex-mode) ("\\.bib\\'" . bibtex-mode) ("\\.article\\'" . text-mode) ("\\.letter\\'" . text-mode) ("\\.\$?:tcl\\|exp\$\\'" . tcl-mode) ("\\.wrl\\'" . vrml-mode) ("\\.awk\\'" . awk-mode) ("\\.prolog\\'" . prolog-mode) ("\\.\$?:arc\\|zip\\|lzh\\|zoo\$\\'" . archive-mode) ("\\`/tmp/Re" . text-mode) ("/Message[0-9]*\\'" . text-mode) ("/drafts/[0-9]+\\'" . mh-letter-mode) ("^/tmp/fol/" . text-mode) ("\\.y\\'" . c-mode) ("\\.lex\\'" . c-mode) ("\\.m\\'" . objc-mode) ("\\.oak\\'" . scheme-mode) ("\\.s?html?\\'" . html-mode) ("\\.htm?l?3\\'" . html3-mode) ("\\.\$?:! ! sgml?\\|dtd\$\\'" . sgml-mode) ("\\.c?ps\\'" . postscript-mode) ("[/\\][._].*emacs\\'" . emacs-lisp-mode) ("\\.m4\\'" . autoconf-mode) ("configure\\.in\\'" . autoconf-mode) ("\\.ml\\'" . lisp-mode) ("\\.ma?k\\'" . makefile-mode) ("[Mm]akefile\$\\.\\|\\'\$" . makefile-mode) ("\\.X\$defaults\\|environment\\|resources\\|modmap\$\\'" . xrdb-mode) ("/app-defaults/" . xrdb-mode) ("\\.[^/]*wm2?\$?:rc\$?\\'" . winmgr-mode) ("\\.\$?:jpe?g\\|JPE?G\\|png\\|PNG\\|gif\\|GIF\\|tiff?\\|TIFF?\$\\'" . image-mode)) Noah> In case it's of any use, this is the section of my .emacs Noah> file that xemacs is using to turn various packages on: Your .emacs does not look right. Where do all the (*-package t) come from? Regards, Adrian Noah> (custom-set-variables '(speedbar-package t) '(efs-package t) Noah> '(sh-script-package t) '(cperl-electric-parens t) Noah> '(text-modes-package t) '(prog-modes-package t) Noah> '(ediff-package t) '(vc-package t) '(textools-package t) Noah> '(strokes-package t) '(edit-utils-package t) Noah> '(texinfo-package t) '(time-package t) '(ispell-package t) Noah> '(pcl-cvs-package t) '(reftex-package t) '(c-support-package Noah> t) '(eudc-package t) '(debug-package t) '(apel-package t) Noah> '(mailcrypt-package t) '(tm-package t) Noah> '(hm--html-menus-package t) '(cc-mode-package t) Noah> '(auctex-package t) '(net-utils-package t) Noah> '(mail-lib-package t) '(xemacs-base-package t) '(cperl-hairy Noah> t) '(gnus-package t) '(font-lock-mode t nil (font-lock))) Noah> (custom-set-faces) Noah> Thanks, Noah Romer -- 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

prog-modes package and perl mode 24 years, 11 months

Noah Romer

I don't know that this is the right place to send this, but I can't find any mention of this in the FAQ on www.xemacs.org and this is the only email address I can find associated w/ the prog-modes package. I recently installed xemacs 21.1 on a Solaris system (SunOS 5.6) and am in the process of installing various packages to get it up to the functionality of the previous installation (19.x). However, I've run into the problem that despite having installed prog-modes (and mail-lib, xemacs-devel, and xemacs-base, as specified by the package index on the ftp site), xemacs still doesn't recognize my perl code as being perl (it just uses the fundamental mode). Is their something I have to turn on besides prog-modes-package? In case it's of any use, this is the section of my .emacs file that xemacs is using to turn various packages on: (custom-set-variables '(speedbar-package t) '(efs-package t) '(sh-script-package t) '(cperl-electric-parens t) '(text-modes-package t) '(prog-modes-package t) '(ediff-package t) '(vc-package t) '(textools-package t) '(strokes-package t) '(edit-utils-package t) '(texinfo-package t) '(time-package t) '(ispell-package t) '(pcl-cvs-package t) '(reftex-package t) '(c-support-package t) '(eudc-package t) '(debug-package t) '(apel-package t) '(mailcrypt-package t) '(tm-package t) '(hm--html-menus-package t) '(cc-mode-package t) '(auctex-package t) '(net-utils-package t) '(mail-lib-package t) '(xemacs-base-package t) '(cperl-hairy t) '(gnus-package t) '(font-lock-mode t nil (font-lock))) (custom-set-faces) Thanks, Noah Romer

1 participants
0 comments

Re: Build failure, xemacs-21.1.2 on rh6-based linux-alpha-unknown 24 years, 11 months

Jan Vroonhof

Hrvoje Niksic <hniksic(a)srce.hr> writes: > int f() { > int a; > int *ip; > a = 10; > ip = &a; > return *ip; > } > > How is this any different than what is done above? In this case both objects are of the same type. float foo; LispObject f(LispObject *bar) { LispObject rval; foo = 3.0; rval = *LispObject; foo = 5.0; return rval; } Here the compiler can remove the first assignment to foo under strict aliasing because it can assume a LispObject pointer never points to a float. > > "everybody has fixed their code already because other compilers have > > been doing this optimization for ages" > > If the last is really the case, then we indeed have nothing to worry > about. XEmacs has compiled and run on non-Gcc compilers for ages. > *If* the last is really the case. Yes, but which of them do this optimization? Jan

2 participants
1 comments

Re: XEmacs is not 64-bit clean (was Re: Build failure, xemacs-21.1.2 on rh6-based linux-alpha-unknown) 24 years, 11 months

Greg J. Badros

SL Baur <steve(a)xemacs.org> writes: > Greg Badros <gjb(a)cs.washington.edu> writes in xemacs-beta(a)xemacs.org: > > >> > I looked at src/xemacs-- it's u+x bit is not set, and it is a large > >> > file that is just a big hole on disk (reads as all NULLs). > > Urgh. There are known problems with XEmacs on DEC Alpha using OSF. > If you have a temacs, cd to the src directory and run `make > run-temacs'. Does that work? Yes, it does. > > > Ok, thanks for your help. Xemacs did build w/o many problems on Intel, > > so it's definitely an issue only on my Alpha box. > > XEmacs is *not* 64 bit clean. On DEC OSF, temacs and dumped xemacs are > semi-functional, but some internals are broken, definitely including > the character sets/character category tables. Do you have any interest in trying to make XEmacs 64bit clean? I will gladly give you an account on my Alpha box here at the UW if you're interested in getting XEmacs to work better with GNU/Linux-Alpha. Thanks, Greg

1 participants
0 comments

Re: Changing fonts from menu causes error 24 years, 11 months

Andy Piper

At 11:17 AM 6/17/99 +0200, rpluim(a)bigfoot.com wrote: > >in XEmacs 21.2 (beta16) "Sumida" [Lucid] (i586-pc-linux) of Mon Jun >14 1999 on ltrpluim > >changing the font family from the menus causes "Wrong type argument: >number-char-or-marker-p, nil" to be signalled in >font-menu-set-font. The following patch fixes it for me, but I don't >know if it's the right fix. It may well be. I forgot this was outstanding. Sorry andy -------------------------------------------------------------- Dr Andy Piper Senior Consultant Architect, BEA Systems Ltd

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