June 2011 - 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

Crash running Cygwin bash shell under XEmacs 12 years, 2 months

Mike Alexander

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

5 participants
5 comments

symbol's value as variable is void: allow-remote-paths 12 years, 10 months

Richard Cook

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

12 participants
51 comments

new icons--which ones? 13 years, 4 months

steven Mitchell

I'm in favor of new icons, and am willing to help. and have been working on some icons for myself for a while now, though understanding glyphs is taking me a while to accomplish, and the time it takes to make icons all from scratch. From scratch, because I see millions of icons in the internet with unknown licenses, and am cautious of stepping on somebody's toes by giving them out with XEmacs. I find I have never used some of the icons that are on the iconbar now, and wish there were icons for additional (different) tasks from the current set. 2 questions, 2 comments: 1. What do people want to do with icons? personally I use the one-button-click save as I save pretty frequently. What do other people actually want to use their iconbar for? 2. what icons should be included in a "complete set" of icons that we are talking about making here? 3. Also, I wonder if we did do some new icons if that would be enough. Wouldn't we also want to do some other components on the screen, like the iconbar background, and then make the menubar background to match it, then there are the gutters with the scroll bars, surely they should match the menubar too. Where do you stop? Do you implement full theming? All the sudden this looks like it would grow into a full facelift and take a large amount of all of our time. 4. If we do make a set (or several) of icons and update the screen's looks, it would be nice to make a lisp file to automatically change all the icons to a new set, and a lisp file to change all the icons back to the defaults, in case they get messed up by user modifications along the way. Steve Mitchell _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

5 participants
5 comments

Impossible to commit to packages 13 years, 4 months

Didier Verna

I cannot cvs ci to the packages today. Here's what I get: Can't do setuid (cannot exec sperl) cvs commit: Pre-commit check failed cvs [commit aborted]: correct above errors first! Here's my setup: CVS/Repository: XEmacs/packages CVS/Root: :ext:didier-guest＠cvs.debian.org:/cvs/xemacs -- Resistance is futile. You will be jazzimilated. Scientific site: http://www.lrde.epita.fr/~didier Music (Jazz) site: http://www.didierverna.com _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

5 participants
4 comments

encoding of etc/HELLO 13 years, 4 months

Jeff Sparkes

Aidan updated etc/HELLO to use iso-ir-196, which seems to my untrained eye to be a method to wedge iso-2022-7 into unicode, maybe? The new HELLO is based on the one in Emacs. XEmacs opens the Emacs HELLO and sets the buffer encoding to iso-2022-7. Opening the XEmacs HELLO gets the buffer encoding set to raw-text which doesn't display properly. Should the encoding be set in the variables at the end of the file? And what would that be? I've tried utf-8 and iso-2022-7, which has exhausted my meagre knowledge. -- Jeff Sparkes jsparkes(a)gmail.com _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Re: some utf8 chars are terrible small. 13 years, 5 months

Aidan Kehoe

Ar an t-ochtú lá is fiche de mí Meitheamh, scríobh Stephen J. Turnbull: > Aidan Kehoe writes: > > > Fontconfig is *far worse* in this issue, > > Far worse in what issue? Let me lay out my attitudes before I go into this. The first priority of redisplay in font selection is to display a glyph that is recognisable as the character that was handed to it. That is: · If the user has chosen a monospace font, and no glyph is available from that font in that size, choose a glyph from another monospace font in that size. If a variable-width font is the only font available with that glyph, it is correct to choose the glyph from that font, and, for example, break any ASCII-art that the user is attempting to display because of the changed width. Jamie Zawinski disagrees with this, and is wrong: https://bugzilla.mozilla.org/show_bug.cgi?id=156200 · Fonts with a big size disconnect, but with the corresponding glyph are preferable to blank squares. *After that*, once coverage has been addressed, it is appropriate to focus on what is a good fallback and what isn’t, in terms of size and style and so on. But the two problems are closely linked and it’s very easy to work on the second while the first regresses; I see this on Firefox on OS X currently, 3.X was better at finding appropriate glyphs than is Firefox 4.0.1. The XEmacs implementation of Fontconfig plus XFT doesn’t come close to server-side X11 in finding fonts for characters, mostly because the older ISO-2022-oriented Mule character approach suits server-side X11 fonts better. So for the specific example of TeX-escape-region.el you have the following comparison, with lots of blank squares under XFT and very very few with server-side fonts: http://www.parhasard.net/xemacs/TeX-escape-region-server-side.png http://www.parhasard.net/xemacs/TeX-escape-region-xft.png And once text gets a bit more exotic it becomes even starker: http://www.parhasard.net/xemacs/no-resources-xft.png http://www.parhasard.net/xemacs/no-resources-server-side-fonts.png http://www.parhasard.net/xemacs/no-resources-gtk-2-pango.png Note that the GTK screenshot reflect some local changes of mine, the other screenshots are with -vanilla and an empty X resource database. -- ‘Iodine deficiency was endemic in parts of the UK until, through what has been described as “an unplanned and accidental public health triumph”, iodine was added to cattle feed to improve milk production in the 1930s.’ (EN Pearce, Lancet, June 2011) _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Re: some utf8 chars are terrible small. 13 years, 5 months

Uwe Brauer

>> Regarding Re: some utf8 chars are terrible small.; Mike Kupfer <mike.kupfer(a)xemacs.org> adds: > Uwe Brauer wrote: >> I now tried >> M-: (set-face-font 'default >> "-*-courier-bold-r-*-*-*-180-*-*-*-*-*-*") >> deleting the 18 has a terrible effect on the font, chars to >> large and to thin, > That's not terribly surprising. On my system, that font specification > matches 4 fonts: > -adobe-courier-bold-r-normal--18-180-75-75-m-110-iso10646-1 > -adobe-courier-bold-r-normal--18-180-75-75-m-110-iso8859-1 > -adobe-courier-bold-r-normal--25-180-100-100-m-150-iso10646-1 > -adobe-courier-bold-r-normal--25-180-100-100-m-150-iso8859-1 xlsfonts -fn '-adobe-courier-bold-r-normal--18-180-75-75-m-110-iso10646-1' seems to tell me that the font is available. However when I select this font via (set-face-font 'default "-adobe-courier-bold-r-normal--18-180-75-75-m-110-iso10646-1") The \infty symbol did not change not change. Could you do an experiment? Download Aidan's pkg http://www.parhasard.net/xemacs/TeX-escape-region.el and convert the symbol using the function TeX-escape-region. And tell us what you see. Uwe _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

5 participants
6 comments

Summary of XEmacs Issue Tracking System Issues 13 years, 5 months

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2011-06-21 - 2011-06-28) XEmacs Issue Tracking System at http://tracker.xemacs.org/XEmacs/its/ To view or respond to any of the issues listed below, click on the issue number. Do NOT respond to this message. 526 open ( +0) / 249 closed ( +0) / 775 total ( +0) Open issues with patches: 12 Average duration of open issues: 886 days. Median duration of open issues: 941 days. Open Issues Breakdown new 190 ( +0) deferred 6 ( +0) napping 4 ( +0) verified 54 ( +0) assigned 151 ( +0) committed 28 ( +0) documented 3 ( +0) done/needs work 24 ( +0) Issues Now Closed (1) _____________________ [Bug: 21.5-b29] Ediff and emacs-internal coding system 741 days http://tracker.xemacs.org/XEmacs/its/issue529 stephen _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Changing ellipsis display for invisible lines? 13 years, 5 months

Uwe Brauer

Hello In Gnu emacs you change change it via (set-display-table-slot standard-display-table 4 ">>>") But this function does not exist in Xemacs and it looks a little tricky to port. I know (set-glyph-face invisible-text-glyph 'blue) but this is not what I want. Uwe Brauer _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

3 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 June 2011