March 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Re: why do not provide author's names and legal docs to emasc ? 24 years, 2 months

SL Baur

Michael Sperber <sperber(a)informatik.uni-tuebingen.de> writes in xemacs-beta(a)xemacs.org: >>>>>> "kai" == kai <kaiq(a)hotmail.com> writes: kai> why????????????????????????????????????????????? > Most of us have. I, for one, have stopped. Negotiating with RMS over > terminology and legalese tends to be among the few things in life more > painful than having my gums scraped. Disclaimer: I don't speak for the XEmacs maintainers. Stallman lied about copyright assignment being a barrier to importing XEmacs code into Emacs. The Mule code he imported for Emacs 20 (and since) is owned by the Japanese government and the tag in the source code "Licensed to the FSF" has no written basis[1]. If the Japanese government decided for any reason to change copyright terms (it's paid for by tax Yen), there isn't a court on Earth he could go for redress. Given the facts as I now know them, it makes utterly no sense for XEmacs to require copyright assignment on code. It only pisses people off, is make work for the maintainers, and when copyright assignment is made Stallman usually makes a pitch to the person to stop developing for XEmacs. Bah. Who needs that? He imported a huge body of Mule code without copyright assignment into Emacs. Let him do the same with XEmacs code (IMO). Footnotes: [1] There is no formal, written contract.

1 participants
0 comments

Re: why do not provide author's names and legal docs to emasc ? 24 years, 2 months

Michael Sperber

>>>>> "kai" == kai <kaiq(a)hotmail.com> writes: kai> why????????????????????????????????????????????? Most of us have. I, for one, have stopped. Negotiating with RMS over terminology and legalese tends to be among the few things in life more painful than having my gums scraped. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

More on make-face-larger 24 years, 2 months

Kirill 'Big K' Katsnelson

I traced it down to frob-face-property, where I broke a bunch of legs on my code walk-through. If anybody can read this function, that'd be great. Here's what I got. xemacs -q (specifier-spec-list (face-font 'default)) => nil (make-face-larger 'default nil) ;; nothing changes really (specifier-spec-list (face-font 'default)) => nil (make-face-larger 'default (selected-device)) ;; Zoom! (specifier-spec-list (face-font 'default)) => (#<mswindows-device 0x1b04> (nil . #<font-instance "Courier New:Regular:11::Western" on #<mswindows-device 0x1b04> 0x980a1653 0x1fb1>))) (make-face-larger 'default nil) ;; Zoom again => ((#<mswindows-device 0x1b04> (nil . #<font-instance "Courier New:Regular:12::Western" on #<mswindows-device 0x1b04> 0x100a0494 0x2117>))) Anybody understand what is going on? Big K

1 participants
0 comments

make-face-larger does not anymore. 24 years, 2 months

Kirill 'Big K' Katsnelson

I just built XEmacs from a snapshot under NT, and (make-face-larger 'default) does not work at all, nothing really changes, nor does (m-f-smaller 'default) work. Anybody else seeing this? Big K

1 participants
0 comments

(Real) Database support for Emacs, V2 24 years, 2 months

SL Baur

This patch is against 21.1. The next patch will be against 21.2 and go to xemacs-patches. I plan on maintaining a version of this patch against 21.1 until 21.2 is released, though I don't know yet where I'm going to put it. Changes from the last posting: All of the API except copy in/out and asynchronous notification has been implemented. I have not yet converted certain error returns to signals, but will prior to final integration. There is now a comprehensive programmer's manual, with many, many examples. I have made PQclear and PQfinish visible to Lisp, though they will cause crashes at least at the next garbage collection. The code in the stub file, lisp/pg-util.el was moved into the programmer's manual. There is a TODO list in postgresql.c that list the items I feel are incomplete. The new files src/postgresql.h, src/postgresql.c, man/lispref/postgresql.texi are attached at the end of this message. Questions, comments, discussion welcome. SQL in an Emacs Lisp Interaction buffer rocks. ChangeLog: 2000-03-06 SL Baur <steve(a)musashimaru.m17n.org> * configure.in: add autodetection of PostgreSQL runtime libraries src/ChangeLog: 2000-03-06 SL Baur <steve(a)musashimaru.m17n.org> * config.h.in: Add symbols HAVE_POSTGRESQL and HAVE_POSTGRESQLV7 * inline.c: Include postgresql.h lrecord stuffs to placate buggy GCCs. * emacs.c (main_1): Call postgres initialization code. * postgresql.h: New file. PostgreSQL RDBMS support. * postgresql.c: New file. man/ChangeLog: 2000-03-07 SL Baur <steve(a)musashimaru.m17n.org> * lispref/postgresql.texi (PostgreSQL Support): New File. * lispref/ldap.texi: Insert PostgreSQL/libpq chapter. * lispref/lispref.texi (Top): Ditto. * lispref/internationalization.texi: Ditto. Index: configure.in =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/configure.in,v retrieving revision 1.138 diff -u -r1.138 configure.in --- configure.in 2000/02/09 01:40:53 1.138 +++ configure.in 2000/03/08 03:32:51 ＠＠ -497,6 +497,7 ＠＠ with_sparcworks | \ with_tooltalk | \ with_ldap | \ + with_postgresql | \ with_pop | \ with_kerberos | \ with_hesiod | \ ＠＠ -2698,6 +2699,55 ＠＠ fi fi +dnl Autodetect PostgreSQL +dnl The default installation location (non-Linux) is /usr/local/pgsql; +dnl a different prefix can be selected at build/install time. If PostgreSQL +dnl is installed into a different prefix, that prefix must be specified in +dnl in the --site-prefixes flag. +dnl The default RPM-based Linux installation location is /usr. +AC_CHECKING(for PostgreSQL) +postgres_includes_found=no +save_c_switch_site="$c_switch_site" +dnl First check site prefixes +if test "$with_postgresql" != "no"; then + AC_CHECK_HEADER(libpq-fe.h,postgres_includes_found=yes) +fi +dnl test for Linux-style installation in /usr +if test "$postgres_includes_found" = "no" -a "$with_postgresql" != "no" -a \ + -d "/usr/include/pgsql"; then + c_switch_site="$c_switch_site -I/usr/include/pgsql" + AC_CHECK_HEADER(libpq-fe.h,postgres_includes_found=yes) + if test "$postgres_includes_found" != "yes"; then + c_switch_site="$save_c_switch_site" + fi +fi +if test "$postgres_includes_found" = "no" -a "$with_postgresql" != "no" -a \ + -d "/usr/local/pgsql/include"; then + c_switch_site="$c_switch_site -I/usr/local/pgsql/include" + AC_CHECK_HEADER(libpq-fe.h,postgres_includes_found=yes) + if test "$postgres_includes_found" != "yes"; then + c_switch_site="$save_c_switch_site" + fi +fi + +dnl last check -- can we link against libpq? +if test "$postgres_includes_found" = "yes"; then + AC_CHECK_LIB(pq,PQconnectdb,with_postgresql=yes,with_postgresql=no) +fi +if test "$with_postgresql" = "yes"; then + AC_CHECK_LIB(pq,PQconnectStart,with_postgresqlv7=yes,with_postgresqlv7=no) +fi +if test "$with_postgresql" = "yes"; then + AC_DEFINE(HAVE_POSTGRESQL) + if test "$with_postgresqlv7" = "yes"; then + AC_DEFINE(HAVE_POSTGRESQLV7) + fi + XE_PREPEND(-lpq, LIBS) + XE_ADD_OBJS(postgresql.o) +else + c_switch_site=$save_c_switch_site +fi + dnl ---------------------- dnl Graphics libraries dnl ---------------------- ＠＠ -4060,6 +4110,12 ＠＠ test "$with_ns_ldap" = yes && echo " Compiling in support for LDAP (Netscape SDK)." test "$with_ldap" = yes -a "$with_umich_ldap" = no -a "$with_ns_ldap" = no && echo " Compiling in support for LDAP (Generic)." +if test "$with_postgresql" = yes; then + echo " Compiling in support for PostgreSQL." + if test "$with_postgresqlv7" = yes; then + echo " Using PostgreSQL V7 bindings." + fi +fi test "$with_ncurses" = yes && echo " Compiling in support for ncurses." test "$with_gpm" = yes && echo " Compiling in support for GPM (General Purpose Mouse)." Index: man/lispref/internationalization.texi =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/man/lispref/internationalization.texi,v retrieving revision 1.2 diff -u -r1.2 internationalization.texi --- man/lispref/internationalization.texi 1998/07/10 02:49:03 1.2 +++ man/lispref/internationalization.texi 2000/03/08 03:32:56 ＠＠ -3,7 +3,7 ＠＠＠c Copyright (C) 1990, 1991, 1992, 1993 Free Software Foundation, Inc. ＠c See the file lispref.texi for copying conditions. ＠setfilename ../../info/internationalization.info -＠node Internationalization, MULE, LDAP Support, top +＠node Internationalization, MULE, PostgreSQL Support, top ＠chapter Internationalization ＠menu Index: man/lispref/ldap.texi =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/man/lispref/ldap.texi,v retrieving revision 1.1 diff -u -r1.1 ldap.texi --- man/lispref/ldap.texi 1998/07/10 02:56:12 1.1 +++ man/lispref/ldap.texi 2000/03/08 03:32:56 ＠＠ -3,7 +3,7 ＠＠＠c Copyright (C) 1998 Free Software Foundation, Inc. ＠c See the file lispref.texi for copying conditions. ＠setfilename ../../info/ldap.info -＠node LDAP Support, Internationalization, ToolTalk Support, top +＠node LDAP Support, PostgreSQL Support, ToolTalk Support, top ＠chapter LDAP Support ＠cindex LDAP Index: man/lispref/lispref.texi =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/man/lispref/lispref.texi,v retrieving revision 1.12 diff -u -r1.12 lispref.texi --- man/lispref/lispref.texi 1999/05/13 16:14:08 1.12 +++ man/lispref/lispref.texi 2000/03/08 03:32:56 ＠＠ -204,6 +204,7 ＠＠ * ToolTalk Support:: Interfacing with the ToolTalk message service. * LDAP Support:: Interfacing with the Lightweight Directory Access Protocol. +* PostgreSQL Support:: Interfacing to the PostgreSQL libpq library. * Internationalization:: How Emacs supports different languages and cultural conventions. * MULE:: Specifics of the Asian-language support. ＠＠ -1199,6 +1200,7 ＠＠＠include x-windows.texi ＠include tooltalk.texi ＠include ldap.texi +＠include postgresql.texi ＠include internationalization.texi ＠include mule.texi Index: src/config.h.in =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/src/config.h.in,v retrieving revision 1.53 diff -u -r1.53 config.h.in --- src/config.h.in 1999/07/07 03:10:32 1.53 +++ src/config.h.in 2000/03/08 03:33:00 ＠＠ -357,6 +357,11 ＠＠ /* Do we have Netscape LDAP SDK library */ #undef HAVE_NS_LDAP +/* Do we wish to link against the PostgreSQL RDBMS run-time library? + */ +#undef HAVE_POSTGRESQL +#undef HAVE_POSTGRESQLV7 + /* Do you have the Xauth library present? This will add some extra functionality to gnuserv. */ #undef HAVE_XAUTH Index: src/emacs.c =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/src/emacs.c,v retrieving revision 1.93 diff -u -r1.93 emacs.c --- src/emacs.c 1999/12/04 04:13:05 1.93 +++ src/emacs.c 2000/03/08 03:33:01 ＠＠ -1062,6 +1062,10 ＠＠ syms_of_eldap (); #endif +#ifdef HAVE_POSTGRESQL + syms_of_postgresql (); +#endif + /* Now create the subtypes for the types that have them. We do this before the vars_*() because more symbols may get initialized here. */ ＠＠ -1437,6 +1441,10 ＠＠ #ifdef HAVE_LDAP vars_of_eldap (); +#endif + +#ifdef HAVE_POSTGRESQL + vars_of_postgresql(); #endif /* Now initialize any specifier variables. We do this later Index: src/inline.c =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/src/inline.c,v retrieving revision 1.12 diff -u -r1.12 inline.c --- src/inline.c 1998/05/24 05:40:44 1.12 +++ src/inline.c 2000/03/08 03:33:01 ＠＠ -67,6 +67,11 ＠＠ #include "eldap.h" #endif +#ifdef HAVE_POSTGRESQL +#include <libpq-fe.h> +#include "postgresql.h" +#endif + #ifdef HAVE_TOOLBARS #include "toolbar.h" #endif

1 participants
0 comments

Re: A real database for Emacs 24 years, 2 months

Marat Boshernitsan

Hrvoje Niksic <hniksic(a)iskon.hr> writes: > Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > > > SL Baur <steve(a)beopen.com> writes: > > > > > > 1. Can we have this as a module pleeeze? > > > > > > Is the module code stable now? > > > > Yes. > > ? > > Since when? The module code has _never_ ever been stable, nor has it > ever been used for anything other than testing. The modules have been > broken (and in some cases fixed later) by many changes some of which > are still ongoing, like the portable dumper. If that counts for anything, I am using modules quite happily on 21.1.7 + module patches[1]. Has anything significantly changed in 21.2? Marat. Footnotes: [1] Yes, there are some XEmacs compilation quirks, but other than that, they work just fine on Linux and Solaris.

1 participants
0 comments

Re: A real database for Emacs 24 years, 2 months

SL Baur

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes in xemacs-beta(a)xemacs.org: ... > Yes, but still libpq installed (there are already people on various > lists and groups complaining why the debian XEmacs packages requires > the ldap libraries). That is braindamage(TM) that is specifically made taboo in the binary kit building guidelines. If the libraries were statically linked in XEmacs binaries for distribution, there wouldn't be that problem. I may have much more to say about this in the coming months. > Of course I have nothing against having it default to non-mule on a > plain configure. >> asynchronous queries[1] working last night. Cursors should work for >> free since they're implemented by the Postgres backend in SQL. I'll > Cool... I consed up a simple mapping function (just for you :-) last night to put in the programmer's manual. SQL in Emacs Lisp _really_ rocks. (This isn't the most general code in the world, but that's not really important). Here's another example of cursors, this time with a Lisp macro to implement a mapping function over a table. (defmacro map-db (P table condition callout) `(let (R) (pq-exec ,P "BEGIN;") (pq-exec ,P (concat "DECLARE k_cursor CURSOR FOR SELECT * FROM " ,table " " ,condition " ORDER BY f1 DESC;")) (setq R (pq-exec P "FETCH k_cursor;")) (while (eq (pq-ntuples R) 1) (,callout (pq-get-value R 0 0) (pq-get-value R 0 1)) (setq R (pq-exec P "FETCH k_cursor;"))) (pq-exec P "END;"))) => map-db (defun callback (arg1 arg2) (message "arg1 = %s, arg2 = %s" arg1 arg2)) => callback (map-db P "xemacs_test" "WHERE field2 > 10" callback) => arg1 = stuff, arg2 = 42 => arg1 = b, arg2 = 97 => arg1 = a string, arg2 = 12 => arg1 = a, arg2 = 97 => #<PGresult PGRES_COMMAND_OK - COMMIT>

1 participants
0 comments

gnuclient/gnuserv and local internet domain sockets 24 years, 2 months

Greg J. Badros

I'm trying to get multiple gnuserv processes running on the same machine at different ports so that I can selectively connect to a specific one. The high-level specific purpose is to enable me to connect to *the* XEmacs that is already running GNUS, or *the* XEmacs that already has my dissertation text loaded. I typically want to connect via a non-windowed attachment from home, ssh'd in to the machine on which the XEmacsen are running. My attempt to make this work has been to set GNU_PORT to a distinguished number before starting the XEmacs processes. Then I was hoping to be able to use, e.g., gnuclient -p 21033 and gnuclient -p 21035 to connect to two different XEmacsen with GNU_PORT set to 21033 and 21035 respectively. >From what I can gather, though, /tmp/gsrvUID/gsrv is used to initiate the connection *unless* I give the -h option to specify the hostname -- that then forces using internet sockets (and the GNU-SECURE-1 or MIT Magic Cookie authentication method). (The source code to gnuserv leads me to believe that the unix domain socket name cannot be altered.) Unfortunately, the -h option to gnuclient then requires that the -nw option (non-windowing) is *not* given. This is unfortunate, since it's far more convenient to not start a full new frame over a slow modem connection. To work around this difficulty, I've re-built my gnuclient.c to have line 464's conditional always fail to not report an error: if (suppress_windows_system && hostarg && 0 /*GJB:: added && 0 */) { fprintf (stderr, "%s: Remote editing is available only on X\n", progname); exit (1); } I don't doubt that there is some problem with -nw editing w/o X11, but here the fact that the hostarg is given really shouldn't imply that remote editing is requested-- perhaps the host IPs should be compared, instead. I.e., I'm using the -h argument strictly to permit the ability to use internet sockets instead of a unix domain socket. Another, more-direct, possibility to fix this difficulty is to simply permit naming the unix-domain socket to use. I'm not sure of the security implication (if any) of this suggestion, but it seems likely that mangling the UID + some user-specified number would be a nice way to provide this capability in a fairly clean way. I'd love to see a suitable change in the next versions of gnuclient/gnuserv to better support multiple servers. Thanks, Greg J. Badros gjb(a)cs.washington.edu Seattle, WA USA http://www.cs.washington.edu/homes/gjb

1 participants
0 comments

Re: A real database for Emacs 24 years, 2 months

Jan Vroonhof

Hrvoje Niksic <hniksic(a)iskon.hr> writes: > Since when? The module code has _never_ ever been stable, nor has it > ever been used for anything other than testing. I meant 'stable' in the sense that it is finished but for makefile hackery. It does all that it should do. The database stuff seems like an excellent thing to push to a module. "It currently is isn't use much" shouldn't be a reason to not do it, because that would lead to catch-22 situation. Jan

1 participants
0 comments

`scroll-up-command' still broken in 21.2 under AIX 24 years, 2 months

Markus Alt

I still have that very annoying scrolling misbehaviour in 21.2 that I reported a while ago: http://www.xemacs.org/list-archives/xemacs-beta/199911/msg00262.html Unfortunately, there has been almost no response and I haven't found any solution for this - `scroll-up' hasn't worked for me in any beta since 21.2.19 under AIX 4.3.2, although it's ok on Linux. I assume there aren't too many guys out there on AIX, but am I the only one seeing this? If no, perhaps there's really something broken; if yes, what am I doing wrong? (`scroll-down' works and neither configuring `--with-scrollbars=athena' nor '--with-scrollbars=no' helps here). Any hints? Markus

2 participants
1 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 March 2000