Mercurial > hg > xemacs-beta
view tests/Dnd/README @ 5264:0d43872986b6
Change (apply 'nconc (mapcar ...)) to (mapcan ...); warn about first form.
lisp/ChangeLog addition:
2010-09-16 Aidan Kehoe <kehoea@parhasard.net>
* byte-optimize.el (byte-optimize-apply): Transform (apply 'nconc
(mapcar ...)) to (mapcan ...); warn about use of the first idiom.
* update-elc.el (do-autoload-commands):
* packages.el (packages-find-package-library-path):
* frame.el (frame-list):
* extents.el (extent-descendants):
* etags.el (buffer-tag-table-files):
* dumped-lisp.el (preloaded-file-list):
* device.el (device-list):
* bytecomp-runtime.el (proclaim-inline, proclaim-notinline)
Use #'mapcan, not (apply #'nconc (mapcar ...) in all these files.
* bytecomp-runtime.el (eval-when-compile, eval-and-compile):
In passing, mention that these macros also evaluate the body when
interpreted.
author | Aidan Kehoe <kehoea@parhasard.net> |
---|---|
date | Thu, 16 Sep 2010 13:51:49 +0100 |
parents | bc4f2511bbea |
children |
line wrap: on
line source
* Sun May 3 1998 Oliver Graf <ograf@fga.de> This path contains test code for the new XEmacs Drag'n'Drop code. To test the code do the following: 1) call 'bash droptest.sh' to create the test files in /tmp 2) load and eval droptest.el in XEmacs 3) Try to do some internal DnD by using the sources and targets in the new buffer 4) Do some external DnD: 4a) CDE: use dtfile and dtpad 4b) MSWindows: well, explorer should do. But only file data should work, and I don't know if the test already handles this. The misc-user-event now also responds as a button-x-event to the event-* query functions. The function of a drag is called dragdrop-drop-dispatch as you can see in droptest.el. From within the function you can access the actual misc-user-event through the current-mouse-event variable. Short description of the object part of a drop misc-user-event: ( TYPE . DATA ) TYPE is either the symbol dragdrop_MIME or the symbol dragdrop_URL DATA is a list of URL strings if TYPE is dragdrop_URL if TYPE is dragdrop_MIME DATA is either a string which contains the MIME data, or it is a list of ( CONTENT-TYPE CONTENT-ENCODING MIME-DATA ) CONTENT-TYPE is encoded for tm-view (list, first element type, rest key.value conses) CONTENT-ENCODING is a string MIME-DATA is a string CONTENT-TYPE and -ENCODING can be directly supplied to mime/viewer-mode.