July 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: scheme - my opinion 26 years, 2 months

Adrian Aichner

>>>>> "sb" == SL Baur <steve(a)xemacs.org> writes: sb> If God had intended programmers to write constructs like: sb> (if <condition> sb> nil sb> <body>) Didn't you mean to say something like: (if (not <condition>) nil <body>) to make it equivalent to the following (when ...) form? sb> He would never have created the construct sb> (when <condition> sb> <body>) sb> which isn't native to Emacs lisp either ... -- Adrian Aichner Applications Engineer Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 D-81673 MUENCHEN E-mail aichner(a)ecf.teradyne.com

1 participants
0 comments

Questions about font property 26 years, 2 months

Takeshi Hagiwara 萩原威志

I have a question about font property handling in --with-mule configuration. I am using xemacs "21.0 \"Zhong Wei\" XEmacs Lucid" in following font configuration in my .emacs file. (set-face-font 'default '("-*-courier-medium-r-*--17-*-*-*-m-*-iso8859-1" "-*-*-medium-r-*--16-*-*-*-*-*-jisx0201.1976-*" "-*-*-medium-r-*--16-*-*-*-*-*-jisx0208.1983-*") 'global '(mule-fonts)) In this case, I noticed that `make-face-xxxx' changed only the first element of font property. This behavior is caused by `frob-face-property-1' in faces.el. In its function, while loop ends applying func to only first element. So, I have made following modifications. But it changes result type of the function from single font to list of font, so I must use `(setq result (car ...))' in `frob-face-property'. I don't know in which case `device-list' returns multiple devices, so I cannot modify more. Please make proper patch anyone? --- faces.el.org Fri Jul 10 18:03:22 1998 +++ faces.el Mon Jul 13 16:17:05 1998 ＠＠ -857,6 +857,7 ＠＠ new-result) ;; remove duplicates and nils from the obtained list of ;; instantiators. + (setq result (car result)) (mapcar (lambda (arg) (when (and arg (not (member arg new-result))) (setq new-result (cons arg new-result)))) ＠＠ -871,18 +872,20 ＠＠ (defun frob-face-property-1 (sp device inst-list func) (let (first-valid result) - (while (and inst-list (not result)) + (while inst-list ;;(and inst-list (not result)) (let* ((inst-pair (car inst-list)) (tag-set (car inst-pair)) (sp-inst (specifier-instance-from-inst-list - sp device (list inst-pair)))) + sp device (list inst-pair))) + result-tmp) (if sp-inst (progn (if (not first-valid) (setq first-valid inst-pair)) - (setq result (funcall func sp-inst device)) - (if result - (setq result (cons tag-set result)))))) + (setq result-tmp (funcall func sp-inst device)) + (if result-tmp + (setq result-tmp (cons tag-set result-tmp))) + (setq result (cons result-tmp result))))) (setq inst-list (cdr inst-list))) (or result first-valid))) -- Dept. of Information Engineering Faculty of Engineering Niigata University 8050 Ikarashi 2-nocho, Niigata 950-2181, Japan Tel(Fax): +81-25-262-6770 E-mail: hagiwara(a)ie.niigata-u.ac.jp

1 participants
0 comments

Re: scheme - my opinion 26 years, 2 months

SL Baur

Lars Magne Ingebrigtsen <larsi(a)gnus.org> writes: ... > Besides, Scheme doesn't have `when'. One can't not have `when'. That is a deficiency, but ... > Scheme is therefore unusable. > So *there*. :-) Lars, there are 459 usages of the `when' macro in the XEmacs core, and 2584 usages in external Lisp source. `when' is *never* going away regardless of whether we change the extension language. If God had intended programmers to write constructs like: (if <condition> nil <body>) He would never have created the construct (when <condition> <body>) which isn't native to Emacs lisp either ...

1 participants
0 comments

Re: KOI-8 finally 26 years, 2 months

SL Baur

Rebecca Ore <rebecca.ore(a)op.net> writes: > Oh, thank you, thank you. I couldn't get KOI-8 support before. > Relcom shows up in the right font Does the Russian TUTORIAL work for you?

3 participants
2 comments

Re: scheme - my opinion 26 years, 2 months

Lars Magne Ingebrigtsen

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > 4. Where the semantics of common constructs differ among elisp, > Common Lisp, and Scheme, how hard is it going to be for casual elisp > programmers to make the switchover? How hard is it going to be for > core developers and Lisp implementors to make the switchover? At a guess, I would think that Emacs Lispy people would (in general) feel more comfortable switching over to Common Lisp than to Scheme. There are many subtle (and not so subtle) differences between Emacs Lisp and CL, but I'd think that many elisp people have gotten used to having those handy functions and macros that cl.el provides. Anyway. Few would argue that Scheme isn't more ideologically pure, but I dislike cleanliness. Common Lisp is a great, towering beast, but you don't have to be familiar with even a fraction of it to get lots of mileage out of it. And as you learn more, you find that it's basically all there. The problem with Scheme is that's there's generally nothing there, so you have to write all the code yourself, which means that you get a gazillion little functions that work their way into the code base, all functions with their own little peculiarites, which (in the end) means that Scheme turns out to be even bigger than Common Lisp. (How big is Guile now?) With Common Lisp one gets a language environment that is reasonably standard -- you can expect books like CLtL2, commercial environments like Allegro, free environments like CLISP, and (oh, joy of joys) an Emacs that one would know how to use if one was familiar with any of the others. Besides, Scheme doesn't have `when'. One can't not have `when'. Scheme is therefore unusable. So *there*. -- (domestic pets only, the antidote for overdose, milk.) larsi(a)ifi.uio.no * Lars Magne Ingebrigtsen

2 participants
1 comments

[bug?] `pop-to-buffer' selection 26 years, 2 months

Jens-Ulrik Petersen

[I am leaving for a month's holiday on Wednesday and I am unsubscribed from xemacs-beta already: so CC's of replies would be appreciated] I feel this is a bug, but I'm not sure: it is certainly different from the behaviour of Emacs 20. If I'm in the middle of some buffer and load the code ---- Start of included text -----------------------8<--- cut here ------------- (pop-to-buffer (current-buffer) t (make-frame)) (end-of-buffer) ---- End of included text -------------------------8<--- and here ------------- it results in point in the window in the old frame going to the end of the buffer (actually I'm not sure it went all the way to the end under a tty!), and point staying put in the window in the new frame. I would expect point to move in the new frame not the old one. I have a feeling I have reported this before... -- Jens-Ulrik Holger Petersen <http://www.kurims.kyoto-u.ac.jp/~petersen/> Research Institute for Mathematical Sciences, Kyoto University

1 participants
0 comments

scheme - my opinion 26 years, 2 months

Martin Buchholz

scheme is an interesting language, but ... Scheme has been designed for programming language research, rather than practical use. It has such a history of minimalism that all scheme implementations had to provide extensions to be useful. It still is missing many things. For example, my beloved (when ...) is missing (from the standard). Hashtables are missing. (call-with-current-continuation) is a very interesting function, but one cannot expect ordinary humans to understand it. It is only a tool for system implementors. Continuations are gotos into the middle of another function, one that may already have returned! The scheme community seems to be in a downturn. From casual visits to the scheme repository, there seems to be little progress in implementations or standardization. However, there is hope for guile, which has been adopted by gimp, and has active development. Caveat: I have never done programming language research. Martin

2 participants
1 comments

resource->mswindows-resource Try 2 (was Re: Somebody needs to test this) 26 years, 2 months

SL Baur

Remek Trzaska <remek(a)npac.syr.edu> writes: > Bad mojo ;-( > I've got no idea what is going on here, I just patched and compiled ;-) O.K. Ben has told me what went wrong, apparently the renaming _was_ a little more complicated than just renaming a handful of variables. Let's try this again. Reverse the previous patch, this is off a virgin 21.0 "Zhong Wei". 1998-07-12 SL Baur <steve(a)altair.xemacs.org> * general.c (syms_of_general): Add defsymbol for Qresource. * glyphs-msw.c (vars_of_glyphs_mswindows): Rename Qresource to Qmswindows_resource. (TopLevel): Rename 'resource image format to 'mswindows_resource. (mswindows_resource_validate): Rename. (mswindows_resource_normalize): Rename. (mswindows_resource_possible_dest_types): Rename. (mswindows_resource_instantiate): Rename. (image_instantiator_format_create_glyphs_mswindows): Replace `resource' with `mswindows.resource'. 1998-07-12 SL Baur <steve(a)altair.xemacs.org> * msw-mouse.el: Global change resource -> mswindows-resource. Index: src/general.c =================================================================== RCS file: /usr/local/xemacs/xemacs-20.0/src/general.c,v retrieving revision 1.13 diff -u -r1.13 general.c --- src/general.c 1998/05/24 05:40:43 1.13 +++ src/general.c 1998/07/12 23:47:13 ＠＠ -298,6 +298,7 ＠＠ defsymbol (&Qrassoc, "rassoc"); defsymbol (&Qrassq, "rassq"); defsymbol (&Qrequire, "require"); + defsymbol (&Qresource, "resource"); defsymbol (&Qreturn, "return"); defsymbol (&Qreverse, "reverse"); defsymbol (&Qright, "right"); Index: src/glyphs-msw.c =================================================================== RCS file: /usr/local/xemacs/xemacs-20.0/src/glyphs-msw.c,v retrieving revision 1.21 diff -u -r1.21 glyphs-msw.c --- src/glyphs-msw.c 1998/07/10 02:49:11 1.21 +++ src/glyphs-msw.c 1998/07/12 23:42:45 ＠＠ -52,8 +52,9 ＠＠ Lisp_Object Vmswindows_bitmap_file_path; static COLORREF transparent_color = RGB (1,1,1); -DEFINE_IMAGE_INSTANTIATOR_FORMAT (resource); +DEFINE_IMAGE_INSTANTIATOR_FORMAT (mswindows_resource); Lisp_Object Q_resource_type, Q_resource_id; +Lisp_Object Qmswindows_resource; static void mswindows_initialize_dibitmap_image_instance (struct Lisp_Image_Instance *ii, ＠＠ -940,7 +941,7 ＠＠ **********************************************************************/ static void -resource_validate (Lisp_Object instantiator) +mswindows_resource_validate (Lisp_Object instantiator) { if ((NILP (find_keyword_in_vector (instantiator, Q_file)) && ＠＠ -952,7 +953,7 ＠＠ } static Lisp_Object -resource_normalize (Lisp_Object inst, Lisp_Object console_type) +mswindows_resource_normalize (Lisp_Object inst, Lisp_Object console_type) { /* This function can call lisp */ Lisp_Object file = Qnil; ＠＠ -987,7 +988,7 ＠＠ } static int -resource_possible_dest_types (void) +mswindows_resource_possible_dest_types (void) { return IMAGE_POINTER_MASK | IMAGE_COLOR_PIXMAP_MASK; } ＠＠ -1108,7 +1109,7 ＠＠ } static void -resource_instantiate (Lisp_Object image_instance, Lisp_Object instantiator, +mswindows_resource_instantiate (Lisp_Object image_instance, Lisp_Object instantiator, Lisp_Object pointer_fg, Lisp_Object pointer_bg, int dest_mask, Lisp_Object domain) { ＠＠ -1960,24 +1961,25 ＠＠ IIFORMAT_VALID_KEYWORD (bmp, Q_data, check_valid_string); IIFORMAT_VALID_KEYWORD (bmp, Q_file, check_valid_string); - INITIALIZE_IMAGE_INSTANTIATOR_FORMAT (resource, "resource"); + INITIALIZE_IMAGE_INSTANTIATOR_FORMAT (mswindows_resource, + "mswindows-resource"); - IIFORMAT_HAS_METHOD (resource, validate); - IIFORMAT_HAS_METHOD (resource, normalize); - IIFORMAT_HAS_METHOD (resource, possible_dest_types); - IIFORMAT_HAS_METHOD (resource, instantiate); + IIFORMAT_HAS_METHOD (mswindows_resource, validate); + IIFORMAT_HAS_METHOD (mswindows_resource, normalize); + IIFORMAT_HAS_METHOD (mswindows_resource, possible_dest_types); + IIFORMAT_HAS_METHOD (mswindows_resource, instantiate); - IIFORMAT_VALID_KEYWORD (resource, Q_resource_type, + IIFORMAT_VALID_KEYWORD (mswindows_resource, Q_resource_type, check_valid_resource_symbol); - IIFORMAT_VALID_KEYWORD (resource, Q_resource_id, check_valid_resource_id); - IIFORMAT_VALID_KEYWORD (resource, Q_file, check_valid_string); + IIFORMAT_VALID_KEYWORD (mswindows_resource, Q_resource_id, check_valid_resource_id); + IIFORMAT_VALID_KEYWORD (mswindows_resource, Q_file, check_valid_string); } void vars_of_glyphs_mswindows (void) { Fprovide (Qbmp); - Fprovide (Qresource); + Fprovide (Qmswindows_resource); DEFVAR_LISP ("mswindows-bitmap-file-path", &Vmswindows_bitmap_file_path /* A list of the directories in which mswindows bitmap files may be found. This is used by the `make-image-instance' function. Index: lisp/msw-mouse.el =================================================================== RCS file: /usr/local/xemacs/xemacs-20.0/lisp/msw-mouse.el,v retrieving revision 1.3 diff -u -r1.3 msw-mouse.el --- lisp/msw-mouse.el 1998/06/13 04:28:02 1.3 +++ lisp/msw-mouse.el 1998/07/12 23:49:06 ＠＠ -31,18 +31,18 ＠＠ ;;; Code: (set-glyph-image text-pointer-glyph - [resource :resource-type cursor :resource-id "Ibeam"]) + [mswindows-resource :resource-type cursor :resource-id "Ibeam"]) (set-glyph-image nontext-pointer-glyph - [resource :resource-type cursor :resource-id "Normal"]) + [mswindows-resource :resource-type cursor :resource-id "Normal"]) (set-glyph-image selection-pointer-glyph - [resource :resource-type cursor :resource-id "Normal"]) + [mswindows-resource :resource-type cursor :resource-id "Normal"]) (set-glyph-image modeline-pointer-glyph - [resource :resource-type cursor :resource-id "SizeNS"]) + [mswindows-resource :resource-type cursor :resource-id "SizeNS"]) (set-glyph-image divider-pointer-glyph - [resource :resource-type cursor :resource-id "SizeWE"]) + [mswindows-resource :resource-type cursor :resource-id "SizeWE"]) (set-glyph-image busy-pointer-glyph - [resource :resource-type cursor :resource-id "Wait"]) + [mswindows-resource :resource-type cursor :resource-id "Wait"]) (set-glyph-image gc-pointer-glyph - [resource :resource-type cursor :resource-id "Wait"]) + [mswindows-resource :resource-type cursor :resource-id "Wait"]) ;;; msw-mouse.el ends here

2 participants
1 comments

[Success] XEmacs 21.0-b48/pre5 "Zhong Wei" on Linux 26 years, 2 months

Kazuyoshi Furutaka

[i686-GNU-linux] Source : patched up from 21.0 beta47 Patch : patch 2.4 Make : GNU Make version 3.76.1 CC : pgcc-2.90.27 980315 (egcs-1.0.2 release) OS : Linux 2.0.34 (RedHat 5.0) X : X11R6.3 (Accelerated-X ver.4.1 w/ XFree86 3.3.1) gdb : GDB 4.16 [alpha-GNU-linux] Source : patched up from 21.0 beta47 Patch : Patch version 2.1 Make : GNU Make version 3.75 CC : egcs-2.90.29 980515 (egcs-1.0.3 release) OS : Linux 2.1.108 (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: Somebody needs to test this 26 years, 2 months

SL Baur

Remek Trzaska <remek(a)npac.syr.edu> writes: > Bad mojo ;-( > I've got no idea what is going on here, I just patched and compiled ;-) O.K. Thanks for trying. I give up.

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