December 2013 - XEmacs-Beta - XEmacs Mailing List Archives

GPLv3|L8R -- Status report - ready for inspection? 7 years, 5 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: Loading startup changes load-path? 10 years, 7 months

Michael Sperber

Mats Lidell <matsl(a)xemacs.org> writes: >>>>>> Michael Sperber <sperber(a)deinprogramm.de> writes: > >> It is intentional, to some degree: A long time ago, people screamed >> bloody murder at me when the startup paths didn't give configure'd >> paths precedence over those determined at run time. startup.el is just >> the first file that knows about those paths. So there's no good >> solution here that will make everybody happy, I'm afraid. > > But this happens while building the dump. What ever happens when you > start your xemacs is another thing I think. Couldn't this behavior be > controlled some how so that when building the dump we don't do this? It could be done. My point is that, at least once upon a time, there were people who didn't do it to be the way you want it to be. They do have a point in that the already complicated behavior gets more complicated when it's different at dump time. -- Regards, Mike _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

3 participants
6 comments

The help-buffer: Left-click, middle-click, right-click and return...!? 10 years, 9 months

The XEmacs Package Smoketest

Hi, I have had a look at the *Help:-buffer and have spotted some inconsistencies. It seems like left-click, middle-click, right-click and return is used differently. How should we have it? As it is now a referens to a variable sets an extent so that left-click and middle-click goes to the Documentation. Hitting return with the point in the extent does nothing. Finally, right-click will bring up a context menu with alternatives to go to Documentation, the source or Find tag. On the other hand, the source code link after "-- loaded from", does not set up a link for left-click. Here middle click and return works. Right click does nothing special, but could have had a menu for goto source. Wouldn't it be more consistent to let left-, middle-click and return do the same thing. Not that important but the context menu could include something useful for all links as well. Comments? Yours -- %% Mats _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

3 participants
6 comments

Bug fix in menubar.el 10 years, 10 months

Byrel Mitchell

A couple functions in menubar.el (add-menu-item-1, and delete-menu-item) assume that any operations on a top-level menu are operations on current-menubar, and so overwrite it, regardless of whether this menu was passed in as an argument. A test case: (progn (setq my-menu '(("File" "---"))) (add-submenu nil '("Edit" "Editting") nil my-menu) (delete-menu-item '("File") my-menu) (and (assoc "Edit" my-menu) (not (assoc "File" my-menu)))) This should return t; it removes one submenu and adds another. On a 21.5.34 system, however, it will return nil as both add-submenu and delete-menu-item will fail to operate on the local menu. (It won't in fact clobber the current menu; this example's safe.) I'm attaching a patch to fix this. Best, Byrel Mitchell _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Re: Ispell+Flyspell with UTF8 fonts 10 years, 11 months

Richard

On Tue, Dec 24, 2013 at 12:19:19AM +0100, Richard wrote: > On Mon, Dec 23, 2013 at 11:54:50PM +0100, Mats Lidell wrote: > > 2013/12/23 Aidan Kehoe <kehoea(a)parhasard.net> > > > > > > > > It can be both! I have a 75% merged ispell.el sitting around, which I > > > should > > > finish and commit. > > > > > > > Well I have similar problems with the native swedish chars åäö. I'm running > > XEmacs with locale sv_SE.utf8 but according to the suggested spellings when > > checkling a word with åäö in it somewhere another encoding seems to be > > introduced. In the ispell-dictionary-alist "svenska" is listed as > > iso-8859-1. Do I have a bad configuration or is there a bug here? Will your > > fixed ispell.el handle this case? > > I have > > $ echo $LANG > en_US.UTF-8 > > and for me ispell-dictionary-alist has non-utf charsets for all languages > as well. so I have now changed the iso-8851-1 into utf-8 and the error is gone. (copied lisp/ispell/ispell.el into my homedir, edited there and load at top of init.el) With that simple hack the list of characters doesn´t fit anymore the äöüß aren´t recognised as part of word. Simply changing the regexp to include aöüß instead of the previous definitions somehow failed for me, have to look at that closer. Richard --- Name and OpenPGP keys available from pgp key servers _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Ispell+Flyspell with UTF8 fonts 10 years, 11 months

Richard

Hi, I have recently installed Xemacs (21.5.34-1) on Fedora-19. When switching flyspell on it says "starting International Ispell xxx (but really Hunspell 1.3.2)" "ps" shows that hunspell is running as "hunspell -a -C -d de_DE" It seems to work till the moment that I type something with a special chars - typing "daß" results in: (1) (command/warning) Error in `post-command-hook' (resetting to nil): (args-out-of-range (ß 2)) Backtrace follows: # bind (inhibit-quit) string-match(" " "ß" 2) # bind (shift accept-list output) ispell-parse-output("ß") # bind (word poss end start flyspell-word cursor-location) # (unwind-protect ...) # bind (following) flyspell-word() # (unwind-protect ...) # (unwind-protect ...) # bind (command) flyspell-post-command-hook() # (unwind-protect ...) # (catch #<INTERNAL OBJECT (XEmacs bug?) (opaque-ptr, adr=0x0) 0x22> ...) # (unwind-protect ...) # (condition-case ... . error) # (catch top-level ...) The buffer mode-line is showing UTF8. I would be thankfull for any insight if this is a configuration error of me or a bug. Richard --- Name and OpenPGP keys available from pgp key servers _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

4 participants
5 comments

XEmacs Packages have been pre-released (2013-12-19-09) 10 years, 11 months

Norbert Koch

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey there everyone. I have just added the following packages to the 'Pre-Releases' directory: New Packages in Pre-Release: =========================== xemacs-base-2.39-pkg.tar.gz upstream version: none Previously Announced Packages Still in Pre-Release: ================================================== Sun-1.17-pkg.tar.gz upstream version: none cc-mode-1.74-pkg.tar.gz upstream version: 5.32.5 ede-1.04-pkg.tar.gz upstream version: 1.0pre4 ediff-1.82-pkg.tar.gz upstream version: 2.75 edit-utils-2.51-pkg.tar.gz upstream version: none efs-1.35-pkg.tar.gz upstream version: 1.24 eudc-1.41-pkg.tar.gz upstream version: 1.32 games-1.21-pkg.tar.gz upstream version: 2.00 gnus-1.95-pkg.tar.gz upstream version: 5.10.10 haskell-mode-1.12-pkg.tar.gz upstream version: 2.1 hyperbole-1.20-pkg.tar.gz upstream version: 5.0.5 leim-1.34-pkg.tar.gz upstream version: none mh-e-1.33-pkg.tar.gz upstream version: 7.4.2 misc-games-1.23-pkg.tar.gz upstream version: none mmm-mode-1.06-pkg.tar.gz upstream version: 0.4.8 net-utils-1.57-pkg.tar.gz upstream version: N/A pcl-cvs-1.71-pkg.tar.gz upstream version: R-2_9_9 pgg-1.08-pkg.tar.gz upstream version: 0.1 prog-modes-2.29-pkg.tar.gz upstream version: none ruby-modes-1.05-pkg.tar.gz upstream version: 1.8.7 speedbar-1.30-pkg.tar.gz upstream version: 1.0pre4 text-modes-2.01-pkg.tar.gz upstream version: none tramp-1.46-pkg.tar.gz upstream version: 2.2.8 w3-1.38-pkg.tar.gz upstream version: 4.0pre47 x-symbol-1.13-pkg.tar.gz upstream version: 4.5.1 xemacs-devel-1.82-pkg.tar.gz upstream version: none Detailed Changes: ================ - ------- ChangeLog Entries from xemacs-packages/xemacs-base/ChangeLog ------- 2013-12-19 Norbert Koch <viteno(a)xemacs.org> * Makefile (VERSION): XEmacs package 2.39 released. 2013-12-12 Michael Sperber <mike(a)xemacs.org> * compile.el (compilation-error-regexp-alist-alist): Make it autoloaded. 2013-12-14 Mats Lidell <matsl(a)xemacs.org> * Makefile (ELCS): Add rcfiles.elc so it is built and installed. Installing These: ================ Manually: - -------- 1) Download the packages that you want to install from: /ftp.xemacs.org:/pub/xemacs/beta/experimental/packages/ 2) Unpack them to: [1] /usr/local/lib/xemacs/xemacs-packages/ 3) Re-start XEmacs. Using XEmacs Package Tools (XEmacs 21.[245].x): - ---------------------------------------------- 1) Tools -> Packages -> Add Download Site -> Pre-Releases 2) Tools -> Packages -> List and Install 3) Select the packages you wish to install (there are brief instructions at the bottom of the packages buffer). 4) Packages -> Install/Remove Selected 5) Re-start XEmacs. Using XEmacs Package Tools (XEmacs 21.1.14): - ------------------------------------------- 1) Options -> Manage Packages -> Add Download Site -> Pre-Releases 2) Options -> Manage Packages -> List and Install 3 - 5) As per XEmacs 21.[245].x. Footnotes: [1] Note: Mule packages should be installed into: /usr/local/lib/xemacs/mule-packages/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFSsrrp7yJLt8ORD7cRAhg/AKCNFyxbfBOKhNXmPzWopwS8Z8rS4gCcCI17 HHcMr/OHrzSIzXwTvAUARJM= =ni2F -----END PGP SIGNATURE----- _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

[AC] Port `move-beginning-of-line', `move-end-of-line' from GNU Emacs 10 years, 11 months

Stephen J. Turnbull

Michael Sperber writes: > > Michael Sperber <sperber(a)deinprogramm.de> writes: > > > 2013-12-08 Michael Sperber <mike(a)xemacs.org> > > > > * subr-more.el (condition-case-unless-debug): Added, from GNU Emacs. > > (with-demoted-errors): Added, from GNU Emacs. Does it make sense (since we have a sane warning system) to repromote these to warnings, perhaps at a level that doesn't pop the *Warnings* buffer, but only logs the warning for future reference? Steve ? _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

2 participants
2 comments

question about `while-no-input' in xemacs-base/subr-more.el 10 years, 11 months

Stephen J. Turnbull

A blast from the past (March 2013). Michael Sperber writes: > ;;;###autoload > (defmacro while-no-input (&rest body) > "Execute BODY only as long as there's no pending input. > If input arrives, that ends the execution of BODY, > and `while-no-input' returns t. Quitting makes it return nil. > If BODY finishes, `while-no-input' returns whatever value BODY produced." > (declare (debug t) (indent 0)) > (let ((catch-sym (make-symbol "input"))) > `(with-local-quit > (catch ',catch-sym > (let ((throw-on-input ',catch-sym)) > (or (input-pending-p) > (progn ,＠body))))))) Does this actually work in XEmacs? AFAICS there's no symbol `throw-on-input' in XEmacs 21.5. Nor, again AFAICS, is there anything here that actually catches the `quit' signal. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

2 participants
1 comments

Re: Improving [was: Massaging] load-history 10 years, 11 months

Sean MacLennan

On Sun, 15 Dec 2013 10:32:09 +0900 "Stephen J. Turnbull" <stephen(a)xemacs.org> wrote: > Which probably isn't writable for most users (even today, it isn't for > me on *any* of my systems without su/sudo). I was thinking more of the case where somebody has installed XEmacs on the machine (using apt-get under Ubuntu for example). For most of these users they are probably not changing the source packages at all. I am much more likely to look up the source to see how it works (and maybe steal a few ideas) more than looking it up to change it. What I don't understand even after reading the thread Aidan posted is how massaging load-history would affect anybody. My simple use of find-function doesn't seem to be affected by changing load-history. In fact I (setq load-history nil) and describe-function and find-function work the same. Or did the last patch make load-history less important? Cheers, Sean _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

2 participants
2 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 December 2013