November 2014 - XEmacs-Beta - XEmacs Mailing List Archives

GPLv3|L8R -- Status report - ready for inspection? 6 years, 10 months

Mats Lidell

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

4 participants
3 comments

Re: Innosetup binaries for 21.5.32 and later 8 years, 11 months

Vin Shelton

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

2 participants
1 comments

TLS implementation 9 years, 3 months

Jerry James

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

4 participants
12 comments

Cygwin 64-bit compilation experience? 9 years, 3 months

Henry S. Thompson

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

7 participants
35 comments

xemacs crashes on startup 9 years, 3 months

Wilko Keegstra

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

5 participants
13 comments

Disable SSL2 and SSL3 in ssl.el? 9 years, 3 months

Johann 'Myrkraverk' Oskarsson

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

4 participants
15 comments

High resolution XEmacs icon 9 years, 4 months

Jerry James

Hi all, The Fedora project is attempting to move from 32x32 or smaller icons up to at least 64x64, and preferably 256x256. They say that today's high-pixel-density displays make the old icons look either (a) really tiny or (b) fuzzy. Does anybody have, or have the capability to produce, a good looking XEmacs icon at 64x64 or (better) 256x256? Thank you. Non-artistically yours, -- Jerry James http://www.jamezone.org/ _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

4 participants
15 comments

Any built-in support for streams as delayed lists? 9 years, 4 months

Johann 'Myrkraverk' Oskarsson

Hi all, Is there any built-in support for streams of lisp objects? As discussed here: https://mitpress.mit.edu/sicp/full-text/sicp/book/node70.html Either in 21.4 or 21.5 may do. What I mean, is that given any old lisp function that wants a list, can I hand it a stream at it just works? I suspect the answer is "no." -- Johann I'm not from the internet, I just work there. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

3 participants
5 comments

xemacs crash 9 years, 4 months

Ulrich Deiters

Dear friends, after upgrading my OS from openSUSE 13.1 to 13.2, xemacs crashes immediately after invocation. Here is the printout: ukd＠iridium:~> architex/bin/architex UUU Warning: Missing charsets in String to FontSet conversion 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 ...) architex/bin/architex: Zeile 108: 2290 Speicherzugriffsfehler xemacs -l $ATXHOME/interface/init.el -geometry +0+0 some background information: "ArchiTeX" is a text processor that abuses XEmacs to write/edit XML documents, and then produces LaTeX and ultimately PostScript code. Here is the debugger analysis of the core file: ukd＠iridium:~> 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: Datei oder Verzeichnis nicht gefunden Reading symbols from /usr/bin/xemacs...(no debugging symbols found)...done. [New LWP 2438] [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 0x00007f6aa3fb2457 in kill () from /lib64/libc.so.6 Missing separate debuginfos, use: zypper install xemacs-debuginfo-21.5.34-5.1.11.x86_64 (gdb) where #0 0x00007f6aa3fb2457 in kill () from /lib64/libc.so.6 #1 0x00000000004a2a53 in fatal_error_signal () #2 <signal handler called> #3 0x00007f6aa540d64e in XDrawLine () from /usr/lib64/libX11.so.6 #4 0x0000000000615bc0 in ?? () #5 0x00007f6aa595a4d4 in ?? () from /usr/lib64/libXt.so.6 #6 0x00007f6aa595c0ea in XtDispatchEventToWidget () from /usr/lib64/libXt.so.6 #7 0x00007f6aa595c618 in ?? () from /usr/lib64/libXt.so.6 #8 0x00007f6aa595c769 in XtDispatchEvent () from /usr/lib64/libXt.so.6 #9 0x00007f6aa5967c7e in XtAppProcessEvent () from /usr/lib64/libXt.so.6 #10 0x00000000005e3fc1 in ?? () #11 0x00000000005e910d in check_if_pending_expose_event () #12 0x00000000005f7007 in ?? () #13 0x000000000057a863 in redisplay_output_window () #14 0x000000000057235d in ?? () #15 0x0000000000572f24 in redisplay_frame () #16 0x0000000000573bde in Fredisplay_frame () #17 0x00000000004adcf4 in Ffuncall () #18 0x0000000000473061 in execute_optimized_program () #19 0x00000000004adeae in Ffuncall () #20 0x0000000000473061 in execute_optimized_program () #21 0x00000000004adeae in Ffuncall () #22 0x0000000000473061 in execute_optimized_program () ---Type <return> to continue, or q <return> to quit--- Can you make sense out of this? Kind regards, Ulrich Deiters -- Prof. Dr. Ulrich K. Deiters ______________________________________ Institut f. Physikalische Chemie \ Luxemburger Str. 116, D-50939 Koeln Universitaet zu Koeln /\/\... \ Tel. +49 (0)221 470-4543, Fax -4900 _______________________L|L|__|_____\ http://www.uni-koeln.de/deiters/ _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

2 participants
1 comments

Hooking into the event loop? 9 years, 4 months

Johann 'Myrkraverk' Oskarsson

Hi all, Is there any way to hook into the event loop? Either with lisp code, or C. I have some things I'd like to do, but doing it well requires some way to add stuff into the event loop, and it's not exactly documented how it works (at least in the 21.4 codebase). If anyone is aware of significant changes in event handling between 21.4 and 21.5, I'd also like to know. If there is no way to do it, does anyone know what's involved to add such hooks? Johann _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

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