August 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Didier Verna

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > But it's not going to be immediately available on any platform besides > Red Hat Linux, right? Debian Linux doesn't seem to have it, anyway. > Nor does ftp.redhat.com, for that matter. Where did you see this? ?!?!? Huh, on my hard disk :-) I wonder how it can have landed there, since indeed, it doesn't appear on the redhat ftp site... I'll check my RH5.1 CD-ROM tonite. --didier

1 participants
0 comments

GIF without LZW 26 years, 3 months

Didier Verna

After spending a whole saturday afternoon trying to recompile my redhat 5.1 kernel because of a broken Config.in, I finally got it with APM, multicast, and a brand new driver for my zip+. But that's not the point :-) Yesterday, I did a mass RPM upgrade with my zip+, and while updating the packages, I saw one named libungif. The doc string says that this library reads gif, and can write it without using LZW. COuld this be of interest, with regards to the licensing problems ? -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 80 72 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

2 participants
1 comments

Re: 20.1-b51 crash on Solaris 26 years, 3 months

Jan Vroonhof

SL Baur <steve(a)xemacs.org> writes: > > I was running with sparcworks on xemacs. I moved the scrollbar on one > > of the source windows and got the following crash. What hope is there of finding it. Is it in anyway reproducable? Even if it is occassionally reprocable has somebody been annoyed enough to start his XEmacsen under gdb? Jan P.S. I wonder if it is reall sparworks related or that the eos:: stuff just exercices the margin code a lot more.

1 participants
0 comments

Re: Suggested fixes for cperl-mode 26 years, 3 months

Jan Vroonhof

Ilya Zakharevich <ilya(a)math.ohio-state.edu> writes: > In this particular case: compatibility with *what*? If you feel it is > important, please comment it likewise. Like I said, I din't consiously do it in this case, though I guess in this case it provides compatibility with XEmacs 20.2 (and, depending on the byte compiling settings, with XEmacs 19.x) but I am not sure whether that also holds for the rest of cperl (I haven't checked). If you do only runtime tests it is possibly to use XEmacs 19.16 bytecompiled .elc files under almost all current emacsen including FSF 19.34 and 20.2, but cperl currently doesn't so lets not worry about that. > Do not follow you unless backward-delete-function is not > CPerl-specific... Probably it is not, so it is OK. Indeed backward-delete-function is not CPerl-specific. Do you want a combined patch with the other minor changes? Jan

1 participants
0 comments

[patch] `ielm.el' fix, as requested. 26 years, 3 months

Karl M. Hegbloom

1998-08-19 Karl M. Hegbloom <karlheg(a)bittersweet.inetarena.com> * ielm.el (ielm-eval-input): Change `:', `::', `:::' to `!'..., since the `:' is special syntax now for keyword variables. (several other occurances also changed.) I chose !, because shells use that character for history expansion. (ielm-eval-input): Check that `ielm-string' is not null. Integrated reversed patch from Gregory Neil Shapiro <gshapiro(a)sendmail.org>. Index: ielm.el =================================================================== RCS file: /usr/local/cvsroot/xemacs-packages/libs/xemacs-devel/ielm.el,v retrieving revision 1.1.1.1 diff -u -u -r1.1.1.1 ielm.el --- ielm.el 1998/01/14 06:32:32 1.1.1.1 +++ ielm.el 1998/08/19 07:57:48 ＠＠ -283,7 +283,8 ＠＠ (ielm-output "") ; result to display (ielm-wbuf ielm-working-buffer) ; current buffer after evaluation (ielm-pmark (ielm-pm))) - (if (not (ielm-is-whitespace ielm-string)) + (if (and (not (null ielm-string)) + (not (ielm-is-whitespace ielm-string))) (progn (condition-case err (let (rout) ＠＠ -301,15 +302,15 ＠＠ (if (ielm-is-whitespace (substring ielm-string ielm-pos)) ;; need this awful let convolution to work around ;; an Emacs bug involving local vbls and let binding - (let ((:save :) - (::save ::) - (:::save :::)) + (let ((!save !) + (!!save !!) + (!!!save !!!)) (save-excursion (set-buffer ielm-working-buffer) (condition-case err - (let ((: :save) - (:: ::save) - (::: :::save) + (let ((! !save) + (!! !!save) + (!!! !!!save) (ielm-obuf (current-buffer))) (setq ielm-result (eval ielm-form)) (setq ielm-wbuf (current-buffer)) ＠＠ -345,12 +346,13 ＠＠ (if ielm-noisy (ding)) (setq ielm-output (concat ielm-output "*** " ielm-error-type " *** ")) (setq ielm-output (concat ielm-output ielm-result))) - ;; There was no error, so shift the ::: values - (setq ::: ::) - (setq :: :) - (setq : ielm-result)) + ;; There was no error, so shift the !!! values + (setq !!! !!) + (setq !! !) + (setq ! ielm-result)) (setq ielm-output (concat ielm-output "\n")))) - (setq ielm-output (concat ielm-output ielm-prompt)) + (if (not (null ielm-string)) + (setq ielm-output (concat ielm-output ielm-prompt))) (comint-output-filter (ielm-process) ielm-output))) ;;; Process and marker utilities ＠＠ -386,7 +388,7 ＠＠ * \\[comint-dynamic-complete] completes Lisp symbols (or filenames, within strings), or indents the line if there is nothing to complete. -During evaluations, the values of the variables `:', `::', and `:::' +During evaluations, the values of the variables `!', `!!', and `!!!' are the results of the previous, second previous and third previous evaluations respectively. ＠＠ -436,17 +438,17 ＠＠ (setq fill-paragraph-function 'lisp-fill-paragraph) ;; Value holders - (setq : nil) - (make-local-variable ':) - (setq :: nil) - (make-local-variable '::) - (setq ::: nil) - (make-local-variable ':::) + (setq ! nil) + (make-local-variable '!) + (setq !! nil) + (make-local-variable '!!) + (setq !!! nil) + (make-local-variable '!!!) ;; font-lock support (make-local-variable 'font-lock-defaults) (setq font-lock-defaults - '(ielm-font-lock-keywords nil nil ((?: . "w") (?- . "w") (?* . "w")))) + '(ielm-font-lock-keywords nil nil ((?! . "w") (?- . "w") (?* . "w")))) ;; A dummy process to keep comint happy. It will never get any input (if (comint-check-proc (current-buffer)) nil

1 participants
0 comments

[Success] XEmacs 21.0-b53/pre10 "Erzgeberg" on Linux 26 years, 3 months

Kazuyoshi Furutaka

[i686-GNU-linux] Source : patched up from 21.0 beta52 Make : GNU Make version 3.76.1 CC : gcc version pgcc-2.90.29 980515 (egcs-1.0.3 release) OS : Linux 2.0.36pre6 (RedHat 5.1) X : X11R6.3 (Accelerated-X ver.4.1 w/ XFree86 3.3.2) gdb : GDB 4.17 [alpha-GNU-linux] Source : patched up from 21.0 beta52 Make : GNU Make version 3.75 CC : egcs-2.90.29 980515 (egcs-1.0.3 release) OS : Linux 2.1.115 (StataboWare 1.4beta) X : X11R6.3 (XFree86 3.3.2) gdb : GDB 4.16 -- Kazuyoshi Furutaka furutaka(a)tokai.pnc.go.jp furutaka(a)jb3.so-net.ne.jp

1 participants
0 comments

Re: Macros: Scheme vs Common Lisp 26 years, 3 months

Michael Sperber

>>>>> "Holger" == Holger Schauer <schauer(a)coling.uni-freiburg.de> writes: >>>>> "MS" == Michael Sperber schrieb am 18 Aug 1998 14:52:08 +0200: Holger> [Common Lisp and Elisp] MS> (defvar bar 23) MS> (defmacro foo () 'bar) MS> (let ((bar 42)) (foo)) => 42 Holger> (foo) => 23 Holger> Excuse me, but this is evil by design. MS> Absolutely right, Common Lisp's macro system is evil by design. MS> I just want macros to obey the same scoping rules as the rest of MS> the language, and they don't in Common Lisp. Holger> Interesting. Seems I don't understand what you want to say. Holger> (defvar bar 23) Holger> (defun foo () Holger> bar) Holger> (let ((bar 42)) (foo)) => 42 Holger> (foo) => 23 Holger> Where is the difference ? I'm an idiot, and my Common Lisp is obviously rusty. I'm sorry. I meant (setq bar 23) instead of (defvar bar 23). Of course, in the case of dynamic binding, referring to a binding from a macro does the right thing in Common Lisp. MS> No, it isn't. There are many perfectly valid reasons for a macro MS> to refer to an outer binding within the same lexical scope. Holger> What are those reasons ? Why not use a different name in let ? I don't understand that last sentence. If I create a package, and I put abstractions in that package, may they be syntactic or semantic abstractions, I want those abstractions to be able to access bindings in the package. Holger> You also have to when you use functions. This would introduce Holger> a non-intuitive difference between the use of macros and those Holger> of functions, if I understand you correctly. And you seem to Holger> find some benefit in it: which is it ? [1] Holger> [1] This is a serious question, I'm not trying to suggest that there Holger> isn't a benefit. Absolutely. I just fucked up the example. In the case of special variables, you do want the macro to refer to the dynamically bound version. Scheme doesn't have dynamic binding, so the Scheme example was not a translation of the original CL example I gave. It is a translation of the revised version. Again, sorry about creating such confusion. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

[Success] 21.0 "Erzgeberg" XEmacs Lucid on i686-pc-linux 26 years, 3 months

Hayashi Tanaka

Patched up from beta52. > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /home/tanaka/src/xemacs-21.0-b53/Installation: > (Output from most recent run of ./configure)

1 participants
0 comments

Re: [SCROLL] Grrr ! Grrr ! 26 years, 3 months

Karl M. Hegbloom

If you start XEmacs with `-bg grey30 -fg white', the default toolbar comes up with the colors you'd expect, but the `whitespace-mode' toolbar button, which enters the toolbar later, is the same color it is with default XEmacs colors. I found that the Info toolbar does the same thing; its buttons are not white on grey30 as they should be, but are default colors.

1 participants
0 comments

Re: Where do you want to go tomorrow? 26 years, 3 months

Karl M. Hegbloom

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: >> Cool. Do you have any trouble finding computer books where you >> live? Hrvoje> Not with finding as much as with prices. The "computer Hrvoje> books" are usually pretty expensive hard-cover editions Hrvoje> that cost 200-400K (divide with 6 to get a price in Hrvoje> dollars), which is very expensive given the salaries here. Hrvoje> Used books are cheaper, but it's hard to find a used book Hrvoje> about programming, especially about something as exotic as Hrvoje> Lisp or Scheme. I wonder if it's too expensive to order them from the USA, and have them shipped to you? See: http://www.powells.portland.or.us/ and especially the "Technical books" link down in the lower right part of the page. The have new and used titles, and can usually find things they don't have in stock if you ask them.

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 August 1998