Aki Vehtari <Aki.Vehtari(a)hut.fi> writes in xemacs-beta(a)xemacs.org:
...
> Btw. gud.el in XEmacs is dated 1993 and gud.el in emacs-20.3 is
> dated 1998. Unfortunately gud.el in emacs-20.3 does not work in
> XEmacs and I don't know much work it would need to make it work and
I've done the initial port of gud.el to XEmacs. It mostly works[1], but
it sorely lacks the functionality in gdbsrc.el. Making a gudsrc.el
mode is on my list of things to do.
It was in
ftp://altair.xemacs.org/pub/xemacs-futures/
when I was on the 'net.
It was delayed integration into the XEmacs packages pending 21.0
release.
I also have a ported cua-mode.el to integrate.
NOTE: The gud.el and cua-mode.el XEmacs portings are courtesy of
Altrasoft, Inc. Thank you Altrasoft.
Footnotes:
[1] I have a report that my port does not work on Solaris with dbx.

Hello
Please answer my question.
We maked a player in Linux with Lisp languaege ,but we dont know how to make
a UDP connection between our player and the server with Lisp languaege.
We looked in many sources ,but we didn't attain any affects.
Please say to us for making a UDP connection and geting and sending messages
with that Lisp languaege which orders .
Please explan with an example.
Thanks
Mrs Khodadadi

This bug report will be sent to the XEmacs Development Team,
not to your local site managers!!
Please write in English, because the XEmacs maintainers do not have
translators to read other languages for them.
In XEmacs 21.2 (beta22) "Mercedes" [Lucid] (i686-pc-linux) of Tue Nov 30 1999 on pegas.kazbek.ispras.ru
configured using `configure --with-pop'
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
My settings:
(custom-set-variables
'(gutter-visible-p t)
'(default-gutter-position (quote left))
'(buffers-tab-max-size 2))
1. With this settings xemacs opens scratch buffer with "*scratch*" tab
over the first line of the text. With the first cursor movement the
tab disappears, but the text beneath is still invisible. Of course,
it is not forever hidden, and there are more than one way to unhide
it, but still ...
2. After changing default-gutter-position(via custom) from 'left to
'top or 'bottom, ugly blue(on my HP-400 workstation) regions are left
in the current buffer window. These regiona are about 4 chars wide
and attached to the left margin.
Recent keystrokes:
misc-user
Recent messages (most recent first):
Parsing /home/npakoulin/.mailrc...
Loading mail-abbrevs...done
Loading mail-abbrevs...
Loading emacsbug...done
Loading emacsbug...
Loading /home/npakoulin/.e/.xemacs-init...done
Loading ~/.abbrev_defs...done
Loading ~/.abbrev_defs...
Loading time...done
Loading time...

as of CVS some days ago:
uname -a: Linux labyrinth 2.2.5 #1 Tue Oct 12 17:50:33 CEST 1999 i686
unknown
./configure '--with-mule' '--with-widgets=athena3d'
'--with-dialogs=athena3d'
XEmacs 21.2-b19 "Shinjuku" configured for `i686-pc-linux'.
Where should the build process find the source code?
/opt/src/xemacs
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 support for JPEG image handling.
Compiling in support for TIFF image handling.
Compiling in 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.
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.
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: ---------------------------------------------------------
Lisp backtrace follows:
# (condition-case ... . error)
# (catch top-level ...)
--------
mmmm.... not much, and i do not have a core because it was not enabled.
i have NO clue why it crashed or when or what it was doing.
i was just focusing it back for the thousandth time with my autoraise
mouse on X.
i will cvs update and try to run it with core enabled and see what
happens.
--
# Stef Epardaud, # There is no limit to the power of computing ...
# Java Defeater # ... except men maybe ?
# Rotterdam # Lunatech Research,
# NETHERLANDS # soon we will drop the searching for the finding...
# #

I have a small function which toggles the default font between the
normal font and "nil2", which lets me conveniently put aside an XEmacs
that's not currently interesting. Unfortunately, while XEmacs as a
whole reacts to this by smallifying as the text reduces to the "nil2"
font, the font used in the tabs continues to be original size.

I'm stumped.
fill-region-as-paragraph works perfectly (afaik) when not using pdump
or not using mule. Only pdump+mule is broken. While I can mostly
follow the lisp code when featurep 'mule returns nil, I'm overweirded
when the kinsoku junk comes into play.
Could someone more knowledgeable about lisp point me to the
subr/variable/whatever that does not behave the way it should so that
I can trace the problem at the C level?
OG.

This is not critical to me, since I kept a working copy of an older
21.2 beta to actually use ... but I haven't been able to use a current
CVS beta for at least a month because, in gnus, they crash after no
more than ten minutes with errors like these:
xemacs: X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 12 (X_ConfigureWindow)
Value in failed request: 0x0
Serial number of failed request: 79626
Current serial number in output stream: 79659
Error: Widget *Article* has zero width and/or height
--
Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA
mharnois(a)willinet.net aa0bt(a)aa0bt.ampr.org
"Waiter, there's no fly in my soup!" - Kermit the Frog

>>>>> "Robert" == Robert Pluim <rpluim(a)bigfoot.com> writes:
Robert> Hrvoje Niksic writes:
>> Oscar Figueiredo <Oscar.Figueiredo(a)di.epfl.ch> writes:
>>
>> > *** IMPORTANT NOTE ***
>> > Due to the function renaming, this patch introduces an incompatible
>> > change that breaks the packages using the current LDAP API, most
>> > notably EUDC and W3.
>>
>> Renaming doesn't necessarily entail breaking backward compatibility.
>> If you want to be kind to your users, define functions with old names
>> that do nothing except call the new functions.
Robert> Wouldn't define-{obsolete,compatible}-function-alias be better here?
Robert> Or are they intended only for 'core' emacs functions?
Of course I've been concerned by this problem. But I don't know what to do for
the particular case of ldap-search. Currently ldap-search is the name of the
high-level search function (vs. ldap-search-internal which is the low-level
function). But according to the recent discussion on the subject, what we want
is the low-level function to be called ldap-search and the high-level one
called something else (my patch proposes ldap-search-entries). In this
particular case I don't know how to rename backward compatible. That's the
reason why I didn't provide compatibility aliases at all, compatibility will be
broken anyway... :-((
I am not satisfied by this but I've seen no workaround. I don't know how many
packages are currently using the LDAP API. I know of two: EUDC which I
maintain myself and W3. As I said, I can provide a compatible version of EUDC
as soon as necessary and I guess Bill is responsive enough these days to do the
same. I just hope the consequences of this incompatible change will be minor,
the LDAP API has been out since version 21.0 only.
Oscar