Hello everybody,
I tried to update my xemacs-21.5.11 tree to 21.5.12 with the diff file
found in ftp mirrors, but all attempts failed (patch said "patch: ****
malformed patch at line 315").
I tried to skip several parts of the diff file without success (the main
problem ends in the part of "configure", which could not be skipped).
Did anyone encoutered the same problem? Could it be possible to re-generate
the patch file?
\bye
S.
--
MAKING MILHOUSE CRY IS NOT A SCIENCE PROJECT.
MAKING MILHOUSE CRY IS NOT A SCIENCE PROJECT.
MAKING MILHOUSE CRY IS NOT A SCIENCE PROJECT.
-+- Bart Simpson on chalkboard, episode #213

Hi,
Here comes yet another status report from the project of converting to
GPLv3 or later.
There are two lists of files below. The first list contains all files
that are in an undecided state. Please inspect: Do we need to do anything
with them. If so what?
The second list contains all files that we can leave untouched and the
reason for that. Please inspect: Are all reasons OK and correct?
Are we getting close to the were an inspection of the xemacs-gplv3
repository could be performed? With the intent that it that is OK we
could merge back to trunk and go GPLv3 or later?
----------------------------------------------------------------------
"CHANGES-beta"
"ChangeLog"
"PROBLEMS"
"README"
"README.GPLv3"
"etc/ChangeLog"
"etc/Emacs.ad"
"etc/InstallGuide"
"etc/NEWS"
"etc/ONEWS"
"etc/OONEWS"
"etc/README"
"etc/editclient.sh"
"etc/emacskeys.sco"
"etc/emacsstrs.sco"
"etc/gtkrc"
"etc/package-index.LATEST.gpg"
"etc/sample.Xresources"
"etc/xemacs.1"
"lib-src/ChangeLog"
"lib-src/README"
"lisp/ChangeLog"
"lisp/README"
"lisp/mule/mule-locale.txt"
"man/ChangeLog"
"man/README"
"modules/ChangeLog"
"modules/base64/Makefile"
"modules/common/configure-post.ac"
"modules/common/configure-pre.ac"
"modules/zlib/Makefile"
"nt/ChangeLog"
"nt/Emacs.ad.h"
"nt/Installation.el"
"nt/README"
"nt/Win32.cf"
"nt/lisp.ico"
"nt/site.def"
"nt/xemacs.dsp"
"nt/xemacs.dsw"
"src/ChangeLog"
"src/README"
"src/README.kkcc"
"src/m/README"
"src/s/README"
"src/s/freebsd.h"
"src/s/irix6-0.h"
"src/s/netbsd.h"
"src/s/sol2.h"
"tests/ChangeLog"
"tests/Dnd/README"
"tests/automated/README"
"version.sh.in"
----------------------------------------------------------------------
These files below are the files that we might be able to leave as
they are. The reason for why they need not to be changed is listed
after each file: (Some reasons are taken verbatim from private
communication or the "GPL version 3 source survey")
----------------------------------------------------------------------
"INSTALL" -> old FSF Documentation license
"config.guess" -> Part of config which is still GPLv2 or later. See "http://savannah.gnu.org/projects/config"
"config.sub" -> Part of config which is still GPLv2 or later. See "http://savannah.gnu.org/projects/config"
"etc/ETAGS.ChangeLog" -> BSD and GPL v2 or later
"etc/VEGETABLES" -> Not copyrightable.
"etc/XKeysymDB" -> MIT
"etc/ctags.1" -> Part of the etags distribution, which is not part of XEmacs.
"etc/custom/example-themes/ex-custom-file" -> Generated(!?) or GPL V2 or later?
"etc/etags.1" -> Part of the etags distribution, which is not part of XEmacs.
"etc/gnuattach.1" -> simple man link to gnuserv.1
"etc/gnuclient.1" -> simple man link to gnuserv.1
"etc/gnudoit.1" -> simple man link to gnuserv.1
"etc/refcard.ps.gz" -> Generated from refcard..tex
"etc/sample.Xdefaults" -> It is deprecated, so it can be removed but is only a three line reference to .Xresources
"etc/xemacs-X.ico" -> GPLv2 or later but there is not meta data for the file where this can be documented.
"info/dir" -> Generated(?)
"install-sh" -> MIT-style "no advertising" license
"lib-src/b2m.c" -> This is the version from GNU Emacs, so should be OK.
"lib-src/config.values.in" -> Generated.
"lib-src/emacs.csh" -> I don't think this even works with XEmacs ("emacsclient"), so I believe we can just delete it.
"lib-src/insert-data-in-exec.c" -> Compatible license.
"lib-src/mmencode.c" -> Compatible license.
"lisp/dump-paths.el" -> Empty file. Not copyrightable.
"lisp/term/bobcat.el" -> Emacs version has no explicit license declaration
"lisp/term/vt102.el" -> Emacs version has no explicit license declaration
"lisp/term/vt125.el" -> Emacs version has no explicit license declaration
"lisp/term/vt200.el" -> Emacs version has no explicit license declaration
"lisp/term/vt201.el" -> Emacs version has no explicit license declaration
"lisp/term/vt220.el" -> Emacs version has no explicit license declaration
"lisp/term/vt240.el" -> Emacs version has no explicit license declaration
"lisp/term/vt300.el" -> Emacs version has no explicit license declaration
"lisp/term/vt320.el" -> Emacs version has no explicit license declaration
"lisp/term/vt400.el" -> Emacs version has no explicit license declaration
"lisp/term/vt420.el" -> Emacs version has no explicit license declaration
"lock/.precious" -> Not copyrightable.
"modules/canna/install-sh" -> MIT
"modules/ldap/install-sh" -> MIT
"modules/postgresql/install-sh" -> MIT
"modules/sample/external/install-sh" -> MIT
"modules/sample/internal/install-sh" -> MIT
"move-if-change" -> Identical to GPLv3 or later Emacs version
"nt/Xmd.patch" -> GPLv2 or later but only a few lines
"nt/file.ico" -> MIT
"nt/minitar.c" -> Public domain
"nt/paths.h" -> Generated
"nt/xemacs.ico" -> GPLv2 or later but there is not meta data for the file where this can be documented.
"src/alloca.c" -> Public domain.
"src/depend" -> Generated
"src/emacs-marshals.c" -> Generated.
"src/emacs-widget-accessors.c" -> Generated.
"src/intl-auto-encap-win32.c" -> Generated.
"src/intl-auto-encap-win32.h" -> Generated.
"src/libsst.c" -> Compatible license.
"src/libsst.h" -> Compatible license.
"src/libst.h" -> Compatible copyright.
"src/linuxplay.c" -> Compatible license. (MIT-like)
"src/miscplay.c" -> Compatible license. (MIT-like)
"src/miscplay.h" -> Compatible license. (MIT-like)
"src/nas.c" -> Compatible license. (MIT-like)
"src/paths.h.in" -> Generated.
"src/s/openbsd.h" -> Too short. (< 10 lines)
"src/s/usg5-4-2.h" -> Too short. (< 10 lines)
"src/sunplay.c" -> Compatible copyright.
"tests/gtk/UNIMPLEMENTED" -> Does notes need a license?
"tests/tooltalk/beeps.el" -> Too short. (< 10 lines)
----------------------------------------------------------------------
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta

>>>>> "Paul" == Paul Krause <paulkrause1(a)mediaone.net> writes:
Paul> Adrian Aichner <adrian(a)xemacs.org> writes:
>> >> Do we want to make C-u M-x comment-region smarter?
>>
Paul> No! Make indentation smarter. If a comment begins in column
Paul> 1, don't
Paul> indent it when reindenting a region. This solves the
Paul> problem without
Paul> style-changes or hacks to comment-region.
>>
Paul> Have I overlooked anything?
>>
>> This, maybe?
>>
>> (Info-goto-node "(xemacs)Comments")
>>
>> Adrian
Paul> Could you be a little more specific? I don't what you're
Paul> referring to. Maybe this?
Paul> You can also use `Meta-;' to align an existing comment. If a line
Paul> already contains the string that starts comments, `M-;' just moves
Paul> point after it and re-indents it to the conventional place.
Paul> Exception:
Paul> comments starting in column 0 are not moved.
Yes, that, and also the following paragraph.
Some major modes have special rules for indenting certain kinds of
comments in certain contexts. For example, in Lisp code, comments which
start with two semicolons are indented as if they were lines of code,
instead of at the comment column. Comments which start with three
semicolons are supposed to start at the left margin. Emacs understands
these conventions by indenting a double-semicolon comment using TAB and
by not changing the indentation of a triple-semicolon comment at all.
You have a valid point, though.
single-; comments srarting in column 0 should not be moved and
comment-region would work as advertised!
You opened my eyes!
To All:
Isn't this what we should do?
Martin?
Stephen?
Best regards,
Adrian
Paul> The trouble is, it doesn't work as documented. Here's a sample.
Paul> ;;; header comment
Paul> ;; This function is just an example.
Paul> ;;; Here either two or three semicolons are appropriate.
Paul> (defun foo (x)
Paul> ;;; And now, the first part of the function:
Paul> (lambda (foo bar)
Paul> (if (foo bar)
Paul> 'bif
Paul> 'baz))
Paul> ;; The following line adds one.
Paul> (1+ x)) ; This line adds one.
Paul> ;; This function is just an example.
Paul> ;;; Here either two or three semicolons are appropriate.
Paul> (defun foo (x)
Paul> ;;; And now, the first part of the function:
Paul> ;; The following sexp is commented out using comment-region.
Paul> ; (lambda (foo bar)
Paul> ; (if (foo bar)
Paul> ; 'bif
Paul> ; 'baz))
Paul> ;; The following line adds one.
Paul> (1+ x)) ; This line adds one.
Paul> I get the same indentation using either M-; or C-M-q.
Paul> Testing using xemacs -vanilla on
Paul> XEmacs 21.2 (beta37) "Pan" (win32) of Sun Dec 03 2000 on PAULKRAUSE
Paul> as well as
Paul> XEmacs 21.0 "20 minutes to Nikko" (win32) of Fri Mar 26 1999 on
Paul> BLACKBIRD
Paul> (which I just happen to have lying around)
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/

I had a need to run something on my Windows machine today which
required a newer version of Cygwin than the ancient one that was
installed there. After I upgraded to the current version (1.7.9) I
can't start a shell in XEmacs (via M-X shell) using Cygwin's version of
bash. When I try to do so I get
Process bash.exe exited abnormally with code 35584
3 [sig] bash 1168 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
1556 [sig] bash 1168 open_stackdumpfile: Dumping stack trace to
bash.exe.stackdump
The stack dump is uninteresting except that the crash happens at offset
0x169220 in cygwin1.dll. It appears that this crash happens very early
on, before it's read /etc/profile. I see that I also have similar
stack dumps from other programs (find.exe and xargs.exe) in the XEmacs
directory all exactly the same.
I installed the latest Windows version of XEmacs from the installer at
<http://ftp.xemacs.org/pub/xemacs/binaries/win32/InnoSetup/XEmacs_Setup_21...>
and tried starting it with --vanilla. This didn't make any difference.
I also did a clean install of Cygwin 1.7.9 in case there was any crud
left around from the old version. This also didn't help. I'm running
on an old Dell with Windows XP Professional SP3. Perhaps that's the
problem. I probably should install Windows on my Mac under one of the
emulators, but that's more than I want to get into right now.
I've Googled around a bit and although others have seen this problem,
none of the solutions (mostly involving changing ownership of Cygwin
files and running rebaseall) did any good. The bash shell runs fine
when I start it using the .bat file installed by Cygwin, so it's
basically working, but it won't run in an XEmacs shell window.
Has anyone else seen this or know how to fix it? This little episode
reminds me why I avoid using Windows, but sometimes it's necessary.
Mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta

I was eaten by an Android for a few months Now I'm bored with my phone and
tablet.
<stephen(a)xemacs.org> wrote:
> Jeff Sparkes writes:
>
> > Sorry I disappeared for a few months, but I'm back working on Gtk.
>
> BTW, would you remind us (me, anyway) of your long-term plans? ISTR
> that right now you're working with the existing GTK+ v1 code. But
> that's going to be quite painful in the long run ... are you aiming at
> GTK+ v2 for the next big step, or GTK+ v3?
>
Its been using Gtk+2.X for a year now. My target is late Gnome 2 (gtk
2.29) with deprecated code references removed. (see
http://live.gnome.org/GnomeGoals/RemoveDeprecatedSymbols/GTK%2B). Then
XEmacs should also compile with Gtk 3. All of the drawing will be done
with cairo and pango. I have just started removing deprecated code, so
there's still a fair amount to redo. I'm tackling images right now.
It's currently good enough for me to use by default. Display is good (as
long as you use mono fonts), crashes are rare. I suspect events are lost
occasionally, the scrollbar can't be dragged and the mouse wheel doesn't
work, so it's not complete yet.
I haven't done much with the implementing widgets. In the longer term I'm
interested in using gnome introspection to implement the FFI bindings so
that all of the gnome libraries will accessible from elisp. Then the
widgets should be easy. :-)
--
Jeff Sparkes
jsparkes(a)gmail.com
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta

Hi!
I need to push the top-level ChangeLog in the package repository. This
fails due to cross-branch stuff. I suppose it would succeed if I could
push only this directory. Is this possible?
Thanks,
norbert.
--
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta

Hi, I compiled xemacs myself and installed into $HOME/xemacs-without-ipv6-cname
I then made a symlink of $HOME/xemacs-without-ipv6-cname/bin/xemacs to $HOME/bin/xemacs
I untarred the sumo tarball from http://ftp.xemacs.org/pub/xemacs/packages/xemacs-sumo-2009-02-17.tar.gz and untarred it into $HOME/xemacs-without-ipv6-cname/lib/xemacs, which made a directory called xemacs-packages there.
When I run xemacs, I am not able to update my packages.
I go to Tools -> Packages -> Set Download Site -> Official Releases -> US and choose US Main.
I then go "update package index" or any other command in the Tools menu about Packages and it complains: "symbol's value as variable is void: allow-remote-paths"
Can anyone help me with this? Thanks.
--
✐Richard Cook
✇ Lawrence Livermore National Laboratory
Bldg-453 Rm-4024, Mail Stop L-557
7000 East Avenue, Livermore, CA, 94550, USA
☎ (office) (925) 423-9605
☎ (fax) (925) 423-6961
---
Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept.
(opinions expressed herein are mine and not those of LLNL)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/mailman/listinfo/xemacs-beta

Hello
I just realized that Xemacs 21.5.29 Mule does not support
cp1255 (Hebrew windows) in file coding, while GNU emacs does
:(....
Are there plans to include this feature any time soon?
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta