May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

[DANGER] Re: beta39-pre5 -- Developer's edition 26 years, 6 months

SL Baur

Be careful with this one until we get it fixed, or the bad patch backed out. With no X resources it infloops on start up beeping `wrong type argument integer, ?^S'.

1 participants
0 comments

Re: [bug] buffer-syntactic-context hosed by `(' at beginning of line 26 years, 6 months

Jan Vroonhof

Glynn Clements <glynn(a)sensei.co.uk> writes: > Hrvoje Niksic wrote: > > > Now go to the line beginning with `This program is distributed > > with...' and evaluate (buffer-syntactic-context). For me, it > > evaluates to nil, which is bogus because it should be `block-comment'. > > It evaluates to `block-comment' for me (CC-mode 5.22). Using 'xemacs -q -no-site-file' ? Jan

2 participants
1 comments

beta39-pre5 -- Developer's edition 26 years, 6 months

SL Baur

I've done a cvs commit on accumulated patches to beta39. There's a problem with initial frame size that has appeared in the last round of patches. Could someone please reexamine their patch and fix it? Thanks. -- MS Windows build fix for minimal tagbits, etc. from Kirill Katsnelson -- Fix initial frame display oddities from Kirill Katsnelson -- Fix cancelling directory creation prompt from Hrvoje Niksic -- cygwin build fixes from Andy Piper -- Restore oo-browser etags.c as ootags.c -- Socket connections for Windows from Kirill Katsnelson -- region limiting fixes from Hrvoje Niksic -- cleanup focus-follows-mouse handling from Greg Klanderman -- mswindows cursor support from Andy Piper -- elimination of bzero from Michael Sperber -- build fix from Jeff Miller -- xpm button fix from Andy Piper -- add optional `norecord' arg to select-window from Greg Klanderman -- regexp quote fix from Hrvoje Niksic -- early frame title update from Jan Vroonhof -- Make character 0240 display as space from Kyle Jones -- 0 argument printing fix from Hrvoje Niksic -- revert recent changes to etags.c -- dump clean up, removal of Lisp reader macros -- spelling fix from Jonathan Harris -- MS Windows build fix from Kirill Katsnelson -- sound fixes from Kyle Jones -- LDAP updates from Oscar Figueiredo -- Drag and drop update from Oliver Graf -- rename XEmacs internal realpath from Kyle Jones -- rangetab cleanup from Martin Buchholz -- etags fix -- miscellaneous bug fixes

1 participants
0 comments

XEmacs 20.4: vm.texi typo 26 years, 6 months

Michael Ernst

This patch fixes a typo in the VM manual. -Michael Ernst mernst(a)cs.washington.edu --- /tmp/gjb/xemacs-20.4/man/vm.texi Sat Feb 15 14:21:56 1997 +++ - Wed May 6 15:15:45 1998 ＠＠ -57,7 +57,7 ＠＠＠menu * Introduction:: Overview of the VM interface. -* Starting Up:: What happens when your start VM. +* Starting Up:: What happens when you start VM. * Selecting Messages:: How to select messages for reading. * Reading Messages:: Previewing and paging through a message. * Sending Messages:: How to send messages from within VM.

1 participants
0 comments

Re: [PATCH] efs-kerberos typo 26 years, 6 months

SL Baur

Raymond Toy <toy(a)rtp.ericsson.se> writes: > Olivier Galibert <galibert(a)pobox.com> writes: >> On Wed, May 06, 1998 at 11:39:36AM -0400, Raymond Toy wrote: >> > Should this have been sent to the patches mailing list? Are all >> > patches supposed to go there now? >> >> Yep. For Steve's sake, you should add a Changelog entry too, please. For everyone's sake. > Ok. I'll resubmit the patch and do it correctly this time. You will be submitting it via efs-bug in EFS, right? Michael Sperber, the EFS maintainer, has requested bug reports and patches to go through that route instead of to the XEmacs lists.

1 participants
0 comments

Re: emacs and guile (Re: SUGGESTION: gtk and xemacs) 26 years, 6 months

Adrian Aichner

The following message is a courtesy copy of an article that has been posted to comp.emacs,comp.emacs.xemacs as well. >>>>> "Jon" == Jon Drukman <jsd(a)hudsucker.gamespot.com> writes: Jon> (setq text-mode-hook '(lambda () (auto-fill-mode 1))) Jon> what is lambda going to mean to someone who just wants to get their Jon> buffers auto-filled? How about M-x describe-function RET lambda RET or M-x info-query RET lispref RET m lambda expressions RET Jon> far worse: what about something like this? Jon> (custom-set-faces Jon> '(font-lock-string-face ((t (:foreground "blue3"))) t) Jon> '(font-lock-doc-string-face ((t (:foreground "blue3"))) t) Jon> '(font-lock-variable-name-face ((t nil)) t) Jon> '(font-lock-keyword-face ((t (:foreground "brown"))) t) Jon> '(font-lock-type-face ((t (:foreground "brown"))) t) Jon> '(font-lock-other-type-face ((t (:foreground "brown"))) t) Jon> '(font-lock-comment-face ((t (:foreground "red"))) t)) The forms (custom-set-faces ...) and (custom-set-variables ...) are not meant to be editted by hand. They are udated via Options -> Customize -> ... When you click the Save button for any customized variable or faces. Perhaps a leading comment should written before these forms pointing this out to a user stumbling into these lisp forms. Regards, Adrian Jon> how the heck is anyone supposed to be able to read that, let alone Jon> REMEMBER it when asked how to change the colors? Jon> i don't have any answers, but i do believe you are underestimating Jon> the amount of work required to customize some common, trivial items. Jon> i've been using emacs for years so i have absorbed a baseline amount Jon> of elisp knowledge just through osmosis. pity the new user who just Jon> wants to get some work done! Jon> at this point i have given up on customizing emacs to do precisely what Jon> i want. i just keep reading the newsgroups in the hope that someone Jon> will post a snippet of elisp that i can steal and mangle enough to Jon> work for me. :) so far i've been lucky... -- Adrian Aichner Applications Engineer Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Straße 2 Fax +49/89/41861-217 D-81673 MÜNCHEN E-mail aichner(a)ecf.teradyne.com

1 participants
0 comments

Re: [FAILURE] XEmacs 21.0-beta38 on MkLinux 26 years, 6 months

Kaoru Fukui

I search three files(floatfns.c,math.h of glibc-961212-1f.src.rpm,math.h of glibc-2.0.6.tar.gz). Floatfns.c is no fail. Struct __exception in glibc-961212 is excanged to struct exception. Kaoru fukui k_fukui(a)highway.or.jp > From: "Stephen R. Anderson" <sra(a)bloch.ling.yale.edu> > > I enclose a copy of the most recent /usr/include/math.h, from > ftp://ftp.linuxppc.org/linuxppc/redhat/RPMS/ppc/glibc-devel-0.961212-1f.p... > > > #ifdef __USE_SVID > /* In SVID error handling, `matherr' is called with this description > of the exceptional condition. */ > struct __exception > { > int type; > char *name; > double arg1; > double arg2; > double retval; > }; > > extern int __matherr __P ((struct __exception *)); > extern int matherr __P ((struct __exception *)); ================== math.h in glibc-2.0.7 ================== #ifdef __USE_SVID /* In SVID error handling, `matherr' is called with this description of the exceptional condition. We have a problem when using C++ since `exception' is reserved in C++. */ #ifdef __cplusplus struct __exception #else struct exception #endif { int type; char *name; double arg1; double arg2; double retval; }; #ifdef __cplusplus extern int __matherr __P ((struct __exception *)); extern int matherr __P ((struct __exception *)); #else extern int __matherr __P ((struct exception *)); extern int matherr __P ((struct exception *)); #endif ================ floatfns.c in Xemacs ================ #if defined (HAVE_MATHERR) && !defined(__cplusplus) int matherr (struct exception *x) { Lisp_Object args; if (! in_float) /* Not called from emacs-lisp float routines; do the default thing. */ return 0; /* if (!strcmp (x->name, "pow")) x->name = "expt"; */ args = Fcons (build_string (x->name), Fcons (make_float (x->arg1), ((in_float == 2) ? Fcons (make_float (x->arg2), Qnil) : Qnil))); switch (x->type) { case DOMAIN: Fsignal (Qdomain_error, args); break; case SING: Fsignal (Qsingularity_error, args); break; case OVERFLOW: Fsignal (Qoverflow_error, args); break; case UNDERFLOW: Fsignal (Qunderflow_error, args); break; default: Fsignal (Qarith_error, args); break; } return 1; /* don't set errno or print a message */ } #endif /* HAVE_MATHERR */

1 participants
0 comments

Re: [FAILURE] XEmacs 21.0-beta38 on MkLinux 26 years, 6 months

Kaoru Fukui

I search three files(floatfns.c,math.h of glibc-961212-1f.src.rpm,math.h of glibc-2.0.6.tar.gz). Floatfns.c is no fail. Struct __exception in glibc-961212 is excanged to struct exception. Kaoru fukui k_fukui(a)highway.or.jp > From: "Stephen R. Anderson" <sra(a)bloch.ling.yale.edu> > > I enclose a copy of the most recent /usr/include/math.h, from > ftp://ftp.linuxppc.org/linuxppc/redhat/RPMS/ppc/glibc-devel-0.961212-1f.p... > > > #ifdef __USE_SVID > /* In SVID error handling, `matherr' is called with this description > of the exceptional condition. */ > struct __exception > { > int type; > char *name; > double arg1; > double arg2; > double retval; > }; > > extern int __matherr __P ((struct __exception *)); > extern int matherr __P ((struct __exception *)); ================== math.h in glibc-2.0.7 ================== #ifdef __USE_SVID /* In SVID error handling, `matherr' is called with this description of the exceptional condition. We have a problem when using C++ since `exception' is reserved in C++. */ #ifdef __cplusplus struct __exception #else struct exception #endif { int type; char *name; double arg1; double arg2; double retval; }; #ifdef __cplusplus extern int __matherr __P ((struct __exception *)); extern int matherr __P ((struct __exception *)); #else extern int __matherr __P ((struct exception *)); extern int matherr __P ((struct exception *)); #endif ================ floatfns.c in Xemacs ================ #if defined (HAVE_MATHERR) && !defined(__cplusplus) int matherr (struct exception *x) { Lisp_Object args; if (! in_float) /* Not called from emacs-lisp float routines; do the default thing. */ return 0; /* if (!strcmp (x->name, "pow")) x->name = "expt"; */ args = Fcons (build_string (x->name), Fcons (make_float (x->arg1), ((in_float == 2) ? Fcons (make_float (x->arg2), Qnil) : Qnil))); switch (x->type) { case DOMAIN: Fsignal (Qdomain_error, args); break; case SING: Fsignal (Qsingularity_error, args); break; case OVERFLOW: Fsignal (Qoverflow_error, args); break; case UNDERFLOW: Fsignal (Qunderflow_error, args); break; default: Fsignal (Qarith_error, args); break; } return 1; /* don't set errno or print a message */ } #endif /* HAVE_MATHERR */

1 participants
0 comments

[PATCH] Unified frame shakers 26 years, 6 months

Kirill M. Katsnelson

In this patch, I changed how XEmacs resizes its frame to keep its character geometry consistent. The readjustment is done only once upon frame redisplay, as Ben suggested couple of months ago. This means that frame does not shake any more upon loading options.el. I removed five trickiermost device methods which were responsible for adjusting the frame. Fset_frame_size does the job fine. The change withstood this test under both X and Windows. Editres also works as expected. (defun fiddle-with-specifier (spec &optional delta smin smax) (let* ((oldval (specifier-instance spec)) (newval (if (boolean-specifier-p spec) (if (oddp (random)) (oddp (random)) oldval) (min smax (max smin (+ oldval (random (* 2 delta)) (- delta))))))) (set-specifier spec newval))) (set-frame-size nil 100 35) (setq font-sentinel 0) (while t (fiddle-with-specifier scrollbar-width 8 0 40) (fiddle-with-specifier scrollbar-height 8 0 40) (fiddle-with-specifier default-toolbar-visible-p) (fiddle-with-specifier default-toolbar-height 16 24 100) (fiddle-with-specifier default-toolbar-border-width 4 0 40) ; Kick (if (zerop (random 17)) (set-frame-size nil 100 35)) ; Faces (when (and (> font-sentinel -3) (zerop (random 7))) (make-face-larger 'default) (decf font-sentinel)) (when (and (< font-sentinel 3) (zerop (random 7))) (make-face-smaller 'default) (incf font-sentinel)) (if (zerop (random 17)) (set-frame-size nil 100 35)) ; Toolbar position (when (zerop (random 11)) (set-default-toolbar-position (aref [left top right bottom] (random 4)))) (sit-for 0.1) (assert (= (frame-width) 100)) (assert (= (frame-height) 35))) Kirill 1998-05-06 Kirill M. Katsnelson <kkm(a)kis.ru> * frame.h (struct frame): Added char_{width,height} member variables and access macros Added size_slipped redisplay bit and mark/clear macros. * redisplay.c (redisplay_frame): Adjust frame size if size slipped bit is set. (redisplay_device): Call redisplay_frame if size slipped bit is set. * frame.c (adjust_frame_size): Redisplay beats frame back in shape with this. Added. (frame_size_slipped): Added. (internal_set_frame_size): Clear size slipped bit. (change_frame_size_1): Store real charsize into frame object. (vars_of_frame): Declared adjust-frame-function. * frame-msw.c (mswindows_update_frame_external_traits): Same change as for frame-x.c (mswindows_frame_size_fixed_p): Implemented the method. * frame-x.c (x_update_frame_external_traits): Do not call Fset_frame_size to adjust frame, redisplay will do. * faces.c (update_EmacsFrame): Mark frame as slipped when default font changes. * toolbar.c (compute_frame_toolbars_data): Removed obsoleted call to change_frame_size. Redisplay will fix it later. Removed toolbar_*_changed_in_frame specifier change handlers. (specifier_vars_of_toolbar): Calls to these routed to frame_size_slipped generic handler. * toolbar-x.c: Removed toolbar_*_changed_in_frame device methods. * scrollbar-x.c: Removed scrollbar_*_changed_in_frame device methods. * scrollbar.c: Removed scrollbar_*_changed_in_frame specifier change handlers. (specifier_vars_of_scrollbar): Calls to the above changed to frame_size_slipped generic handler. * device-x.c: Removed declaration of in_specifier_change_function. * EmacsFrame.c (EmacsFrameSetValues): Do not check in_specifier_change_function. * console.h (struct console_methods): Removed declarations for all <specifier>_changed_in_frame methods for toolbars and scrollbars. Added frame_size_fixed_p method.

1 participants
0 comments

Re: More package questions 26 years, 6 months

SL Baur

Olivier Galibert <galibert(a)pobox.com> writes: > On Wed, May 06, 1998 at 05:25:09PM +0200, Hrvoje Niksic wrote: >> Olivier Galibert <galibert(a)pobox.com> writes: >> > In *this* case what we have to fix is the dependency. We should have a >> > "dependency overrride" flag, but *not* set it by default. >> >> Or, maybe we should do what Debian does, which is distinguish between >> "suggesting" a package and "requiring" it. When package A requires >> package B, it means it will be useless without it. OTOH, when package >> A suggests package B, it means that it will run without it, but (say) >> with less features. > This would be nice, too. And does not preclude the flag existence, > which is a necessity (un-overridable package systems simply aren't > usable). Steve, can this "suggest/require" distinction fit nicely in > what you have ? I think so. Right now the dependencies are tuned _only_ for bytecompilation.

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