May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

[patch] [bug] src/eval.c: give Fcond Scheme-style `=>' syntax. 26 years, 7 months

Karl M. Hegbloom

I've given the `cond' special form the r{4,5}rs scheme-style `=>' syntax. It's working, when the test code is run interpreted, but not when run byte-compiled. Attached is the simple test code followed by my first C code patch to XEmacs. (not counting typos in docstrings or comments.) My question is: Should the byte compiler be compiling `cond' like that, since it's in C already? Wouldn't it run faster if it only translated things like the anonymous lambda, and left the rest for the C code to run? #include <nerdy/any_ideas.h> 1998-04-27 Karl M. Hegbloom <karlheg(a)inetarena.com> * eval.c (Fcond): Support scheme-style `=>' syntax.

3 participants
2 comments

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

Hrvoje Niksic

"Kirill M. Katsnelson" <kkm(a)kis.ru> writes: > (defcustom scrollbars-visible-p ;; added for the options menu - dverna > (> (specifier-instance scrollbar-width) 0) > "Whether the scrollbars are globally visible. This variable can be > customized through the options menu." > :group 'display > :type 'boolean > ;; This is really a hack: there should be a real specifier for this, in > ;; order to turn on/off the scrollbars without altering their size. > :set '(lambda (var val) > (if val > (progn > (set-specifier scrollbar-width 15) > (set-specifier scrollbar-height 15)) > (set-specifier scrollbar-width 0) > (set-specifier scrollbar-height 0)) > (setq scrollbars-visible-p val)) > ) BURN THIS! BURN THIS! BURN THIS! (sorry, Didier! please don't take this personally, but this defcustom simply cannot be allowed to stay. it must be implemented correctly or not at all.) > But the ideal solution is a separate specifier for scrollbar > visibility, as the comment suggests. I remeber that Hrvoje said that > in last October, but perhaps it was not the first time this' been > said... :) > > Btw, this specifier will not break any backward > compatibility. Phasing out a convention that zero size toolbar is no > toolbar may then take some time but is very harmless. With Steve's permission, I could try to implement it for 21.0... -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- A radioactive cat has eighteen half-lives.

2 participants
1 comments

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

Ben Wing

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. Also, do there exist forms save-selected-frame and with-selected-frame? If not, there should be. Also, focus-follows-mouse needs to be a console property instead of just a simple variable. 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. Greg Klanderman wrote: > OK, this should do it in terms of documentation and fixing C-x 5 o. > > greg > > >>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: > Hrvoje> > Hrvoje> greg(a)alphatech.com (Greg Klanderman) writes: > >> Are we agreed that with f-f-m true, C-x 5 o (other-frame) is the > >> *only* command which should warp focus. > Hrvoje> > Hrvoje> Yes. But this is still a major behavioral change which you should > Hrvoje> document. For instance, it may be worth noting (in the manual) that > Hrvoje> if you want `select-frame' to actually select the WM frame, you must > Hrvoje> bind focus-follows-mouse to nil. > Hrvoje> > Hrvoje> Other than the `C-x 5 o' problem, I must once again state that your > Hrvoje> patch does The Right Thing. For instance, > Hrvoje> (progn (select-frame (other-frame)) (insert "foo")) inserts "foo" in > Hrvoje> the other buffer's frame, which is correct, and then reselects this > Hrvoje> frame for focus. Kudos to you. :-) > > 1998-04-30 Greg Klanderman <greg(a)alphatech.com> > > * frame.el (other-frame): Work even when focus-follows-mouse is true. > > 1998-04-30 Greg Klanderman <greg(a)alphatech.com> > > * frame.c (Fselect_frame): update docstring to describe > focus-follows-mouse behavior. > > 1998-04-30 Greg Klanderman <greg(a)alphatech.com> > > * lispref/frames.texi (Input Focus): Document behavior of > select-frame wrt focus-follows-mouse. > > Index: etc/NEWS > =================================================================== > RCS file: /usr/CVSroot/XEmacs/xemacs-20/etc/NEWS,v > retrieving revision 1.48 > diff -u -r1.48 NEWS > --- NEWS 1998/04/24 21:33:58 1.48 > +++ NEWS 1998/05/01 08:41:08 > ＠＠ -33,6 +33,17 ＠＠ > * Changes in XEmacs 21.0 > ======================== > > +** When the variable focus-follows-mouse is non-nil, it is no longer > +possible for select-frame to permanently select a different frame. > +The frame selection is temporary and is reverted when the current > +command terminates, much like the buffer selected by `set-buffer'. > +In order to effect a permanent focus change in this case, bind > +focus-follows-mouse to nil, select the frame you want, and do a > +(sit-for 0) within the scope of the binding. The function > +other-frame (normally bound to C-x 5 o) is the only command provided > +which does not respect the setting of focus-follows-mouse, and *will* > +allow one to select a different frame even when set non-nil. > + > ** XEmacs has been unbundled into constituent installable packages. > See the file `etc/PACKAGES' in the distribution for a full > description. > Index: man/lispref/frames.texi > =================================================================== > RCS file: /usr/CVSroot/XEmacs/xemacs-20/man/lispref/frames.texi,v > retrieving revision 1.1.1.1 > diff -u -r1.1.1.1 frames.texi > --- frames.texi 1996/12/18 22:43:49 1.1.1.1 > +++ frames.texi 1998/05/01 08:41:09 > ＠＠ -677,6 +677,13 ＠＠ > ＠code{deselect-frame-hook} to be run, until the next time that XEmacs is > waiting for an event. > > +Also note that when the variable ＠code{focus-follows-mouse} is non-nil, > +the frame selection is temporary and is reverted when the current > +command terminates, much like the buffer selected by ＠code{set-buffer}. > +In order to effect a permanent focus change in this case, bind > +＠code{focus-follows-mouse} to nil, select the frame you want, and do a > +＠code{(sit-for 0)} within the scope of the binding. > + > ＠ignore (FSF Emacs) > XEmacs cooperates with the X server and the window managers by arranging > to select frames according to what the server and window manager ask > Index: lisp/frame.el > =================================================================== > RCS file: /usr/CVSroot/XEmacs/xemacs-20/lisp/frame.el,v > retrieving revision 1.11 > diff -u -r1.11 frame.el > --- frame.el 1998/04/23 02:07:52 1.11 > +++ frame.el 1998/05/01 08:41:10 > ＠＠ -516,10 +516,15 ＠＠ > (defun other-frame (arg) > "Select the ARG'th different visible frame, and raise it. > All frames are arranged in a cyclic order. > -This command selects the frame ARG steps away in that order. > +This command selects the frame ARG steps away in that order, > +regardless of the value of `focus-follows-mouse'. > A negative ARG moves in the opposite order." > (interactive "p") > - (let ((frame (selected-frame))) > + (let ((frame (selected-frame)) > + ;; Allow selecting another frame even when > + ;; focus-follows-mouse is true. > + (focus-policy focus-follows-mouse) > + (focus-follows-mouse nil)) > (while (> arg 0) > (setq frame (next-frame frame 'visible-nomini)) > (setq arg (1- arg))) > ＠＠ -528,6 +533,8 ＠＠ > (setq arg (1+ arg))) > (raise-frame frame) > (select-frame frame) > + (if focus-policy ;; this hack allows the focus change to be > + (sit-for 0)) ;; processed while focus-follows-mouse is nil. > ;this is a bad idea; you should in general never warp the > ;pointer unless the user asks for this. Furthermore, > ;our version of `set-mouse-position' takes a window, > Index: src/frame.c > =================================================================== > RCS file: /usr/CVSroot/XEmacs/xemacs-20/src/frame.c,v > retrieving revision 1.27 > diff -u -r1.27 frame.c > --- frame.c 1998/04/29 23:03:51 1.27 > +++ frame.c 1998/05/01 08:41:11 > ＠＠ -667,6 +667,13 ＠＠ > Note that this does not actually cause the window-system focus to > be set to this frame, or the select-frame-hook or deselect-frame-hook > to be run, until the next time that XEmacs is waiting for an event. > + > +Also note that when focus-follows-mouse is non-nil, the frame > +selection is temporary and is reverted when the current command > +terminates, much like the buffer selected by `set-buffer'. In order > +to effect a permanent focus change in this case, bind > +focus-follows-mouse to nil, select the frame you want, and do > +a (sit-for 0) within the scope of the binding. > */ > (frame)) > { -- This message composed using voice recognition software and foot pedals. (No keyboards were harmed while composing this message.)

1 participants
0 comments

Re: Process output problem? 26 years, 7 months

SL Baur

Ben Wing <ben(a)666.com> writes: > Under Unix, you can type xemacs -batch -l dunnet. Oh My Ghod! You can! Wow! I'm *still* learning things about XEmacs ... $ src/xemacs -batch -l dunnet Dead end You are at a dead end of a dirt road. The road goes to the east. In the distance you can see that it will eventually fork off. The trees here are very tall royal palms, and they are spaced equidistant from each other. There is a shovel here. > where I don't understand that. > look Dead end You are at a dead end of a dirt road. The road goes to the east. In the distance you can see that it will eventually fork off. The trees here are very tall royal palms, and they are spaced equidistant from each other. There is a shovel here. > take shovel Taken. >

1 participants
0 comments

package updates April 30, 1998 26 years, 7 months

SL Baur

I've updated the following packages on the FTP site. The updated package-get-base.el is in `package-get-base.el-21.0-b38-pre3'. xemacs-base-1.19: Shell.el -- don't use reader macro mail-lib-1.11: Add mail-rewrite-address-function hook eudc-1.05: Synch with EUDC-1.05 skk-1.06: De-ebolification textools-1.05: Add autoloads prog-modes-1.05: Add autoloads pcl-cvs-1.07: Add autoloads tm-1.06: Bug fix about nil encoding

1 participants
0 comments

Re: [Success] 21.0 "Repartida-pre3" XEmacs Lucid (beta38) on i586-pc-linux 26 years, 7 months

SL Baur

Kai Haberzettl <khaberz(a)privat.circular.de> writes: > No problems. Let the good times roll! Let's get the MS Windows problems fixed and get this baby out the door ...

1 participants
0 comments

RE: [Success] 21.0 "Repartida-pre2" XEmacs Lucid (beta38-pre2) o n i386-pc-cygwin32 26 years, 7 months

Ian MacKinnon

What I mean is that patch-xemacs.sh is looking for a patch of the name version+1 whereas what we have is pre-version+1 so it can't find it Once I have done a mv on the patch file patch works with no problems Should I try and patch patch-xemacs.sh so it will work for a patch named pre ? Or is there in fact a newer version ? --- Ian -----Original Message----- From: SL Baur [mailto:steve＠xemacs.org] Sent: Thursday, April 30, 1998 11:05 PM To: xemacs-beta(a)xemacs.org Subject: Re: [Success] 21.0 "Repartida-pre2" XEmacs Lucid (beta38-pre2) on i 386-pc-cygwin32 Ian MacKinnon <IMacKinnon(a)telia.co.uk> writes: > Does any one else have to hack the filename of the pre patches so > patch-xemacs will work ? Is this the case? The pre-patches are generated the same way the beta-n -> beta-n+1 patches are generated and should work with any reasonable version of patch. I know `cvs diff' causes heartache, weeping and gnashing of teeth with malformed filenames in patches, but this is the first I've heard of `cvs rdiff' having a problem. Index: xemacs-20.0/CHANGES-beta diff -u xemacs-20.0/CHANGES-beta:1.125 xemacs-20.0/CHANGES-beta:1.128 --- xemacs-20.0/CHANGES-beta:1.125 Sat Apr 25 21:07:11 1998 +++ xemacs-20.0/CHANGES-beta Wed Apr 29 16:03:42 1998 You have to specify `-p1' to patch to make the first part of the path go away, but that should be all.

1 participants
0 comments

[OK] 21.0 "Repartida-pre3" XEmacs Lucid (beta38) on i686-pc-linux 26 years, 7 months

Tetsuya HOYANO

Patched up from beta37 as directed works fine so far. ~$ gcc -v Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnulibc1/pgcc-2.91.24/specs gcc version pgcc-2.91.24 19980418 (gcc2 ss-980401 experimental) --HOYANO > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /home2/beta/xemacs-21.0-beta/Installation: > (Output from most recent run of ./configure)

1 participants
0 comments

Re: find-file FSFmacs synch? 26 years, 7 months

Oscar Figueiredo

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: Hrvoje> Should we copy this: Hrvoje> ** If you try to find a file that is not read-accessible, you now get Hrvoje> an error, rather than an empty buffer and a warning. I would be in favor. Oscar

1 participants
0 comments

[Success] 21.0 "Repartida-pre3" XEmacs Lucid (beta38) on i586-pc-linux 26 years, 7 months

Kai Haberzettl

No problems. > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/src/packages/xemacs/xemacs-21.0-b35/Installation: > (Output from most recent run of ./configure)

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