April 1998 - XEmacs-Beta - XEmacs Mailing List Archives

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

Hrvoje Niksic

Didier Verna <verna(a)inf.enst.fr> writes: > That could be due to the recent modifications of the options-menu > code. Do you have some customized variables (like > scrollbars-visible-p) in your options file ? The `scrollbars-visible-p' variable has got to go. It is too /ad hoc/ and unclean (it should be a specifier anyway) to leave it. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- - Now what did we learn from this? - I learned what my liver looks like!

1 participants
0 comments

Re: Lstreams, coding and md5 (was: Re: [PATCH] menubar selection in mswindows) 26 years, 8 months

Pete Ware

Hrvoje Niksic <hniksic(a)srce.hr> writes: > Nope. OBJECT is a buffer or string in internal XEmacs format, and we > don't want to calculate a digest of the internal representation > (that's what the old non-Mule-ized code did), but of the external > representation, as saved to disk etc. I forgot that a buffer is in internal format rather than an abstract type that supports various operations. --pete

1 participants
0 comments

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

Didier Verna

greg(a)alphatech.com (Greg Klanderman) writes: > Between b27 and now, > > XEmacs.scrollbar.height: 0 > > has stopped working. Also, > > XEmacs.scrollBarHeight: 0 > > as documented in sample.Xdefaults and Emacs.ad does not work either. > Anyone know what the right resource is? That could be due to the recent modifications of the options-menu code. Do you have some customized variables (like scrollbars-visible-p) in your options file ?

1 participants
0 comments

bug setting scrollbar height w/ X resources? 26 years, 8 months

Greg Klanderman

Between b27 and now, XEmacs.scrollbar.height: 0 has stopped working. Also, XEmacs.scrollBarHeight: 0 as documented in sample.Xdefaults and Emacs.ad does not work either. Anyone know what the right resource is? greg

1 participants
0 comments

[Success] XEmacs 21.0-b38 "Repartida-pre2", sparc-sun-solaris2.5.1 26 years, 8 months

Adrian Aichner

Building from CVS was easy after I learned that I have to use the -A option to cvs update after updating to a tagged release. > XEmacs Build Report as generated > by build-report-version $Revision: 1.39 $ follows: > Contents of /export/home/tmp/CVSroot/xemacs-20/Installation: > (Output from most recent run of ./configure)

1 participants
0 comments

Re: b37 FAIL 26 years, 8 months

Georg Nikodym

Thanks to Oscar, who in the minimal tagbits debate, piped up about startup problems under Solaris. I rebuilt without -gung-ho and now have a working b37...

1 participants
0 comments

Re: [PATCH] center-to-window-line 26 years, 8 months

Hrvoje Niksic

Ben Wing <ben(a)666.com> writes: > I think you should separate out the clear and redisplay > functionality as well, like force-redisplay, and then move recenter > into Lisp. Makes sense. I'll simply use `redraw-frame' for the "redisplay" part of recenter. > Come to think of it, the various functions that cause redisplay to > happen (such as force-redisplay and redraw-frame) have too much > overlapping functionality and need to be thought out more clearly. Hmm. Maybe. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- You have an unusual magnetic personality. Don't walk too close to metal objects which are not fastened down.

1 participants
0 comments

Re: Lstreams, coding and md5 (was: Re: [PATCH] menubar selection in mswindows) 26 years, 8 months

Pete Ware

> Before coding systems came into the picture, Fmd5 was an exemplary > of Lisp elegance: > > `md5' is a built-in function > (md5 OBJECT &optional START END) > > Documentation: > Return the MD5 message digest of OBJECT, a buffer or string. > > Optional arguments START and END denote positions for computing the > digest of a portion of OBJECT. I'm a MOLE (MOnoLingual Emacs) so take what I have with a shalt shaker but shouldn't OBJECT be in the already appropriate coding system for whatever the message digest is being computed? To put it another way, shouldn't there be a set of functions that given an OBJECT in one coding system return another OBJECT in a different coding system? --pete P.S. I don't understand MULE and I'm not going to try to, so don't waste a lot of time if "no" is an appropriate answer.

1 participants
0 comments

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

Andy Piper

Built and runs fine. 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-pre2" 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: Lstreams, coding and md5 (was: Re: [PATCH] menubar selection in mswindows) 26 years, 8 months

Hrvoje Niksic

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > Hrvoje> ...the point I'm trying to make is that interface to > Hrvoje> user-visible Lisp functions should be well thought-out, or > Hrvoje> problems will arise. > > Yes, indeed. I shudder to think what working on Mule would be like > if Ben had not founded his work on that principle as applied to > internal APIs. Agreed. Ben has done excellent work, and I cannot help but wonder what the original MULE 2.0 must have looked like. For people who doesn't understand what I'm talking about, here is our and the latest FSF version of Fcompare_buffer_substrings (the latter just just having been rewritten by Stallman): XEmacs: DEFUN ("compare-buffer-substrings", Fcompare_buffer_substrings, 6, 6, 0, /* Compare two substrings of two buffers; return result as number. the value is -N if first string is less after N-1 chars, +N if first string is greater after N-1 chars, or 0 if strings match. Each substring is represented as three arguments: BUFFER, START and END. That makes six args in all, three for each substring. The value of `case-fold-search' in the current buffer determines whether case is significant or ignored. */ (buffer1, start1, end1, buffer2, start2, end2)) { Bufpos begp1, endp1, begp2, endp2; REGISTER Charcount len1, len2, length, i; struct buffer *bp1, *bp2; Lisp_Object trt = ((!NILP (current_buffer->case_fold_search)) ? current_buffer->case_canon_table : Qnil); /* Find the first buffer and its substring. */ bp1 = decode_buffer (buffer1, 1); get_buffer_range_char (bp1, start1, end1, &begp1, &endp1, GB_ALLOW_NIL); /* Likewise for second substring. */ bp2 = decode_buffer (buffer2, 1); get_buffer_range_char (bp2, start2, end2, &begp2, &endp2, GB_ALLOW_NIL); len1 = endp1 - begp1; len2 = endp2 - begp2; length = len1; if (len2 < length) length = len2; for (i = 0; i < length; i++) { Emchar c1 = BUF_FETCH_CHAR (bp1, begp1 + i); Emchar c2 = BUF_FETCH_CHAR (bp2, begp2 + i); if (!NILP (trt)) { c1 = TRT_TABLE_OF (trt, c1); c2 = TRT_TABLE_OF (trt, c2); } if (c1 < c2) return make_int (- 1 - i); if (c1 > c2) return make_int (i + 1); } /* The strings match as far as they go. If one is shorter, that one is less. */ if (length < len1) return make_int (length + 1); else if (length < len2) return make_int (- length - 1); /* Same length too => they are equal. */ return Qzero; } The latest FSFmacs: DEFUN ("compare-buffer-substrings", Fcompare_buffer_substrings, Scompare_buffer_substrings, 6, 6, 0, "Compare two substrings of two buffers; return result as number.\n\ the value is -N if first string is less after N-1 chars,\n\ +N if first string is greater after N-1 chars, or 0 if strings match.\n\ Each substring is represented as three arguments: BUFFER, START and END.\n\ That makes six args in all, three for each substring.\n\n\ The value of `case-fold-search' in the current buffer\n\ determines whether case is significant or ignored.") (buffer1, start1, end1, buffer2, start2, end2) Lisp_Object buffer1, start1, end1, buffer2, start2, end2; { register int begp1, endp1, begp2, endp2, temp; register struct buffer *bp1, *bp2; register Lisp_Object *trt = (!NILP (current_buffer->case_fold_search) ? XCHAR_TABLE (current_buffer->case_canon_table)->contents : 0); int chars = 0; int i1, i2, i1_byte, i2_byte; /* Find the first buffer and its substring. */ if (NILP (buffer1)) bp1 = current_buffer; else { Lisp_Object buf1; buf1 = Fget_buffer (buffer1); if (NILP (buf1)) nsberror (buffer1); bp1 = XBUFFER (buf1); if (NILP (bp1->name)) error ("Selecting deleted buffer"); } if (NILP (start1)) begp1 = BUF_BEGV (bp1); else { CHECK_NUMBER_COERCE_MARKER (start1, 1); begp1 = XINT (start1); } if (NILP (end1)) endp1 = BUF_ZV (bp1); else { CHECK_NUMBER_COERCE_MARKER (end1, 2); endp1 = XINT (end1); } if (begp1 > endp1) temp = begp1, begp1 = endp1, endp1 = temp; if (!(BUF_BEGV (bp1) <= begp1 && begp1 <= endp1 && endp1 <= BUF_ZV (bp1))) args_out_of_range (start1, end1); /* Likewise for second substring. */ if (NILP (buffer2)) bp2 = current_buffer; else { Lisp_Object buf2; buf2 = Fget_buffer (buffer2); if (NILP (buf2)) nsberror (buffer2); bp2 = XBUFFER (buf2); if (NILP (bp2->name)) error ("Selecting deleted buffer"); } if (NILP (start2)) begp2 = BUF_BEGV (bp2); else { CHECK_NUMBER_COERCE_MARKER (start2, 4); begp2 = XINT (start2); } if (NILP (end2)) endp2 = BUF_ZV (bp2); else { CHECK_NUMBER_COERCE_MARKER (end2, 5); endp2 = XINT (end2); } if (begp2 > endp2) temp = begp2, begp2 = endp2, endp2 = temp; if (!(BUF_BEGV (bp2) <= begp2 && begp2 <= endp2 && endp2 <= BUF_ZV (bp2))) args_out_of_range (start2, end2); i1 = begp1; i2 = begp2; i1_byte = buf_charpos_to_bytepos (bp1, i1); i2_byte = buf_charpos_to_bytepos (bp2, i2); while (i1 < endp1 && i2 < endp2) { /* When we find a mismatch, we must compare the characters, not just the bytes. */ int c1, c2; if (! NILP (bp1->enable_multibyte_characters)) { c1 = BUF_FETCH_MULTIBYTE_CHAR (bp1, i1_byte); BUF_INC_POS (bp1, i1_byte); i1++; } else { c1 = BUF_FETCH_BYTE (bp1, i1); c1 = unibyte_char_to_multibyte (c1); i1++; } if (! NILP (bp2->enable_multibyte_characters)) { c2 = BUF_FETCH_MULTIBYTE_CHAR (bp2, i2_byte); BUF_INC_POS (bp2, i2_byte); i2++; } else { c2 = BUF_FETCH_BYTE (bp2, i2); c2 = unibyte_char_to_multibyte (c2); i2++; } if (trt) { c1 = XINT (trt[c1]); c2 = XINT (trt[c2]); } if (c1 < c2) return make_number (- 1 - chars); if (c1 > c2) return make_number (chars + 1); chars++; } /* The strings match as far as they go. If one is shorter, that one is less. */ if (chars < endp1 - begp1) return make_number (chars + 1); else if (chars < endp2 - begp2) return make_number (- chars - 1); /* Same length too => they are equal. */ return make_number (0); } 59 and 156 lines respectively, for *completely* equivalent functionality. So much for XEmacs being "large" and "bloated". I won't even comment the clarity of code. Just regard the beautiful code repetition between BUF_FETCH_BYTE and BUF_FETCH_MULTIBYTE_CHAR cases. And the original MULE was likely much *worse* than this. > The bare minimum that will be necessary for any Mule-ized function > whose value may end up being used by tools outside of XEmacs is > going to be that it be told how its value will be used, so that it > can choose an appropriate representation relative to which it will > compute the value. That's OK. Again, I definitely realize that Fmd5 must have internal file-coding built-in. > In the case of Fmd5, it should normally be possible to guess the > usage from properties of the source of the text, so the variable > could be used. On the other hand, for other functions it may rarely > be possible; if such cases are the majority, then for consistency of > the Mule interface we would want an argument, I think. How do you > see it? I don't know enough about Mule to be able to answer this authoritatively. Offhand, I think I prefer a set of variables set by the environment, and respected by the primitives such as `md5' and `save-buffer'. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- * Q: What is an experienced Emacs user? * A: A person who wishes that the terminal had pedals.

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