November 1999 - XEmacs-Beta - XEmacs Mailing List Archives

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

William M. Perry

karlheg(a)cathcart.sysc.pdx.edu (Karl M. Hegbloom) writes: > >>>>> "Ben" == Ben Wing <ben(a)666.com> writes: > > Ben> Actually, Oscar, I was suggesting more simple changes, > Ben> i.e. just make your API consistent with general Elisp API > Ben> principles. > > Ben> For example: > > Ben> -- Instead of ldap-add-internal, just call it ldap-put and > Ben> make it the advertised > Ben> interface. There is no need to provide an interface like > Ben> ldap-add that automatically does an open and a close, > Ben> displays messages, looks for ldap-default-host, etc. Follow > Ben> standard convention and make the caller do this. > > But then just about every program that uses it will need to define a > wrapper function that does all that. The current ldap-add is very inneficient if you are going to be making anything other than _1_ modification, which isn't usually the case (at least when I use ldap :) I was thrown off by the fact that the LDAP routines you are supposed to use if you make the connection your self are all named 'xxx-internal', which means (to me) 'DO NOT USE THIS DIRECTLY', etc. Kind of like open-network-stream-internal and friends. -Bill P.

1 participants
0 comments

Re: Martin makes man & Makefile makeover 25 years

Adrian Aichner

>>>>> "APA" == Adrian Aichner <aichner(a)ecf.teradyne.com> writes: >>>>> "Martin" == Martin Buchholz <martin(a)xemacs.org> writes: APA> Hi Martin, APA> building on Windows NT native I get as far as this: APA> Wrote d:\tmp\21.2\xemacs\info\xemacs.info-19 APA> Splitting Info file...done. APA> Saving modified d:\tmp\21.2\xemacs\info\xemacs.info APA> Wrote d:\tmp\21.2\xemacs\info\xemacs.info APA> NMAKE : fatal error U1073: don't know how to make '..\man\lispref\index.perm' APA> Stop. APA> Compilation exited abnormally with code 2 at Thu Nov 18 00:44:43 APA> Have you removed APA> $(MANDIR)\lispref\index.perm APA> ? APA> nt/xemacs.mak has this rule: APA> $(INFODIR)\lispref.info: $(MANDIR)\lispref\lispref.texi APA> copy $(MANDIR)\lispref\index.perm $(MANDIR)\lispref\index.texi APA> $(MAKEINFO) $** APA> Why should $(MANDIR)\lispref\index.perm be discontinued? Hi again! I updated xemacs\man again. The previous distclean had removed index.texi files. The update gave me the info-related files: CVSROOT directory: :pserver:xemacs＠cvs.xemacs.org:/usr/CVSroot Working directory: d:\tmp\21.2\xemacs\man In directory .: Unknown .cvsignore Patched ChangeLog Patched Makefile Updated emodules.texi Removed info-stnd.texi Patched info.texi Patched standards.texi Patched texinfo.tex Patched texinfo.texi Patched xemacs-faq.texi In directory .\internals: Unknown .cvsignore Updated index.texi In directory .\lispref: Unknown .cvsignore Updated index.texi --------------------- End --------------------- Now I get stopped by this error: Saving modified d:\tmp\21.2\xemacs\info\emodules.info Wrote d:\tmp\21.2\xemacs\info\emodules.info ..\src\xemacs.exe -no-site-file -no-init-file -batch -l texinfmt -f batch-texinfo-format ..\man\info.texi texinfo formatting d:\tmp\21.2\xemacs\man\info.texi... Formatting Info file... Formatting Info file: ../info/info.info Converting info.texi to Info format... Removing trailing whitespace from Info buffer... >> Error: (error "＠ifnottex is not handled by texinfo") >> point at >> >> ＠node Top >> ＠top Info: An Introduction >> Info is a program for reading documentation, which you are us NMAKE : fatal error U1077: '..\src\xemacs.exe' : return code '0x1' Stop. Compilation exited abnormally with code 2 at Thu Nov 18 01:39:23 APA> Regards, APA> Adrian Martin> * internals/Makefile: Martin> * xemacs/Makefile: Martin> * lispref/Makefile: Martin> * new-users-guide/Makefile: Martin> * lispref/index.perm: Martin> * lispref/index.unperm: Martin> * lispref/permute-index: Martin> * internals/index.perm: Martin> * internals/index.unperm: Martin> Remove these Makefiles. Martin> Include all functionality in man/Makefile. Martin> Support only non-permuted indexes for simplicity. Martin> * emodules.texi: Martin> - TeX doesn't tolerate `_' in variable names; use `-' instead. Martin> * lispref/commands.texi:

1 participants
0 comments

CVS broken wrt subdirectories 25 years

Martin Buchholz

CVS appears to have a bug where if part of a commit involves files in directory and subdirectories of that directory, it forgets about the parent directory and only the subdirectory gets committed. I got bitten *twice* by this bug in one day. Unknown whether it's a client or server problem. I am running cvs 1.10.5 on Linux. If you run the same commit again, the remaining files actually make it to the repository. So I ran two extra `cvs commit's today. So do another CVS update. Again, the instructions to get your CVS tree up-to-date: rm man/*/index.texi # (only need to do this once) cvs update Martin

1 participants
0 comments

Re: gnuclient makes 21.2.b20 unhappy 25 years

Karl Kleinpaste

karlheg(a)cathcart.sysc.pdx.edu (Karl M. Hegbloom) writes: > Please tell me what frame #1 represents. Why is it all `f' and ?? ()? The source line in event-unixoid.c:93 is just nread = read (fd, &ch, 1); so evidently that frame is a piece of the glibc2.1 syscall interface.

1 participants
0 comments

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

Karl M. Hegbloom

>>>>> "Ben" == Ben Wing <ben(a)666.com> writes: Ben> Actually, Oscar, I was suggesting more simple changes, Ben> i.e. just make your API consistent with general Elisp API Ben> principles. Ben> For example: Ben> -- Instead of ldap-add-internal, just call it ldap-put and Ben> make it the advertised Ben> interface. There is no need to provide an interface like Ben> ldap-add that automatically does an open and a close, Ben> displays messages, looks for ldap-default-host, etc. Follow Ben> standard convention and make the caller do this. But then just about every program that uses it will need to define a wrapper function that does all that.

1 participants
0 comments

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

Karl M. Hegbloom

>>>>> "William" == William M Perry <wmperry(a)aventail.com> writes: William> After spitting out those ideas this morning, I think you William> could make it fit fairly easily, but whether anyone William> thinks the costs are worth it. There IS code out there William> that uses the existing LDAP routines (Emacs/W3, EUDC, William> etc), but nothing that really uses the db routines (can William> anyone contradict this? I couldn't find anything), so... `where-was-i-db.el' uses it.

1 participants
0 comments

Re: gnuclient makes 21.2.b20 unhappy 25 years

Karl M. Hegbloom

Karl Kleinpaste <karl(a)justresearch.com> writes: > #0 0x2ae11534 in __libc_read () > #1 0xffffffff in ?? () > #2 0x80cd313 in read_event_from_tty_or_stream_desc (event=0x87db8f0, Please tell me what frame #1 represents. Why is it all `f' and ?? ()?

1 participants
0 comments

Re: [HEADS UP] movemail locking overhaul ahead 25 years

Karl M. Hegbloom

>>>>> "Michael" == Michael Sperber <sperber(a)informatik.uni-tuebingen.de> writes: >>>>> "Jan" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: Jan> sperber(a)informatik.uni-tuebingen.de (Michael Sperber Jan> [Mr. Preprocessor]) writes: Jan> I propose that it should (by default) always use dotlocking Jan> (even together with any other method). >>> >>> I don't believe that's a good idea: Locking would no longer be >>> atomic, and you can get deadlocks that way. Jan> Not if everybody acquires the locks in the same order. Which Jan> is indeed the case. Michael> What's the order? And why is this the case? Is there a Michael> standard or agreement on this? Debian has a standard/policy on mail locking. Please see: <URL:http://www.debian.org/doc/debian-policy/ch5.html#s5.6> Perhaps `liblockfile' would be usefull for `movemail' as well?

1 participants
0 comments

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

Hrvoje Niksic

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > Hrvoje Niksic <hniksic(a)iskon.hr> writes: > > > > Can somebody give a bunch of examples where using integers as > > > characters is useful? > > > > I can. Here are four: > > > > (let ((letter ?a)) > > (while (< letter ?z) > > ... do something with letter ... > > (incf letter))) > > If only everybody used incf. I think it could make sense to make > incf and < work with characters (and not convert them to int). (incf foo) is exactly equivalent to (setf foo (1+ foo)). If you don't get my drift, try to imagine what (incf (car letters)) does. The point is, incf is a macro, and it doesn't know at compile-time whether the symbol will hold characters or numbers at run-time. If you want magic, build it into 1+. But I think I'd be against it. > Things get tricky with > > (+ ?a 1) ;; Return char > (+ ?a ?z) ;; Signal error? How about (+ 1 ?a)? And (+ 1 2 3 ?b)? It'd have to be *way* too much magic.

1 participants
0 comments

Re: Whatever happened to 21.1.8? 25 years

Jan Vroonhof

Jake Colman <colman(a)ppllc.com> writes: > Was 21.1.8 ever released? I remember the maintainer mentioning that he was > about to release it several weekends ago but I don't recall having seen it. It's out http://www.xemacs.org/list-archives/xemacs-announce/9911/msg00000.html Jan

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