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

Cygwin 64-bit compilation experience? 9 years, 10 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

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

Re: Cygwin 64-bit compilation experience? 10 years, 10 months

Henry S. Thompson

Mats Lidell writes: > M-x shell-command works with ls. Right, so it really does look like this is the (pseudo-)tty stuff, not sub-process as such. 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

1 participants
0 comments

keyboard macros 10 years, 10 months

steven Mitchell

Is there a way to get a list of all named-keyboard macros in memory? Some may be defined and/or loaded from the init.el and some may be created, named, during the current session and not yet saved to a file. Some may be named and assigned to keys, and some might not be assigned to a key sequence yet. Not sure how to identify them to compile a list of them... Thanks, Steve Mitchell _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

3 participants
2 comments

possible bug in redisplay 10 years, 10 months

Julian Bradfield

A couple of days ago, my XEmacs crashed when I did something as innocent as narrowing-to-region and then M-<. I haven't seen this before, but it turned out to be repeatable - but heavily dependent on the exact file, region, font setup, etc, so I didn't reproduce it in a vanilla standard XEmacs. The crash was an assertion failure in the first check in extents.c:extent_fragment_update() Tracing back the reason for this, it was that redisplay.c:start_with_line_at_pixpos() was returning a value before the start of the narrowed region. Of course, this is my heavily modified Unicode-internal fork of 21.4, but as far as I can see, nothing I've done is implicated in the problem. One return point of start_with_line_at_pixpos() is inside the while ( cur_elt < 0 ) { ... } loop, and at the point it is checked whether cur_pos is before BUF_BEGV before returning it. There's another return point inside if (pixheight < 0) {...} before that loop, in which either prev_pos or cur_pos is returned, without checking whether they're less than BUF_BEGV. It may be that prev_pos can't be, because it would have been caught by the other check in the previous iteration of the main loop; but I can't see why cur_pos might not be, as indeed it was in the crash I saw. I added a check at that point, and the crash went away. If this is a bug, rather than a subtle consequence of an assumption being broken by some other bug I've introduced, it probably applies to all current XEmacsen, as this code is still current in the latest 21.5. However, my understanding of the redisplay code is, to put it mildly, limited. This is what I've done: *** redisplay.c 2012/06/03 15:16:04 1.42 --- redisplay.c 2014/01/01 11:01:33 1.43 *************** *** 8181,8192 **** if (pixheight < 0) { w->line_cache_validation_override--; if (-pixheight > point_line_height) /* We can't make the target line cover pixpos, so put it above pixpos. That way it will at least be visible. */ ! return prev_pos; else ! return cur_pos; } cur_elt--; --- 8181,8195 ---- if (pixheight < 0) { w->line_cache_validation_override--; + /* I see no reason why cur_pos can't be before BEGV + here, so check for it. It's not clear to me whether + prev_pos could be before BEGV, so check that as well. */ if (-pixheight > point_line_height) /* We can't make the target line cover pixpos, so put it above pixpos. That way it will at least be visible. */ ! return (prev_pos <= BUF_BEGV (b)) ? BUF_BEGV (b) : prev_pos; else ! return (cur_pos <= BUF_BEGV (b)) ? BUF_BEGV (b) : cur_pos; } cur_elt--; _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

3 participants
3 comments

XEmacs Packages have been pre-released (2014-01-07-09) 10 years, 10 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: =========================== edit-utils-2.52-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 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-base-2.39-pkg.tar.gz upstream version: none xemacs-devel-1.82-pkg.tar.gz upstream version: none Detailed Changes: ================ - ------- ChangeLog Entries from xemacs-packages/edit-utils/ChangeLog ------- 2014-01-07 Norbert Koch <viteno(a)xemacs.org> * Makefile (VERSION): XEmacs package 2.52 released. 2013-1-1 Steve Mitchell <smitchel(a)bnin.net> Byrel Mitchell <byrel.mitchell(a)gmail.com> * register-menu.el: Added new package Allows easy access to register functionality, including in-menu previews of register contents, bookmarking, etc. * register-toolbar.el: Added new package Allows easy access to copy and pasting from 10 registers, including from columnar blocks. * Makefile (ELCS,DATA_FILES): added new files * rt: added icon files for register toolbar. 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) iD8DBQFSy8Jd7yJLt8ORD7cRAv/jAJ9dRsYilI5bmStGlHwG/VKWs5rQhQCeNxvA HUi2nJ2LThW9qo2YvH9N5dg= =nzcB -----END PGP SIGNATURE----- _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Icon-themes 10 years, 10 months

Byrel Mitchell

Well, last year Steve Mitchell and I wrote a package for theming the toolbar. We extracted several icon themes from existing open-source (LGPL or GPLv3) icon libraries, and made on derivative light-on-dark theme from the default XEmacs icon theme. We've tested this with Windows and Linux, latest stable, lastest beta in linux, and the latest beta with a binary windows release (21.5.29) in windows. No crashes, loads, and compiles fine. In windows the plain-text theme doesn't actually work; the windows glyph system doesn't support a simple text string input. Originally we were going to put this into edit-utils, and even had the initial icon-themes.el in there already, with only the default and text icons selectable. We just finished refactoring it all into a stand-alone package and testing it. The current repo is on bitbucket: hg(a)bitbucket.org/skm/icon-themes. I'm not sure what the procedure is for getting a package double-checked and added; the only change needed to the xemacs-packages repo is adding icon-themes to the list in xemacs-packages/Makefile. Let me know if you find any bugs/issues! Best, Byrel _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Edit-utils register interface addition 10 years, 10 months

Byrel Mitchell

Norbert, Steve and I committed a couple of (optional) register user interface utilities to edit-utils. We wrote these last year, and have been doing minor revisions, etc. since. Hopefully this can expose a bit more of XEmac's functionality to casual users. Register Menu is a toplevel menu for register access. It provides an in-menu preview of register contents, and options for most register interaction implemented in XEmacs. This menu defaults to off, and can be toggled with a button in Options->Menubars, or via it's customize group (register-menu) Register Toolbar is a minor mode which inserts 11 toolbar buttons for register access; a mode button, which toggles between copy, insert, move, etc. and 10 register buttons for the first ten registers (corresponding to 0x00-0x09 in ascii). The buttons highlight or gray out depending on zmacs-region, whether registers are currently full, etc. We generated a set of icons using netpbm tools. These are optimized for a light on dark color scheme; making a dark on light set should be fairly simple if desired. We've tested these on several versions (stable and beta) of XEmacs on Windows and Linux. If anyone runs into any issues, please let us know! Some of the functionality is cased out in older versions of XEmacs (including current stable), which don't support a few features (like :active tags for submenus). Best, Byrel Mitchell _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 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 January 2014