Fix some bugs in load-history construction, built-in symbol file names. lib-src/ChangeLog addition: 2008-12-27 Aidan Kehoe <kehoea@parhasard.net> * make-docfile.c (main): Allow more than one -d argument, followed by a directory to change to. (put_filename): Don't strip directory information; with previous change, allows retrieval of Lisp function and variable origin files from #'built-in-symbol-file relative to lisp-directory. (scan_lisp_file): Don't add an extraneous newline after the file name, put_filename has added the newline already. lisp/ChangeLog addition: 2008-12-27 Aidan Kehoe <kehoea@parhasard.net> * loadup.el (load-history): Add the contents of current-load-list to load-history before clearing it. Move the variable declarations earlier in the file to a format understood by make-docfile.c. * custom.el (custom-declare-variable): Add the variable's symbol to the current file's load history entry correctly, don't use a cons. Eliminate a comment that we don't need to worry about, we don't need to check the `initialized' C variable in Lisp. * bytecomp.el (byte-compile-output-file-form): Merge Andreas Schwab's pre-GPLv3 GNU change of 19970831 here; treat #'custom-declare-variable correctly, generating the docstrings in a format understood by make-docfile.c. * loadhist.el (symbol-file): Correct behaviour for checking autoloaded macros and functions when supplied with a TYPE argument. Accept fully-qualified paths from #'built-in-symbol-file; if a path is not fully-qualified, return it relative to lisp-directory if the filename corresponds to a Lisp file, and relative to (concat source-directory "/src/") otherwise. * make-docfile.el (preloaded-file-list): Rationalise some let bindings a little. Use the "-d" argument to make-docfile.c to supply Lisp paths relative to lisp-directory, not absolutely. Add in loadup.el explicitly to the list of files to be processed by make-docfile.c--it doesn't make sense to add it to preloaded-file-list, since that is used for purposes of byte-compilation too. src/ChangeLog addition: 2008-12-27 Aidan Kehoe <kehoea@parhasard.net> * doc.c (Fbuilt_in_symbol_file): Return a subr's filename immediately if we've found it. Check for compiled function and compiled macro docstrings in DOC too, and return them if they exist. The branch of the if statement focused on functions may have executed, but we may still want to check variable bindings; an else clause isn't appropriate.

 * 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) OffiX: use files and editor of OffiX
              drag something from files or editor into XEmacs
              drag something from XEmacs to xv (only with OffiX patch,
              editor or files -- files can only move and copy within
              itself, cause OffiX is not quite the right thing to do)
   4b) CDE: use dtfile and dtpad instead, but here everything should
            work.
   4c) 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.