November 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: [21.2] LDAP add and delete functions + interrupt fixes 26 years

William M. Perry

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > >>>>> "-BP" == William M Perry <wmperry(a)aventail.com> writes: > > -BP> To merge the LDAP code, you would have to do a major overhaul > -BP> of the existing database code, and I'm not sure you would be > -BP> able to get the full power of LDAP without making the > -BP> 'normal' databases pretty difficult to use. > > OK, that's why it might be hard. It still sounds like it's a good > idea to me. Perhaps, but I think that the code to do anything ldap-ish would still look very ldap-ish as opposed to abstract-database-ish. Another big problem with LDAP vs. the other database types is the ability to have multiple values off of a single attribute, and each 'key' in the database can have multiple attributes. In LDAP you have: uid=wmperry,ou=aventail.com,c=us -> cn = William M. Perry Bill Perry Emacs Dork mail = wmperry(a)aventail.com The older database backends would require you to do: You could theoretically do: - extend open-database to take a plist, but this breaks all (any?) existing code. LDAP would be a generic instance with (open-database '(:host "ldap.in.aventail.com" :type ldap :subtype 3 :bind-username "something" :bind-password "somethingelse" :base "o=aventail.com, c=us")) - extend get-database to be able to return multiple hits for a key. (get-database KEY ATTRIBUTE DATABASE) Documentation: Return value(s) for ATTRIBUTE on object KEY in DATABASE. An assoc list is returned, the car of each entry in the list the attribute name. The cdr is a list of values for that attribute. If there is no corresponding value, return nil. If ATTRIBUTE is t, returns all attributes and values. (get-database "uid=wmperry, o=aventail.com, c=us" "mail" dbhandle) => '(("mail" "wmperry(a)aventail.com")) (get-database "uid=wmperry, o=aventail.com, c=us" "cn" dbhandle) => '(("mail" "wmperry(a)aventail.com") ("cn" "William M. Perry" "Bill Perry" "Emacs Dork")) - extend put-database to be able to set multiple hits for a key, and submit multiple changes at once. (put-database KEY VALUES DATABASE &optional replace) Documentation: Updated record KEY in DATABASE with new VALUES. VALUES is an assoc list of attribute/value pairs. Some databases support multiple values. If optional fourth arg REPLACE is non-nil, replace any existing entry in the database. This whole doc string needs better updates. :) (put-database "uid=wmperry, o=aventail.com, c=us" '("cn" "Willie Perry") dbhandle nil) => t Would _add_ a CN to the record, so we'd now look like: uid=wmperry,ou=aventail.com,c=us -> cn = William M. Perry Bill Perry Emacs Dork Willie Perry mail = wmperry(a)aventail.com - New function search-database (search-database DATABASE CRITERIA) Documentation: Search DATABASE for records matching CRITERIA. CRITERIA is a property list. It is up to the backend database to convert this to native representation. Maybe we could have something for this that looks more lispish than an LDAP request. I'm not sure how a berkeley db database would implement this. For LDAP, we could have something like: (search-database dbhandle '(& (| ("cn" "William M. Perry" "Bill Perry")) ("mail" "wmperry(a)aventail.com"))) The ldap backend would convert this into: "(& (| (cn=William M. Perry") (cn="Bill Perry")) (mail=wmperry(a)aventail.com"))" And pass that off to ldap_search() - map-database would have to be revamped to return new values, etc. It would be nice if you could register new database backends at runtime, even for lisp functions. Then you could write an SQL backend in lisp using <URL:http://www.chez.com/emarsden/downloads/pg.el>. That could be done by having a generic 'elisp' backend in database.c, and be able to do something like: (define-database TYPE FUNCPLIST) Where the entries in FUNCPLIST would be the generic name 'open' 'close' 'search' etc would be the key, and the value would be the actual lisp function to call to do the searching. That's all just off the top of my head, but it might work. :) -Bill P.

2 participants
1 comments

Re: [21.2] LDAP add and delete functions + interrupt fixes 26 years

Oscar Figueiredo

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)iskon.hr> writes: >> Perhaps, but I think that the code to do anything ldap-ish would >> still look very ldap-ish as opposed to abstract-database-ish. Hrvoje> I agree with Bill. Abstract interfaces are a nice thing up to a Hrvoje> point, i.e. as long as they serve to us and not the other way around. Hrvoje> If LDAP serves a purpose totally different than a flat database, it's Hrvoje> quite fine to have a different interface for the two. Just to add my 2 cts, I also like abstraction and uniform interfaces (after all EUDC is a simple attempt at that) but I agree 200% with Bill and Hrvoje. The LDAP APIs are still evolving, adhering to them is the simple way to go. Even if we devised a good interface above the current API now, nothing guarantees we could easily fit forthcoming evolutions into it. I, for one, won't go that way but I won't discourage anyone that would like to implement such an interface. Oscar

2 participants
1 comments

Re: read-coding-system 26 years

Ben Wing

Approved, but: 1) You should never combine patches like this. Instead, resubmit the patch that was not approved, with a comment about this fact. (Which the patch tender -- currently Jan -- ought to have noticed, and done something about.) 2) Try to put some comment into the source whenever you change anything -- e.g. in case 1: ; exclude blank arguments, which result when the user accepts the default value in case 2: change the doc string from Prompting with string PROMPT. If the user enters null input, return second argument DEFAULT-CODING-SYSTEM." to Prompting with string PROMPT. If the user enters null input, return second argument DEFAULT-CODING-SYSTEM. DEFAULT-CODING-SYSTEM can be a string, symbol, or coding-system object." (and in the process, fix up the code so this is actually true.) ben Yoshiki Hayashi wrote: > xemacs -vanilla > > C-x RET c RET > Wrong type argument: stringp, iso-2022-8 > > C-x RET c or universal-coding-system-argument passes > buffer-file-coding-system as a default value to > read-coding-system. > However, read-coding-system only expects string as a default > argument. It should recognize symbol. > > Because of CVS, this patch cantains another patch, > http://www.xemacs.org/list-archives/xemacs-patches/9910/msg00047.html > which I've got no reply. > > 1999-11-16 Yoshiki Hayashi <t90553(a)mail.ecc.u-tokyo.ac.jp> > > * minibuf.el (read-coding-system): Accept symbol as > a default-coding-system. > > ------------------------------------------------------------------------ > Index: minibuf.el > =================================================================== > RCS file: /usr/CVSroot/XEmacs/xemacs/lisp/minibuf.el,v > retrieving revision 1.14.2.7 > diff -u -r1.14.2.7 minibuf.el > --- minibuf.el 1999/07/22 06:19:44 1.14.2.7 > +++ minibuf.el 1999/11/16 06:44:55 > ＠＠ -327,7 +327,7 ＠＠ > (defvar current-minibuffer-contents) > (defvar current-minibuffer-point) > > -(defcustom minibuffer-history-minimum-string-length nil > +(defcustom minibuffer-history-minimum-string-length 1 > "*If this variable is non-nil, a string will not be added to the > minibuffer history if its length is less than that value." > :type '(choice (const :tag "Any" nil) > ＠＠ -2118,7 +2118,9 ＠＠ > Prompting with string PROMPT. > If the user enters null input, return second argument DEFAULT-CODING-SYSTEM." > (intern (completing-read prompt obarray 'find-coding-system t nil nil > - default-coding-system))) > + (if (symbolp default-coding-system) > + (symbol-name default-coding-system) > + default-coding-system)))) > > (defun read-non-nil-coding-system (prompt) > "Read a non-nil coding-system from the minibuffer. > > ------------------------------------------------------------------------ > > -- > Yoshiki Hayashi

1 participants
0 comments

21.2.b20: C-g in isearch differs from old b17 behavior 26 years

Mark Thomas

I've recently upgraded from 21.2.b17 to 21.2.b20 and I notice that C-g behaves differently during incremental search. Suppose I isearch (successfully) for "foo" and press RET to exit isearch. Next I isearch (successfully) for "bar" and use C-g to exit isearch. In b17, pressing C-s C-s would isearch for "bar"; in b20, it searches for "foo". Is this by design? I don't remember seeing mention of it on the xemacs-beta list. I notice that isearch-quit (bound by default to (ugh!) ESC ESC ESC) remembers the most recent search string. Perhaps I'll just bind isearch-quit to something more convenient (and eventually retrain my fingers). -Mark

1 participants
0 comments

Re: elisp packages 26 years

Raymond Toy

>>>>> "Martin" == Martin Buchholz <martin(a)xemacs.org> writes: Martin> that it is entirely natural that people would omit including the Martin> packages, even if they are professional GNU software maintainers such Martin> as inhabit Cygnus. Also, people who did try to follow the Martin> instructions and use documented interfaces to install packages after Martin> installing the `core' XEmacs often failed (and reverted to 20.4, since Martin> that actually `worked'). >> From this point of view, the package system has been an unmitigated disaster. I wouldn't exactly say that. Of course, being behind a firewall with an ftp that efs doesn't like, I've never had to really deal with packages. I just download the sumo tarballs whenever I feel like it, or the individual packages if I need them. However, I think the whole package stuff would work better if it used http instead of ftp to get the packages. "Everyone" has a working http access. ftp is much more difficult, and, in my case, unusable. (It works just fine from the command line, but not via efs.) I wish I had time (and knowledge) to make the package stuff use http instead of efs.... Ray

1 participants
0 comments

Re: elisp packages 26 years

Martin Buchholz

>>>>> "R" == Ravi Wikramanayake <rwiks(a)hotmail.com> writes: R> I recently purchased cygwin 1.0 from cygnus. It appears that the xemacs R> bundled with it does not seem to have c++-mode, c-mode, java-mode *.el and R> *.elc files. Could you please suggest how I can gain access to the R> respective *.el and associated *.elc files. Get the `sumo' package tarball from ftp://ftp.xemacs.org/pub/xemacs/packages/xemacs-sumo.tar.gz Also get xemacs-mule-sumo.tar.gz if your binaries are using the `Mule' feature. I predicted in private that this sort of thing would happen. There is such a legacy of being able to build *functional* software using the algorithm: get foo-n.m.tar.gz tar xzf foo-n.m.tar.gz cd foo-n.m configure make make install that it is entirely natural that people would omit including the packages, even if they are professional GNU software maintainers such as inhabit Cygnus. Also, people who did try to follow the instructions and use documented interfaces to install packages after installing the `core' XEmacs often failed (and reverted to 20.4, since that actually `worked'). >From this point of view, the package system has been an unmitigated disaster. Martin

1 participants
0 comments

Re: gnuserv dies when I gnuclient a file I can't read 26 years

Hamish Macdonald

>>>>> Hamish Macdonald <hamishm(a)lucent.com> writes: Hamish> When I use gnuclient to attempt to edit or view a file for Hamish> which I do not have read permissions, the file-error raised Hamish> causes gnuserv to die, requiring gnuserv to be restarted. Followup: I did some more investigation, and discovered that on an error raised by the evaluation of the client request, gnuserv-process-filter tries to write back the error to the client using the gnuserv-current-client variable, except that in my case, gnuserv-edit-files has nil-ed out gnuserv-current-client as seen in the lisp code below (from gnuserv.el). This nil is then passed to gnuserv, which can't parse a "%d/%d" client-id/length out of the result. The sscanf in gnuserv.c:handle_response should probably have its return value (the number of items scanned) examined. In my case, sscanf can't scan an integer, leaving the result_len variable undefined, since it is never initialized to zero. On my machine, gnuserv exits with a stderr error message I never see. For now, I've worked around the problem by commenting out the nil-ing of gnuserv-current-client in gnuserv-edit-files. Regards, Hamish. ---------------------------------------------------------------------- ;; "Execute" a client connection, called by gnuclient. This is the ;; backbone of gnuserv.el. (defun gnuserv-edit-files (type list &rest flags) "For each (line-number . file) pair in LIST, edit the file at line-number. The visited buffers are memorized, so that when \\[gnuserv-edit] is invoked in such a buffer, or when it is killed, or the client's device deleted, the client will be invoked that the edit is finished. TYPE should either be a (tty TTY TERM PID) list, or (x DISPLAY) list. If a flag is `quick', just edit the files in Emacs. If a flag is `view', view the files read-only." (let (quick view) (mapc (lambda (flag) (case flag (quick (setq quick t)) (view (setq view t)) [...] (client (make-gnuclient :id gnuserv-current-client :device device :frame new-frame))) => (setq gnuserv-current-client nil) ;; If the device was created by this client, push it to the list. (and (/= old-device-num (length (device-list))) (push device gnuserv-devices)) (and (frame-iconified-p frame) (deiconify-frame frame)) ;; Visit all the listed files. (while list (let ((line (caar list)) (path (cdar list))) (select-frame frame) ;; Visit the file. (funcall (if view gnuserv-view-file-function gnuserv-find-file-function) path) (goto-line line) [...] --=-=-=--

1 participants
0 comments

Re: Char-related crashes (hopefully) fixed 26 years

Raymond Toy

>>>>> "Valdis" == Valdis Kletnieks <Valdis.Kletnieks(a)vt.edu> writes: Valdis> On Tue, 16 Nov 1999 08:00:51 +0100, Hrvoje Niksic said: >> But Common Lisp's char concept is evil in its own way. I believe >> Common Lisp allows various modifiers to be encoded in the character >> itself. Yuck. Valdis> The mind boggles. You mean you can have a green A, a blue A, Valdis> an A with a swedish accent (not to be confused with any ISO8859-1 Valdis> character that looks like a modified A)? I believe that was so up through CLtL2, but ANSI CL got rid of the character attributes. Ray

2 participants
1 comments

Crash on signal in tabs with --pdump 26 years

Stephen J. Turnbull

Wasn't doing much. I had some gutter-related files open. The crash was apparently triggered by clicking on the tab for gutter.info (which doesn't exist in the distribution yet, so don't get your hopes up). Immediately before that I had read that file with C-x C-f, inserted src/gutter.c with C-x i, and then read src/gutter.h with C-x C-f. I had a crash on the same binary temacs/xemacs.dmp a few days ago, but had ulimit -c 0 :-( I have the core file if anyone can think of useful things to do with it. Debian linux "potato", current as of mid last week. XEmacs 21.2.20 by CVS update a few hours after the 21.2.20 release was announced. Lisp backtrace, C backtrace, and Installation appended. Lisp backtrace follows: # (condition-case ... . error) # (catch top-level ...) gdb /home/steve/Projects/XEmacs/xemacs-21.2/src/temacs core GNU gdb 19990928 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"... Core was generated by `./temacs'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libaudio.so.2...done. Reading symbols from /usr/lib/libcanna.so.1...done. Reading symbols from /usr/lib/libRKC.so.1...done. Reading symbols from /usr/X11R6/lib/libXaw3d.so.6...done. Reading symbols from /usr/lib/libpng.so.2...done. Reading symbols from /usr/lib/libz.so.1...done. Reading symbols from /usr/X11R6/lib/libXpm.so.4...done. Reading symbols from /usr/X11R6/lib/libXmu.so.6...done. Reading symbols from /usr/X11R6/lib/libXt.so.6...done. Reading symbols from /usr/X11R6/lib/libXext.so.6...done. Reading symbols from /usr/X11R6/lib/libX11.so.6...done. Reading symbols from /usr/X11R6/lib/libSM.so.6...done. Reading symbols from /usr/X11R6/lib/libICE.so.6...done. Reading symbols from /lib/libdl.so.2...done. Reading symbols from /lib/libdb.so.3...done. Reading symbols from /lib/libncurses.so.4...done. Reading symbols from /lib/libm.so.6...done. Reading symbols from /lib/libc.so.6...done. Reading symbols from /lib/ld-linux.so.2...done. Reading symbols from /lib/libnss_files.so.2...done. Reading symbols from /lib/libnss_compat.so.2...done. Reading symbols from /lib/libnsl.so.1...done. #0 0x402fd5d1 in kill () from /lib/libc.so.6 (gdb) where #0 0x402fd5d1 in kill () from /lib/libc.so.6 #1 0x808fce4 in fatal_error_signal (sig=11) at emacs.c:276 #2 0x402fd508 in sigaction () from /lib/libc.so.6 #3 0x81e5ca6 in XawTabsSetHighlight (t=0x841fab8, w=0x85211f0) at xlwtabs.c:1283 #4 0x81e53f0 in XawTabsSetTop (w=0x85211f0, callCallbacks=1) at xlwtabs.c:1262 #5 0x81e60af in TabsSelect (w=0x841fab8, event=0xbffff73c, params=0x0, num_params=0x40178d14) at xlwtabs.c:1047 #6 0x4016a773 in _XtMatchAtom () from /usr/X11R6/lib/libXt.so.6 #7 0x4016abcc in _XtMatchAtom () from /usr/X11R6/lib/libXt.so.6 #8 0x4016b0e4 in _XtTranslateEvent () from /usr/X11R6/lib/libXt.so.6 #9 0x40148d15 in XtDispatchEventToWidget () from /usr/X11R6/lib/libXt.so.6 #10 0x4014963e in _XtOnGrabList () from /usr/X11R6/lib/libXt.so.6 #11 0x40149888 in XtDispatchEvent () from /usr/X11R6/lib/libXt.so.6 #12 0x40154074 in XtAppProcessEvent () from /usr/X11R6/lib/libXt.so.6 #13 0x81aeb4b in emacs_Xt_next_event (emacs_event=0x84adb70) at event-Xt.c:2427 #14 0x80dac48 in event_stream_next_event (event=0x84adb70) at event-stream.c:565 #15 0x80dcdf0 in next_event_internal (target_event=139123568, allow_queued=1) at event-stream.c:2020 #16 0x80dd46d in Fnext_event (event=139123568, prompt=1078469536) at event-stream.c:2237 #17 0x8073cb1 in Fcommand_loop_1 () at cmdloop.c:566 #18 0x8073f5d in command_loop_1 (dummy=1078469536) at cmdloop.c:490 #19 0x80921be in condition_case_1 (handlers=1078469344, bfun=0x8073f14 <command_loop_1>, barg=1078469536, hfun=0x8073fcc <cmd_error>, harg=1078469536) at eval.c:1630 #20 0x80740bf in command_loop_2 (dummy=1078469536) at cmdloop.c:252 #21 0x80993dc in internal_catch (tag=1078287784, func=0x8074080 <command_loop_2>, arg=1078469536, threw=0x0) at eval.c:1305 #22 0x80734ce in initial_command_loop (load_me=1078469536) at cmdloop.c:301 #23 0x808e0bd in xemacs_21_2_b20_i686_pc_linux () at emacs.c:1873 #24 0x808fe5b in main (argc=1, argv=0xbffffd64, envp=0xbffffd6c) at emacs.c:2236 (gdb) uname -a: Linux tleepslib 2.2.10 #2 Thu Jun 24 19:22:23 JST 1999 i686 unknown ./configure '--with-mule' '--with-xim=xlib' '--with-xfs' '--with-sound=both' '--with-widgets=athena3d' '--with-dialogs=athena3d' '--pdump' XEmacs 21.2-b20 "Yoko" configured for `i686-pc-linux'. Where should the build process find the source code? /home/steve/Projects/XEmacs/xemacs-21.2 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the GNU C Library.) Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11R6/include Where do we find X Windows libraries? /usr/X11R6/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in both network and native sound support. Compiling in support for Berkeley DB. Compiling in support for ncurses. Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using raw Xlib to provide XIM support. Using XFontSet to provide bilingual menubar. Compiling in support for Canna on Mule. Compiling in support for proper WM_COMMAND handling. Using Lucid menubars. Using Lucid scrollbars. Using Athena-3d native widgets. Using Athena-3d dialog boxes. Compiling in DSO module support. movemail will use "dot-locking" for locking mail spool files. Using the new portable dumper (wishful thinking). Compiling in extra code for debugging. WARNING: --------------------------------------------------------- WARNING: Compiling in support for runtime error checking. WARNING: XEmacs will run noticeably more slowly as a result. WARNING: Error checking is on by default for XEmacs beta releases. WARNING: --------------------------------------------------------- -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 __________________________________________________________________________ __________________________________________________________________________ What are those two straight lines for? "Free software rules."

2 participants
3 comments

Win32 21.1.6 immediate crash bug in Win98 26 years

Jari Aalto

[please keep CC, since I'm not currently in the list] I'm Running Win98 with IE 5. For some reason the ~ is not interpreted as HOME -- My Home disks are under drive d: -- And Unix replicate is on drive e: (setenv "HOME" "d:/home/jaalto/") (expand-file-name "~") "e:\\usr\\local\\bin\\emacs\\xemacs\\XEmacs-21.1.6\\i386-pc-win32\\home\\jaalto\\" Since expand-file-name is used in numerous places I tried to fix this with simple advice code. But using the adviced function makes Xemacs to die with windows exception :-) (defun my-expand-file-name (path) "Expand ~ to mean HOME. XEmacs 21.1.6 win32 expands it somehow wrong." (let ((home (getenv "HOME")) ) (cond ((string-match "~/" path) (concat (file-name-as-directory home) (substring path 2))) ((string-match "~" path) (file-name-as-directory home)) (t path )))) (when (string-match "21\.1.*win32" (emacs-version)) (defadvice expand-file-name (before my act) "Replace Function with `my-expand-file-name'." (ad-set-arg 0 (my-expand-file-name (ad-get-arg 0))))) (expand-file-name "~") C-xC-e ---> and XEmacs is taken down by the Win98.... jari

1 participants
0 comments

2025

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 November 1999