August 1998 - XEmacs-Beta - XEmacs Mailing List Archives

RE: Offtopic - Palm Pilot III 25 years, 10 months

Ian MacKinnon

I don't know how much they are, but I have a Palm II and think its brilliant, given that there is a linux port under way, when can we expect Xemacs ? I'm not sure whether you should but one today or not, there are fairly serious rumours of a new version Q498 --- Ian -----Original Message----- From: Andy Piper [SMTP:andyp＠parallax.co.uk] Sent: Tuesday, August 25, 1998 11:26 AM To: xemacs-beta(a)xemacs.org Subject: Offtopic - Palm Pilot III Can anyone tell me how much they cost in the US. They are about $400 here I'm wondering whether it would be cheaper to import one or get one when I'm next over. andy ------------------------------------------------------------------------ --- " .sigs are like your face - rarely seen by you and uglier than you think" Dr Andy Piper, Technical Architect, Parallax Solutions Ltd mail: andyp(a)parallax.co.uk web: www.parallax.co.uk/~andyp

1 participants
0 comments

Offtopic - Palm Pilot III 25 years, 10 months

Andy Piper

Can anyone tell me how much they cost in the US. They are about $400 here I'm wondering whether it would be cheaper to import one or get one when I'm next over. andy --------------------------------------------------------------------------- " .sigs are like your face - rarely seen by you and uglier than you think" Dr Andy Piper, Technical Architect, Parallax Solutions Ltd mail: andyp(a)parallax.co.uk web: www.parallax.co.uk/~andyp

1 participants
0 comments

Re: Macros: Scheme vs Common Lisp 25 years, 10 months

Hrvoje Niksic

Holger Schauer <schauer(a)coling.uni-freiburg.de> writes: > >>>>"MS" == Michael Sperber schrieb am 24 Aug 1998 13:50:54 +0200: > > MS> Ah, now I see what you meant. Unfortunately, this approach works > MS> only with self-quoting values for BAR: > > What Common Lisp are you using ? > > USER(8): (setq bar #'(lambda (x) x)) > #<Interpreted Function (unnamed) ＠ #x8cf772> > USER(9): (defmacro foo () bar) > FOO > USER(10): (let ((bar #'(lambda (x) (+ x 1)))) (funcall (foo) 23)) > 23 I may not understand all of the implications of the thread, but I'm getting the identical results from clisp: > (setq bar #'(lambda (x) x)) #<CLOSURE :LAMBDA (X) X> > (defmacro foo () bar) FOO > (let ((bar #'(lambda (x) (+ x 1)))) (funcall (foo) 23)) 23 -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- "A Real Programmer's code can awe with its fiendish brilliance, even as its crockishness appalls."

1 participants
0 comments

Re: X-error in get_mouse_position 25 years, 10 months

Jan Vroonhof

Ben Wing <ben(a)666.com> writes: > > > Why is the XSync solution not OK? Isn't the problem that we are > > > getting return outdated information because Xt has a backlog > > > processing events. > [Ben: This must be an Xlib bug. It is not synchromising correctly. > (incidently it cannot happen that another app like the window manager > deletes the window in between the two calls since the window > manager only ASKs an app to delete its window)] > > Martin seemed unhappy with the idea of adding yet another XSync > > because of the performance hit it causes. > > > [Ben: Put the Xsync at the end of the delete-frame code, that should > also cause other problems caused by this bug to go way] Brilliant solution! delete_frame is not performance crititical. Jan

1 participants
0 comments

Re: Macros: Scheme vs Common Lisp 25 years, 10 months

Michael Sperber

>>>>> "Holger" == Holger Schauer <schauer(a)coling.uni-freiburg.de> writes: >>>>> "MS" == Michael Sperber schrieb am 24 Aug 1998 13:50:54 +0200: MS> Ah, now I see what you meant. Unfortunately, this approach works MS> only with self-quoting values for BAR: Holger> What Common Lisp are you using ? CLISP, indeed. Holger> USER(8): (setq bar #'(lambda (x) x)) Holger> #<Interpreted Function (unnamed) ＠ #x8cf772> Holger> USER(9): (defmacro foo () bar) Holger> FOO Holger> USER(10): (let ((bar #'(lambda (x) (+ x 1)))) (funcall (foo) 23)) Holger> 23 Holger> This is Allegro Common Lisp 4.3. I think that it should be pretty Holger> close to ANSI Cl requirements. I bet CMUCL is somewhat more Holger> explanative than ACL (note however that CMUCL as of 17f does not Holger> implement ANSI CL, although 18 is said to move towards ANSI Holger> compliance). The fact that one Common Lisp allows this is irrelevant. The fact that the standard doesn't specify (or requires) an external representation for closures is. I believe CLISP is entirely correct in generating the error. Here's another unintended effect which exposes the hackishness of this, this time relying on the fact that symbols are not self-quoting: (setq bar (intern "Foo")) (defmacro foo () bar) (cons (foo) '()) => variable |Foo| has no value Again, the problem is that BAR is not referring to a binding---it's referring to the value of the binding. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: Sound [Quite Off topic] 25 years, 10 months

Sebastien Carpe

Rebecca Ore <rebecca.ore(a)op.net> writes: > I'd been playing with Enlightenment and it appears that the sound for > that mucked with my general sound configurations. XEmacs is okay now. Just want to "enlighten" you 'bout this. Enlightenment is using esd (Enl. sound daemon) - which is the also the Gnome sound daemon -. This is a centralised sound daemon. application are supposed to send sound to it, so that it can mix sound altogether. This is the good thing about this .... The bad thing is that it just keep /dev/audio for itself, preventing any other application to use it, while running (esd suppose all application will use esd for sound). The thing to do to free /dev/audio while esd is running (asid killing esd :) ) is to run 'esdctl standby' (and 'esdctl resume' to resume) for the moment... This is rather unconvenient at the moment, but may be an optionnal esd support in XEmacs would be fine for the future (and possibly help junking all the native sound support (each system do it another way) for a better uniform and abstract sound support -like esd is supposed to offer- ). -- Seb C. (mailto:scarpe＠atos-group.com) | Working for Atos at Lille, France *********************************************************************

1 participants
0 comments

Re: XEmacs 21.0-pre11 "Finnish Landrace" is released 25 years, 10 months

Adrian Aichner

>>>>> "Matthew" == Matthew O Persico <mpersico(a)erols.com> writes: Matthew> SL Baur wrote: Matthew> [snip] >> There's an experimental no-Mule SUMO tarball in the main FTP directory >> for those who need it (thanks Jan and Jason). >> Matthew> I've just go to ask: does SUMO stand for anything or is Matthew> it reflective of the tarball's size? Matthew> And, just for kicks, which file is pre-11? The latest I Matthew> see is b54. Hello Matthew, this is the version.sh of XEmacs 21.0-pre11 "Finnish Landrace" which technically isn't a beta release anymore. #!/bin/sh emacs_major_version=21 emacs_minor_version=0 emacs_beta_version= xemacs_codename="Finnish Landrace" infodock_major_version=4 infodock_minor_version=0 infodock_build_version=4 You get it all by fetching xemacs-21.0-b54.tar.gz I think the announcement should have made this clear. Without knowing all the history of xemacs-beta over the past few weeks or months it's impossible to know that pre11 === b54. HTH, Adrian Matthew> -- Matthew> #!/usr/bin/perl -- Matthew O. Persico Matthew> print "Just Another Perl Neophyte\n"; Matthew> ## Simplicity is a blessing when you're Matthew> ## supporting the program at 2AM -- 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

bug-report (core dump) 25 years, 10 months

Roeland Merks

Bug-report; whether you are using a prebuilt binary from ftp.xemacs.org or compiled XEmacs yourself for your system, etc. using precompiled binary, see below If at all possible, *please* try to obtain a C stack backtrace; it will help us immensely in determining what went wrong. To do this, locate the core file that was produced as a result of this crash (it's usually called `core' and is located in the directory in which you started XEmacs, or maybe in your home directory), and type gdb /Home/roel/bin/xemacs core then type `where' when the debugger prompt comes up. (If you don't have GDB on your system, you might have DBX, or XDB, or SDB. A similar procedure should work for all of these. Ask your system administrator if you need more help.) Lisp backtrace follows: # (condition-case ... . error) # (catch top-level ...) [1] IOT trap xemacs (core dumped) roel(cyber)[4]: #0 0x2a89f8 in kill () #1 0x2f02c in fatal_error_signal () #2 <signal handler called> #3 0x2af244 in abort () #4 0x338d4 in signal_1 () #5 0x33cf8 in Fsignal () #6 0x33d2c in signal_error () #7 0x34128 in error () #8 0x34c4 in xrealloc () #9 0x2a120 in Dynarr_resize () #10 0x99ce8 in add_emchar_rune () #11 0x9c498 in create_text_block () #12 0x99730 in generate_display_line () #13 0x9fde8 in regenerate_window () #14 0xa1764 in redisplay_window () #15 0xa1ae4 in redisplay_windows () #16 0xa1ae4 in redisplay_windows () #17 0xa1d4c in redisplay_frame () #18 0xa2054 in redisplay_device () #19 0xa2578 in redisplay_without_hooks () #20 0x40600 in Fnext_event () #21 0x191a0 in Fcommand_loop_1 () #22 0x18df4 in command_loop_1 () #23 0x334f0 in condition_case_1 () #24 0x18150 in command_loop_3 () #25 0x181a0 in command_loop_2 () #26 0x33120 in internal_catch () #27 0x185e4 in initial_command_loop () #28 0x30280 in main_1 () #29 0x30a88 in main () emacs-version: XEmacs 19.16 "Lille" [Lucid] (sparc-sunOS4.1.3) of Thu Oct 16 1997 on gold Please feel free to ask more details, (I will keep the core dump until you tell me to throw it away) Yours sincerely, Roeland Merks roel(a)cyber.c.u-tokyo.ac.jp

2 participants
1 comments

Re: X-error in get_mouse_position 25 years, 10 months

Gunnar Evermann

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > Maybe you could move the call > > f = x_any_window_to_frame (d, win); > if (!f) > return 0; > > to before the loop. Since frames are biggest structures we support, if > it is not a window of a frame there is no use iterating down anyway. Oh, good point! I'll try that -- I hadn't because I thought that the Window could be something strange, like a scrollbar or something, which doesn't correspond to an Emacs window... To answer my own question: I just had another look at frame-x.c and feel real stupid now, as I found 'is_valid_window()' which aparently does exeactly what I was looking for :-) Next time I will read the whole source before posting dumb questions. Sorry for the waste of bandwidth... I will send a new patch later this weekend. > Why is the XSync solution not OK? Isn't the problem that we are > getting return outdated information because Xt has a backlog > processing events. Yes, that's what I think. Martin seemed unhappy with the idea of adding yet another XSync because of the performance hit it causes. Gunnar

2 participants
1 comments

Re: local and networked X connections 25 years, 10 months

Hrvoje Niksic

Didier Verna <verna(a)inf.enst.fr> writes: > Chuck or Ben, could you explain to me exactly what represents a > console (as opposed to a device) under X ? I am not sure whether Ben reads thist list (Chuck does not), but I'll try to answer. If I understand correctly, console is the place where input is drawn from, which may encompass several devices. For example, if you use a multi-headed X display, you may have more than one device under just one console. However, in 99% cases, one console corresponds to one device. This is why I think the introduction of consoles was a mistake, because it totally muddled the otherwise clear and well-thought-out concept of devices. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- - When I die, shall I not be like Enkidu? - Like, no, man, you'll be, like, totally dead.

2 participants
1 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 August 1998