May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: De-GIFfing (was Re: beta38-pre3 has been uploaded) 26 years, 7 months

SL Baur

Hrvoje Niksic <hniksic(a)srce.hr> writes: > Martin Buchholz <martin(a)xemacs.org> writes: >> I also vote for continuing to include GIF-reading capability in >> XEmacs. > If it comes to a vote, I'm pro GIF reading. GIF reading is not up for a vote[1]. Where did you get the impression that it was? I think we should finish de-GIFfing XEmacs by converting the files in xmine to PNG and if Jareth cannot distribute a separate giflib, then reluctantly we'll have to see about putting the reading code back in the XEmacs core. Footnotes: [1] That would imply I would have to abide by a decision to take it out and I have no intention of doing so.

2 participants
1 comments

[SUCCESS] 21.0 "Repartida-pre3" XEmacs Lucid (beta38) on i386-pc-cygwin32 26 years, 7 months

Andy Piper

Needed my cygwin32.h patch to compile andy > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /development/build/xemacs-20/Installation: > (Output from most recent run of ./configure) uname -a: CYGWIN32_NT ARMAGEDON 4.0 19.1 i586 unknown ./configure '--site-includes=/usr/local/include' '--package-path=/usr/gnu/lib/xemacs/packages' XEmacs 21.0-b38 "Repartida-pre3" configured for `i386-pc-cygwin32'. Where should the build process find the source code? /development/build/xemacs-20 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/cygwin32.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O2 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? default What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11R6.3/include Where do we find X Windows libraries? /usr/X11R6.3/lib Additional header files: /usr/local/include Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for GIF image conversion. Compiling in support for JPEG image conversion. Compiling in support for PNG image conversion. Compiling in support for TIFF image conversion. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in File coding support. Compiling in support for OffiX. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. WARNING: --------------------------------------------------------- WARNING: Compiling in support for runtime error checking. WARNING: XEmacs will run noticeably more slowly as a result. WARNING: Error checking is on by default for XEmacs beta releases. WARNING: --------------------------------------------------------- > /development/build/xemacs-20/beta.err does not exist!

1 participants
0 comments

Re: select-window focus problem [was: Re: minor compile.el bug] 26 years, 7 months

Hrvoje Niksic

Ben Wing <ben(a)666.com> writes: > This business of binding focus follows mouse to nil and then calling > sit-for 0 is really really evil. I think the correct solution is to > make a new command focus-on-frame, somewhat analogous to > switch-to-buffer, that directly changes the window manager's focus. Maybe `set-frame-focus' would be a better name. > Also, do there exist forms save-selected-frame and > with-selected-frame? If not, there should be. I can code and document these. > Also, focus-follows-mouse needs to be a console property instead of > just a simple variable. Oops! Yes, you are right. Should we make it a console method, and use the magic symbol stuff for compatibility? Or, should we make it a console-local variable, which is kludgier but creates less problems? > Also, the default value of focus-follows-mouse should be set > according to the window manager's focus policy. This might entail > some special case code for particular window managers (each of which > has their own protocol for obtaining this property), with a default > value of nil under Unix and true under Windows. Why not the opposite -- nil under Windows, and true under Unix? -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- "Silence!" cries Freydag. "I did not call thee in for a consultation!" "They are my innards! I will not have them misread by a poseur!"

2 participants
1 comments

Re: De-GIFfing (was Re: beta38-pre3 has been uploaded) 26 years, 7 months

SL Baur

Hrvoje Niksic <hniksic(a)srce.hr> writes: [From Unisys:] > In all cases, a written license agreement or statement signed by an > authorized Unisys representative is required from Unisys for all use, > sale or distribution of any software (including so-called "freeware") > and/or hardware providing LZW conversion capability (for example, > downloaded software used for creating/displaying GIF images). > ^^^^^^^^^^ > Are we taking that seriously? I saw that too, and I guess the answer is that until we're called on it (or are sued -- there's nobody to actually sue XEmacs-wise and Bob doesn't care with regards to InfoDock), no we're not taking that seriously. The United States is insane. Who knows what will be illegal[1] next? Footnotes: [1] To people without political pull.

1 participants
0 comments

[PATCH] Update 1998-05-02 26 years, 7 months

Hrvoje Niksic

Documentation updates, plus a few random changes. Applies on top of my previous patches. C ChangeLog: 1998-05-01 Hrvoje Niksic <hniksic(a)srce.hr> * data.c (Fneq): Fix docstring. (arithcompare_many): Slightly simplify. Lisp ChangeLog: 1998-05-01 Hrvoje Niksic <hniksic(a)srce.hr> * byte-optimize.el (byte-boolean-vars): Removed. (byte-optimize-lapcode): Use `built-in-variable-type' instead of lookup through `byte-boolean-vars'. man/ChangeLog: 1998-05-02 Hrvoje Niksic <hniksic(a)srce.hr> * lispref/numbers.texi (Comparison of Numbers): Document multi-arg comparison functions. --- lisp/byte-optimize.el.orig Fri May 1 20:21:08 1998 +++ lisp/byte-optimize.el Fri May 1 21:49:08 1998 ＠＠ -1396,29 +1396,41 ＠＠ ;;; old-pop-ups are not EQ when really they are. So we have to know what ;;; the BOOL variables are, and not perform this optimization on them. ;;; -(defconst byte-boolean-vars - '(abbrev-all-caps purify-flag find-file-compare-truenames - find-file-use-truenames find-file-visit-truename - find-file-existing-other-name byte-metering-on - zmacs-regions zmacs-region-active-p zmacs-region-stays - atomic-extent-goto-char-p suppress-early-error-handler - noninteractive ignore-kernel debug-on-quit debug-on-next-call - modifier-keys-are-sticky x-allow-sendevents vms-stmlf-recfm - disable-auto-save-when-buffer-shrinks indent-tabs-mode - load-in-progress load-warn-when-source-newer load-warn-when-source-only - load-ignore-elc-files load-force-doc-strings - fail-on-bucky-bit-character-escapes popup-menu-titles - menubar-show-keybindings completion-ignore-case - canna-empty-info canna-through-info canna-underline - canna-inhibit-hankakukana x-handle-non-fully-specified-fonts - print-escape-newlines print-readably - delete-exited-processes truncate-partial-width-windows - visible-bell no-redraw-on-reenter cursor-in-echo-area - inhibit-warning-display parse-sexp-ignore-comments words-include-escapes - scroll-on-clipped-lines pop-up-frames pop-up-windows) - "DEFVAR_BOOL variables. Giving these any non-nil value sets them to t. -If this does not enumerate all DEFVAR_BOOL variables, the byte-optimizer -may generate incorrect code.") + +;;; This used to hold a large list of boolean variables, which had to +;;; be updated every time a new DEFVAR_BOOL is added, making it very +;;; hard to maintain. Such a list is not necessary under XEmacs, +;;; where we can use `built-in-variable-type' to query for boolean +;;; variables. + +;(defconst byte-boolean-vars +; '(abbrev-all-caps purify-flag find-file-compare-truenames +; find-file-use-truenames delete-auto-save-files byte-metering-on +; x-seppuku-on-epipe zmacs-regions zmacs-region-active-p +; zmacs-region-stays atomic-extent-goto-char-p +; suppress-early-error-handler-backtrace noninteractive +; inhibit-early-packages inhibit-autoloads debug-paths +; inhibit-site-lisp debug-on-quit debug-on-next-call +; modifier-keys-are-sticky x-allow-sendevents +; mswindows-dynamic-frame-resize focus-follows-mouse +; inhibit-input-event-recording enable-multibyte-characters +; disable-auto-save-when-buffer-shrinks +; allow-deletion-of-last-visible-frame indent-tabs-mode +; load-in-progress load-warn-when-source-newer +; load-warn-when-source-only load-ignore-elc-files +; load-force-doc-strings fail-on-bucky-bit-character-escapes +; popup-menu-titles menubar-show-keybindings completion-ignore-case +; canna-empty-info canna-through-info canna-underline +; canna-inhibit-hankakukana enable-multibyte-characters +; re-short-flag x-handle-non-fully-specified-fonts +; print-escape-newlines print-readably delete-exited-processes +; windowed-process-io visible-bell no-redraw-on-reenter +; cursor-in-echo-area inhibit-warning-display +; column-number-start-at-one parse-sexp-ignore-comments +; words-include-escapes scroll-on-clipped-lines) +; "DEFVAR_BOOL variables. Giving these any non-nil value sets them to t. +;If this does not enumerate all DEFVAR_BOOL variables, the byte-optimizer +;may generate incorrect code.") (defun byte-optimize-lapcode (lap &optional for-effect) "Simple peephole optimizer. LAP is both modified and returned." ＠＠ -1497,7 +1509,8 ＠＠ ((and (eq 'byte-varref (car lap2)) (eq (cdr lap1) (cdr lap2)) (memq (car lap1) '(byte-varset byte-varbind))) - (if (and (setq tmp (memq (car (cdr lap2)) byte-boolean-vars)) + (if (and (setq tmp (eq (built-in-variable-type (car (cdr lap2))) + 'boolean)) (not (eq (car lap0) 'byte-constant))) nil (setq keep-going t) ＠＠ -1803,7 +1816,8 ＠＠ (eq (car (car (setq tmp (cdr (memq (cdr lap2) lap))))) 'byte-varref) (eq (cdr (car tmp)) (cdr lap1)) - (not (memq (car (cdr lap1)) byte-boolean-vars))) + (not (eq (built-in-variable-type (car (cdr lap1))) + 'boolean))) ;;(byte-compile-log-lap " Pulled %s to end of loop" (car tmp)) (let ((newtag (byte-compile-make-tag))) (byte-compile-log-lap --- src/data.c.orig Fri May 1 19:49:50 1998 +++ src/data.c Sat May 2 00:13:04 1998 ＠＠ -187,7 +187,7 ＠＠ even though they are not the same object and are in fact of different types. This is ABSOLUTELY AND UTTERLY HORRENDOUS but is necessary to preserve byte-code compatibility with v19. This kludge is known as the -\"char-to-int confoundance disease\" and appears in a number of other +\"char-int confoundance disease\" and appears in a number of other functions with `old-foo' equivalents. Do not use this function! ＠＠ -374,9 +374,9 ＠＠ DEFUN ("characterp", Fcharacterp, 1, 1, 0, /* Return t if OBJECT is a character. -Unlike in XEmacs v19 and Emacs, a character is its own primitive type. +Unlike in XEmacs v19 and FSF Emacs, a character is its own primitive type. Any character can be converted into an equivalent integer using -`char-to-int'. To convert the other way, use `int-to-char'; however, +`char-int'. To convert the other way, use `int-char'; however, only some integers can be converted into characters. Such an integer is called a `char-int'; see `char-int-p'. ＠＠ -434,7 +434,7 ＠＠ DEFUN ("char-int-p", Fchar_int_p, 1, 1, 0, /* Return t if OBJECT is an integer that can be converted into a character. -See `char-to-int'. +See `char-int'. */ (object)) { ＠＠ -1017,16 +1017,15 ＠＠ arithcompare_many (enum arith_comparison comparison, int nargs, Lisp_Object *args) { - REGISTER int argnum; - for (argnum = 1; argnum < nargs; argnum++) - if (EQ (arithcompare (args[argnum-1], args[argnum], comparison), Qnil)) + for (; --nargs > 0; args++) + if (NILP (arithcompare (*args, *(args + 1), comparison))) return Qnil; return Qt; } DEFUN ("=", Feqlsign, 1, MANY, 0, /* -Return t if all the arguments are equal. +Return t if all the arguments are numerically equal. The arguments may be numbers, characters or markers. */ (int nargs, Lisp_Object *args)) ＠＠ -1071,7 +1070,7 ＠＠ } DEFUN ("/=", Fneq, 1, MANY, 0, /* -Return t if the sequence of arguments is monotonically increasing. +Return t if no two arguments are numerically equal. The arguments may be numbers, characters or markers. */ (int nargs, Lisp_Object *args)) --- man/lispref/numbers.texi.orig Sat May 2 01:00:01 1998 +++ man/lispref/numbers.texi Sat May 2 01:00:49 1998 ＠＠ -240,7 +240,7 ＠＠ Here's a function to do this: ＠example -(defvar fuzz-factor 1.0e-6) +(defconst fuzz-factor 1.0e-6) (defun approx-equal (x y) (or (and (= x 0) (= y 0)) (< (/ (abs (- x y)) ＠＠ -257,40 +257,79 ＠＠ limited range of integer values. ＠end quotation -＠defun = number-or-marker1 number-or-marker2 -This function tests whether its arguments are numerically equal, and -returns ＠code{t} if so, ＠code{nil} otherwise. +In addition to numbers, all of the following functions also accept +characters and markers as arguments, and treat them as their number +equivalents. + +＠defun = number &rest more-numbers +This function returns ＠code{t} if all of its arguments are numerically +equal, ＠code{nil} otherwise. + +＠example +(= 5) + ＠result{} t +(= 5 6) + ＠result{} nil +(= 5 5.0) + ＠result{} t +(= 5 5 6) + ＠result{} nil +＠end example ＠end defun -＠defun /= number-or-marker1 number-or-marker2 -This function tests whether its arguments are numerically not equal. It -returns ＠code{t} if so, and ＠code{nil} otherwise. +＠defun /= number &rest more-numbers +This function returns ＠code{t} if no two arguments are numerically +equal, ＠code{nil} otherwise. + +＠example +(/= 5 6) + ＠result{} t +(/= 5 5 6) + ＠result{} nil +(/= 5 6 1) + ＠result{} t +＠end example ＠end defun -＠defun < number-or-marker1 number-or-marker2 -This function tests whether its first argument is strictly less than -its second argument. It returns ＠code{t} if so, ＠code{nil} otherwise. +＠defun < number &rest more-numbers +This function returns ＠code{t} if the sequence of its arguments is +monotonically increasing, ＠code{nil} otherwise. + +＠example +(< 5 6) + ＠result{} t +(< 5 6 6) + ＠result{} nil +(< 5 6 7) + ＠result{} t +＠end example ＠end defun -＠defun <= number-or-marker1 number-or-marker2 -This function tests whether its first argument is less than or equal -to its second argument. It returns ＠code{t} if so, ＠code{nil} -otherwise. +＠defun <= number &rest more-numbers +This function returns ＠code{t} if the sequence of its arguments is +monotonically nondecreasing, ＠code{nil} otherwise. + +＠example +(<= 5 6) + ＠result{} t +(<= 5 6 6) + ＠result{} t +(<= 5 6 5) + ＠result{} nil +＠end example ＠end defun -＠defun > number-or-marker1 number-or-marker2 -This function tests whether its first argument is strictly greater -than its second argument. It returns ＠code{t} if so, ＠code{nil} -otherwise. +＠defun > number &rest more-numbers +This function returns ＠code{t} if the sequence of its arguments is +monotonically increasing, ＠code{nil} otherwise. ＠end defun -＠defun >= number-or-marker1 number-or-marker2 -This function tests whether its first argument is greater than or -equal to its second argument. It returns ＠code{t} if so, ＠code{nil} -otherwise. +＠defun >= number &rest more-numbers +This function returns ＠code{t} if the sequence of its arguments is +monotonically nonincreasing, ＠code{nil} otherwise. ＠end defun -＠defun max number-or-marker &rest numbers-or-markers +＠defun max number &rest more-numbers This function returns the largest of its arguments. ＠example ＠＠ -303,7 +342,7 ＠＠＠end example ＠end defun -＠defun min number-or-marker &rest numbers-or-markers +＠defun min number &rest more-numbers This function returns the smallest of its arguments. ＠example -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Oh lord won't you buy me a color TV...

2 participants
1 comments

Re: [Failure] 21.0 "Repartida-pre3" XEmacs Lucid (beta38) on i386-pc -cygwin32 26 years, 7 months

SL Baur

Mike Hill <mikehill(a)hgeng.com> writes: > 'make' stops here: > process.c:1695: `SIGIO' undeclared (first use this function) You're getting bitten by this code in src/syssignal.h: /* SIGPOLL is the SVR4 signal. Those systems generally define SIGIO as an alias for SIGPOLL, but just in case ... */ #if !defined (SIGIO) && defined (SIGPOLL) # define SIGIO SIGPOLL #endif

3 participants
3 comments

Re: bug setting scrollbar height w/ X resources? 26 years, 7 months

Hrvoje Niksic

Ben Wing <ben(a)666.com> writes: > I think this is a good idea -- it is really not very much work to > add a specifier like this. I've now looked at the specifier code, and decided that I have no clue how to implement this. I started out with something like this: DEFVAR_SPECIFIER ("vertical-scrollbar-visible-p", &Vvertical_scrollbar_visible_p /* *Whether the vertical scrollbar is visible. This is a specifier; use `set-specifier' to change it. */ ); Vvertical_scrollbar_visible_p = make_specifier (Qboolean); set_specifier_fallback (Vvertical_scrollbar_visible_p, list1 (Fcons (Qnil, Qt))); set_specifier_caching (Vvertical_scrollbar_visible_p, slot_offset (struct window, vertical_scrollbar_visible_p), some_window_value_changed, slot_offset (struct frame, vertical_scrollbar_visible_p), vertical_scrollbar_visible_p_changed_in_frame); But it seems non-obvious what each of these functions (like, say, vertical_scrollbar_visible_p_changed_in_frame) should do, and how the caches work out. Horizontal scrollbar is tougher, because it depends on other things, like truncate-lines and truncate-partial-width-windows. What should be the semantics of setting this specifier? So, if you want to have these two specifiers by 21.0, someone else will have to implement them. Kirill? -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Unspeakable horrors from outer space paralyze the living and resurrect the dead!

1 participants
0 comments

rangetab.h creation 26 years, 7 months

Olivier Galibert

The current range_table_entry lrecord declaration sucks because you can't #include it. Beware Steve, this creates a new file. OG. 1998-05-02 Olivier Galibert <galibert(a)pobox.com> * buffer.h: Put the range_table lrecrod declaration where it belongs... * rangetab.h: New file - ...which is here. * rangetab.c: Move declarations to rangetab.h Index: src/buffer.h =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs-20/src/buffer.h,v retrieving revision 1.11 diff -u -r1.11 buffer.h --- buffer.h 1998/03/31 20:11:25 1.11 +++ buffer.h 1998/05/02 09:10:49 ＠＠ -1789,9 +1789,4 ＠＠ #define DOWNCASE(buf, ch) DOWNCASE_TABLE_OF (buf, ch) - -/* put it here, somewhat arbitrarily ... it needs to be in *some* - header file. */ -DECLARE_LRECORD (range_table, struct Lisp_Range_Table); - #endif /* _XEMACS_BUFFER_H_ */ Index: src/rangetab.c =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs-20/src/rangetab.c,v retrieving revision 1.4 diff -u -r1.4 rangetab.c --- rangetab.c 1998/03/31 20:12:07 1.4 +++ rangetab.c 1998/05/02 09:10:49 ＠＠ -23,35 +23,7 ＠＠ /* Written by Ben Wing, August 1995. */ -#include <config.h> -#include "lisp.h" - -typedef struct range_table_entry range_table_entry; -struct range_table_entry -{ - EMACS_INT first; - EMACS_INT last; - Lisp_Object val; -}; - -typedef struct -{ - Dynarr_declare (range_table_entry); -} range_table_entry_dynarr; - -struct Lisp_Range_Table -{ - struct lcrecord_header header; - range_table_entry_dynarr *entries; -}; - -DECLARE_LRECORD (range_table, struct Lisp_Range_Table); -#define XRANGE_TABLE(x) \ - XRECORD (x, range_table, struct Lisp_Range_Table) -#define XSETRANGE_TABLE(x, p) XSETRECORD (x, p, range_table) -#define RANGE_TABLEP(x) RECORDP (x, range_table) -#define GC_RANGE_TABLEP(x) GC_RECORDP (x, range_table) -#define CHECK_RANGE_TABLE(x) CHECK_RECORD (x, range_table) +#include "rangetab.h" Lisp_Object Qrange_tablep; Lisp_Object Qrange_table; ＠＠ -159,7 +131,7 ＠＠ } DEFINE_LRECORD_IMPLEMENTATION ("range-table", range_table, - mark_range_table, print_range_table, 0, + default_dumper, mark_range_table, print_range_table, 0, range_table_equal, range_table_hash, struct Lisp_Range_Table); Index: src/rangetab.h =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs-20/src/rangetab.h,v retrieving revision 1.0 diff -u -r1.0 rangetab.h --- /dev/null Sat May 2 03:05:04 1998 +++ rangetab.h Sat May 2 03:03:02 1998 ＠＠ -0,0 +1,59 ＠＠ +/* XEmacs routines to deal with range tables. + Copyright (C) 1995 Sun Microsystems, Inc. + Copyright (C) 1995 Ben Wing. + +This file is part of XEmacs. + +XEmacs is free software; you can redistribute it and/or modify it +under the terms of the GNU General Public License as published by the +Free Software Foundation; either version 2, or (at your option) any +later version. + +XEmacs is distributed in the hope that it will be useful, but WITHOUT +ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or +FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License +for more details. + +You should have received a copy of the GNU General Public License +along with XEmacs; see the file COPYING. If not, write to +the Free Software Foundation, Inc., 59 Temple Place - Suite 330, +Boston, MA 02111-1307, USA. */ + +/* Synched up with: Not in FSF. */ + +/* Extracted from rangetab.c by O. Galibert, 1998. */ + +#ifndef _XEMACS_RANGETAB_H_ +#define _XEMACS_RANGETAB_H_ + +#include <config.h> +#include "lisp.h" + +typedef struct range_table_entry range_table_entry; +struct range_table_entry +{ + EMACS_INT first; + EMACS_INT last; + Lisp_Object val; +}; + +typedef struct +{ + Dynarr_declare (range_table_entry); +} range_table_entry_dynarr; + +struct Lisp_Range_Table +{ + struct lcrecord_header header; + range_table_entry_dynarr *entries; +}; + +DECLARE_LRECORD (range_table, struct Lisp_Range_Table); +#define XRANGE_TABLE(x) \ + XRECORD (x, range_table, struct Lisp_Range_Table) +#define XSETRANGE_TABLE(x, p) XSETRECORD (x, p, range_table) +#define RANGE_TABLEP(x) RECORDP (x, range_table) +#define GC_RANGE_TABLEP(x) GC_RECORDP (x, range_table) +#define CHECK_RANGE_TABLE(x) CHECK_RECORD (x, range_table) + +#endif

1 participants
0 comments

Change in patches approval process 26 years, 7 months

Hrvoje Niksic

In order to achieve greater efficiency and spread the maintainership load, the XEmacs development team has decided to formalize the process of approving patches. If you have a patch that you would like applied to the XEmacs distribution, you should mail it to <xemacs-patches(a)xemacs.org>. The patches review board will look at your patch and approve or reject it (informing you of either decision). A rejection will always be accompanied by the rationale written by the board member who vetoed the patch. Rejected patches may be modified and resubmitted for re-evaluation. People interested in tracking the patches can subscribe to the patches list by mailing to <xemacs-patches-request(a)xemacs.org>. This list is moderated, and serves *only* for sending patches. Discussion on this list will not be allowed -- that is what xemacs-beta is for. The patches review board are, in alphabetical order: * Steve Baur <steve(a)xemacs.org> * Martin Buchholz <martin(a)xemacs.org> * Olivier Galibert <galibert(a)pobox.com> * P. E. Jareth Hein <jareth(a)camelot-soft.com> * Kyle Jones <kyle_jones(a)wonderworks.com> * Kirill M. Katsnelson <kkm(a)kis.ru> * Hrvoje Niksic <hniksic(a)srce.hr> * Andy Piper <andyp(a)parallax.co.uk> * Michael Sperber [Mr. Preprocessor] <sperber(a)informatik.uni-tuebingen.de> -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Speak softly and carry a +6 two-handed sword.

1 participants
0 comments

Re: De-GIFfing (was Re: beta38-pre3 has been uploaded) 26 years, 7 months

Hrvoje Niksic

Martin Buchholz <martin(a)xemacs.org> writes: > I also vote for continuing to include GIF-reading capability in > XEmacs. If it comes to a vote, I'm pro GIF reading. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- By any chance, have you seen a summoned 9th order fire elemental wandering around? No? Oh.. Tell me if you do.

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