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
Dear XEmacs Developers,
I recently got a large roundtuit dropped in my lap (my startup company
imploded), so I've spent a few days working on XEmacs native Windows
setup kits.
On Fri, Oct 31, 2014 at 8:45 PM, Biswajit Khandai <b_khandai(a)yahoo.com> wrote:
> I was assuming that the stable channel native windows binary will be built
> by "someone".... If that assumption is right, then the same "someone" could
> build the beta channel native windows binary. It may not be you,
> necessarily.
Your assumption is correct, but I am the only someone who builds these
kits. I will try to make a setup kit for every release, but it is
difficult for me to know how much time I will have for making setup
kits in between releases.
> However, if that assumption is wrong, I would like you to know that a heck
> of a lot of people use xemacs on Windows - maybe you underestimate the
> number of such people.
Dear Biswajit - thank you for your kind words. They certainly made me
feel like my efforts in this area have been well worthwhile.
I have re-made setup kits for 21.4.22, 21.5.34 and 21.4 latest and
21.5 latest. I will upload them this afternoon to ftp.xemacs.org.
I will be sending a small patch to XEmacs-patches to work around a
couple of difficulties building without TLS on native Windows. I have
not attempted to build with TLS as of yet.
- Vin
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
I've been working on TLS support for a little while, and now have what
seems to be working nss, openssl, and gnutls lstream implementations.
The next challenge is making those available via the Emacs interface,
since that is what consuming packages expect. I thought I'd give you
a snapshot of what I've done so far (attached), just in case I get
abducted by aliens who need some operating system work done.
If you see anything that seems wrong or wrong-headed, let me know.
It's still early enough to change direction if I'm doing something
gratuitously stupid.
--
Jerry James
http://www.jamezone.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
New machine, trying 64-bit cygwin, but no joy so far in compiling from
latest sources.
Too soon to say if I've just not got my environment right yet - so at
this point just checking -- has anyone made this work yet?
ht
--
Henry S. Thompson, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht(a)inf.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/
[mail from me _always_ has a .sig like this -- mail without it is forged spam]
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
xemacs is crashing at startup with fatal error (11) in opensuse 13.2
see terminal output & core info below:
wilko131@trein-pc:~/ntrein> xemacs
Warning: Missing charsets in String to FontSet conversion
Fatal error (11).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.
Your version of XEmacs was distributed with a PROBLEMS file that may
describe
your crash, and with luck a workaround. Please check it first, but do
report
the crash anyway.
Please report this bug by invoking M-x report-emacs-bug, or by selecting
`Send Bug Report' from the Help menu. If that won't work, send ordinary
email to `xemacs-beta(a)xemacs.org'. *MAKE SURE* to include this entire
output from this crash, especially including the Lisp backtrace, as well as
the XEmacs configuration from M-x describe-installation (or equivalently,
the file `Installation' in the top of the build tree).
*Please* try *hard* to obtain a C stack backtrace; without it, we are
unlikely
to be able to analyze the problem. Locate the core file produced as a
result
of this crash (often called `core' or `core.<process-id>', and located in
the directory in which you started XEmacs or your home directory), and type
gdb /usr/bin/xemacs core
then type `where' at the debugger prompt. No GDB on your system? You may
have DBX, or XDB, or SDB. (Ask your system administrator if you need help.)
If no core file was produced, enable them (often with `ulimit -c unlimited')
in case of future reoccurrence of the crash.
Lisp backtrace follows:
# (unwind-protect ...)
# (unwind-protect ...)
# bind (inhibit-quit)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
redisplay-frame(#<x-frame "XEmacs" on #<x-device on ":0.0" 0x2> 0x2>)
# bind (ext gutter-string val inhibit-read-only frame value message)
raw-append-progress-feedback("Fontifying *scratch*..." 0 #<x-frame
"XEmacs" on #<x-device on ":0.0" 0x2> 0x2>)
# bind (tmsg top frame value message label)
append-progress-feedback(font-lock "Fontifying *scratch*..." 0 nil)
# bind (frame value message label)
display-progress-feedback(font-lock "Fontifying *scratch*..." 0)
# bind (str)
# (unwind-protect ...)
# bind (args value fmt label)
progress-feedback-with-label(font-lock "Fontifying %s..." 0 "*scratch*")
# bind (maybe-loudly end beg)
font-lock-default-unfontify-region(1 1 t)
# bind (loudly end beg)
font-lock-unfontify-region(1 1 t)
# bind (was-on font-lock-verbose font-lock-message-threshold aborted)
# (unwind-protect ...)
font-lock-default-fontify-buffer()
# bind (font-lock-verbose)
font-lock-fontify-buffer()
# bind (on-p maximum-size arg)
font-lock-mode(1)
turn-on-font-lock()
# bind (explicit-defaults)
font-lock-set-defaults()
# (unwind-protect ...)
# bind (command-line-args-left)
command-line()
# (condition-case ... . ((t (byte-code " ��" [error-data data nil]
1))))
# bind (error-data)
normal-top-level()
# (condition-case ... . error)
# (catch top-level ...)
Segmentation fault (core dumped)
wilko131@trein-pc:~/ntrein> gdb /usr/bin/xemacs core
GNU gdb (GDB; openSUSE 13.2) 7.8
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://bugs.opensuse.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
warning: /etc/gdbinit.d/gdb-heap.py: No such file or directory
Reading symbols from /usr/bin/xemacs...(no debugging symbols found)...done.
[New LWP 2536]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `xemacs'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f7b234ad457 in kill () from /lib64/libc.so.6
Missing separate debuginfos, use: zypper install
xemacs-debuginfo-21.5.34-5.1.11.x86_64
(gdb) quit
Program editing is not possible using my favourate editor xemacs!!
Best wishes,
Wilko Keegstra
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
The Internals manual says:
,-------------------
| The C code is actually written in a dialect of C called "Clean C",
| meaning that it can be compiled, warning-free, with either a C or C++
| compiler.
`-------------------
This doesn't seem to be true for lwlib at least (not that I care about
lwlib specifically -- I just heppened to have used my standard
configure command line). Has anyone actually compiled XEmacs with a
C++ compiler recently and has a recipe that I could borrow?
Thanks
Marcus
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
More and more Emacs packages provide test files based on ert. It might
be useful to have ert provided as XEmacs package, because the tests from
GNU Emacs could run under XEmacs as well.
For example, for me as Tramp maintainer it would be very appreciated to
run ert under XEmacs, because today I cannot apply serious tests with
XEmacs before I release a new Tramp version. With ert, I could apply
tramp-test.el, and I would be much more confident that Tramp works also
with XEmacs.
Opinions?
Best regards, Michael.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hi,
When trying to sync a file to XEmacs I stumbled on that GNU Emacs
since version 24.1 (June 10, 2012) has support for lexical binding. We
seem to have some support for lexical binding (lexical-let) but that
is about it. Anyone who has had a look at how much effort it would
take to implement lexical binding?
I guess my immediate sync problems can probably be solved by going
back before the 21.4 release but I fear this will potentially be a
major incompatibility problem for us?
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hi all,
I'm sure you're all aware of the recent security flaws exposed with SSL3.
Therefore I have to ask, should we disable SSL2 and SSL3 support in ssl.el?
A little bit of reading shows that we can probably do this by adding
-no_ssl2 and -no_ssl3 to the ssl-program-arguments in ssl.el. I have
not tested it yet.
Are there other SSL interfaces exposed on the lisp level?
Johann
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta