August 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: X-error in get_mouse_position 26 years, 3 months

Gunnar Evermann

Peter Ware <ware(a)cis.ohio-state.edu> writes: Hi Pete, > Gunnar Evermann <Gunnar.Evermann(a)nats.informatik.uni-hamburg.de> writes: > > > 1) call XQueryPointer to find out over which Window (if any) the > > pointer currently is. ('child_window') > The race condition is here. There is _no_ general purpose way you can > avoid it in an application -- potentially any other application can > delete the window between the time you do the query pointer and then > ask for the translate coordinates. What do you mean "other application"? I certainly hope that no other app kills my windows, or is that really possible? > > 2) call XTranslateCoordinates() with this Window as the destination > > window. 'If the coordinates are contained in a mapped child of > > dest_w, that child is returned to child_window.' (quote from man > > page) > To get around the problem, you (mentally) acknowledge that there is no > way you can avoid the problem in your application. Instead you OK, I can do that. > install an error handler that says -- "Oh, a bad window error, I'll > ignore that". Do the translate coordinates, uninstall the error > handler, and check if the error handler indicated an error. I'd be > surprised if XEmacs didn't have something to do this automatically. Oh, it does! That would be expect_x_error() and x_error_occurred_p() in device-x.c. The only drawback is that they call XSync(), which started this whole thread :-( Maybe we should just accept this damned X-errors... ;-( Gunnar -- Gunnar Evermann Natural Language Systems Group, University of Hamburg EMail: Gunnar.Evermann(a)nats.informatik.uni-hamburg.de

1 participants
0 comments

Re: Macros: Scheme vs Common Lisp 26 years, 3 months

Clemens Heitzinger

sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: > Clemens> Where do I need explicit annotations? At definition time, I > Clemens> say which hygienic variables I want. This is an explicit > Clemens> annotation. > > And you have to write an unquote before every use. This means you > have annotations everywhere. Well, for me the usage of unquote in my examples was quite intuitive, but I understand that other people may feel differently about this. Actually, we have three definition and use times: (1) Definition of define-hygienic-macro (2) Use of define-hygienic-macro ... Definition of foo2 (3) Use of foo2 It is (2) which you complained about. In (3), the actual "use" time, define-hygienic-macro works transparently. > Clemens> On the other hand, I don't think that in Scheme you can say > Clemens> you want this and that variable *not* to be hygienic. > > No, but (to quote Craig in this discussion :-}) why would you want > this? One example is LOOP-FINISH. From the HyperSpec: ---------------------------------------------------------------------- The loop-finish macro can be used lexically within an extended loop form to terminate that form normally. That is, it transfers control to the loop epilogue of the lexically innermost extended loop form. This permits execution of any finally clause (for effect) and the return of any accumulated result. Examples: ;; Terminate the loop, but return the accumulated count. (loop for i in '(1 2 3 stop-here 4 5 6) when (symbolp i) do (loop-finish) count i) => 3 ---------------------------------------------------------------------- This is defined in the CL standard and I find it quite useful. > Clemens> In CL you can have both behaviours, in Scheme only one. > > As I explained, in CL you only have the non-hygienic option. You can > hack around it, but it's still not going to do the right thing in all > cases. Can you give an example where with-hygienic-variables fails? What is "the right thing"? Yours, -- Clemens Heitzinger Student der Techn. Mathematik, Technische Universität Wien, Österreich Vienna University of Technology, Austria

1 participants
0 comments

Re: X-error in get_mouse_position 26 years, 3 months

Pete Ware

Gunnar Evermann <Gunnar.Evermann(a)nats.informatik.uni-hamburg.de> writes: > 1) call XQueryPointer to find out over which Window (if any) the > pointer currently is. ('child_window') The race condition is here. There is _no_ general purpose way you can avoid it in an application -- potentially any other application can delete the window between the time you do the query pointer and then ask for the translate coordinates. > 2) call XTranslateCoordinates() with this Window as the destination > window. 'If the coordinates are contained in a mapped child of > dest_w, that child is returned to child_window.' (quote from man > page) To get around the problem, you (mentally) acknowledge that there is no way you can avoid the problem in your application. Instead you install an error handler that says -- "Oh, a bad window error, I'll ignore that". Do the translate coordinates, uninstall the error handler, and check if the error handler indicated an error. I'd be surprised if XEmacs didn't have something to do this automatically. --pete

1 participants
0 comments

Re: X-error in get_mouse_position 26 years, 3 months

Jan Vroonhof

Gunnar Evermann <Gunnar.Evermann(a)nats.informatik.uni-hamburg.de> writes: > > 1) call XQueryPointer to find out over which Window (if any) the > pointer currently is. ('child_window') This call gives the root window as the destination window doesn't it? Maybe you should loop over all active frames and call XQueryPointer with the frames main window as the argument to XQueryPointer. Of course this calls XQueryPointer for each frame, I have no idea how expensive this is. At least you always get a child window in a live frame then. Jan

1 participants
0 comments

YASBO (Yet Another ScrollBar Oddity) 26 years, 3 months

Didier Verna

xemacs -vanilla & C-x 5 2 C-h t (for example) In the tutorial frame, grab the scrollbar, move it down to a random place, and release it *with the pointer in the same frame*. Now if you move from this frame to the other you'll see the scrollbar move and/or resize itself. This does not happen if you use the scrollbar arrows, or if you move the pointer to a window that doesn't belong to XEmacs. You really have to leave this window and enter another window of the same XEmacs.

1 participants
0 comments

Re: sound-load-alist references nonexistent files 26 years, 3 months

Adrian Aichner

>>>>> "giacomo" == giacomo boffi <boffi(a)rachele.stru.polimi.it> writes: Hi Giacomo! Have you installed the appropriate sound package? (sounds-au (standards-version 1.0 version "1.02" author-version "21.0" date "1998-06-30" build-date "1998-07-09" maintainer "XEmacs Development Team <xemacs-beta(a)xemacs.org>" distribution stable priority high category "libs" dump nil description "XEmacs Sun sound files." filename "sounds-au-1.02-pkg.tar.gz" md5sum "061ab67267c7cdfe37472141130d19ff" size 125736 provides () requires () type regular )) (sounds-wav (standards-version 1.0 version "1.02" author-version "21.0" date "1998-06-30" build-date "1998-07-09" maintainer "XEmacs Development Team <xemacs-beta(a)xemacs.org>" distribution stable priority high category "libs" dump nil description "XEmacs Microsoft sound files." filename "sounds-wav-1.02-pkg.tar.gz" md5sum "c970808088c408bfd780dc8466a848b3" size 148621 provides () requires () type regular )) See also my recent mail to xemacs-patches to enable sound in sample.emacs for mswindows. HTH, Adrian giacomo> (insert (pp sound-load-alist)) ((load-sound-file giacomo> "drum-beep" 'drum) (load-sound-file "quiet-beep" 'quiet) giacomo> (load-sound-file "bass-snap" 'bass 80) (load-sound-file giacomo> "whip" 'whip 70) (load-sound-file "cuckoo" 'cuckoo) giacomo> (load-sound-file "yeep" 'yeep) (load-sound-file "hype" giacomo> 'hype 100)) giacomo> most of these files are not in default-sound-directory, giacomo> i.e., /usr/local/lib/xemacs-21.2-b1/packages/etc/sounds/ -- 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

2 participants
1 comments

Re: source-directory is no more 26 years, 3 months

Adrian Aichner

acs> I see that starting with b54, the variable source-directory acs> has been removed. I used to use it to find the origin of the acs> XEmacs source tree, more specifically, the place I could find acs> the TAGS file. I found this generally useful when I was acs> browsing either my own customizations or the XEmacs source. acs> What follows is how I used to do this; I'm sure there's acs> another way to do this - can anyone offer any suggestions? Hello Vin, this should work: (require 'config) (setq xemacs-source-directory (gethash 'blddir (config-value-hash-table))) (setq tag-table-alist '(("\\.emacs$" . xemacs-source-directory) ("/lisp" . xemacs-source-directory) ((progn (condition-case nil (or (string-match xemacs-source-directory (buffer-file-name)) nil) (error nil))) . xemacs-source-directory))) Good Luck, Adrian acs> Thanks in advance, vin -- 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

Re: source-directory is no more 26 years, 3 months

Didier Verna

Vin Shelton <acs(a)alumni.princeton.edu> writes: > I see that starting with b54, the variable source-directory has been > removed. It's there in XEmacs 21.2. Are you sure ?

1 participants
0 comments

Re: Macros: Scheme vs Common Lisp 26 years, 3 months

Michael Sperber

>>>>> "Clemens" == Clemens Heitzinger <cheitzin(a)rainbow.studorg.tuwien.ac.at> writes: Clemens> sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: >> >> Hygiene, however, means that variables in macros obey the same scoping >> >> rules as the rest of the language. WITH-HYGIENIC-VARIABLES gives you >> >> no help whatsoever referring to lexical bindings of the macro. CL >> Clemens> What help do you mean? The help hygienic macros give you: an identifier always refers to its lexically enclosing binding. >> >> >> macros are not hygienic, period. >> Clemens> Nobody claimed that. I wanted to make the point that it is quite easy Clemens> to define hygienic macros in CL. Huh? Re-read your sentence, please. >> And I made the point that what you're talking about is not hygiene. >> You still need explicit annotations to prevent variable capture, at >> definitions *and* uses. This is tedious and error-prone. You're >> doing nothing to respect the binding rules of the underlying language. Clemens> (I don't understand your last sentence.) What you're doing is renaming variables so that they are unique. This means that you avoid name clashes with other names. This still doesn't mean an identifier in a macro has the same semantics as everywhere else. It merely means that you simulate the semantics in some cases. You don't in others. Holger and I have exchanged examples in this very thread. Clemens> Where do I need explicit annotations? At definition time, I Clemens> say which hygienic variables I want. This is an explicit Clemens> annotation. And you have to write an unquote before every use. This means you have annotations everywhere. Clemens> On the other hand, I don't think that in Scheme you can say Clemens> you want this and that variable *not* to be hygienic. No, but (to quote Craig in this discussion :-}) why would you want this? Kidding aside, the real peeve may be with the limitations a pattern language imposes upon you. However, I've so far always found a way to make do with it. Clemens> In CL you can have both behaviours, in Scheme only one. As I explained, in CL you only have the non-hygienic option. You can hack around it, but it's still not going to do the right thing in all cases. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: initial frame display problem with beta54 on NT 26 years, 3 months

Adrian Aichner

>>>>> "John" == John Morey <jmorey(a)tbi.com> writes: Hello John, John> I did a native build of beta54 on NT-4.0. I sometimes have John> a display problem with the toolbar in the initial frame. It John> is easy for me to reproduce because my initial XEmacs frames John> always come up in the same place. How to reproduce: My XEmacs migrates SouthEast on each new invocation. I put (print (current-frame-configuration)) at the end of my .emacs. Here is what I get for sucessive invocations on a 800x600 display: (frame-configuration (#<mswindows-frame "emacs" 0xb55> (name "emacs" height 40 width 91 minibuffer t left 0 top 0 custom-properties (type mswindows class color background light) background-mode light) #<window-configuration 0x174b>)) (frame-configuration (#<mswindows-frame "emacs" 0xb55> (name "emacs" height 40 width 91 minibuffer t left 44 top 44 custom-properties (type mswindows class color background light) background-mode light) #<window-configuration 0x174a>)) (frame-configuration (#<mswindows-frame "emacs" 0xb55> (name "emacs" height 40 width 91 minibuffer t left 88 top 88 custom-properties (type mswindows class color background light) background-mode light) #<window-configuration 0x174b>)) (frame-configuration (#<mswindows-frame "emacs" 0xb55> (name "emacs" height 40 width 91 minibuffer t left 132 top 132 custom-properties (type mswindows class color background light) background-mode light) #<window-configuration 0x174a>)) (frame-configuration (#<mswindows-frame "emacs" 0xb55> (name "emacs" height 40 width 91 minibuffer t left 22 top 22 custom-properties (type mswindows class color background light) background-mode light) #<window-configuration 0x174a>)) John> 1) start xemacs 2) start the task manager 3) set the John> task manager to "always on top" 4) move the task manager John> window so that the upper left hand corner covers the text John> "Print" in the toolbar print button. Resize the task John> manager window to the right so that it extends off the edge John> of the XEmacs frame. 5) kill the current xemacs and restart John> 6) most of the toolbar area on the left will display what John> ever is behind it on the desktop and ther will be about a John> button and one half ("open" and 1/2 of "dired") displayed on John> the right hand side of the toolbar. I was not able to reproduce this. How do you start XEmacs? What command-line args do you use? Best, Adrian John> -- John Morey -- 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

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