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
Hi,
attached is a patch which provides basic syntax hilighting for the
clearcase-edcs-mode. For me it works fine with XEmacs 21.4.22 and 21.5.32.
Maybe you or others find it useful, even if my lisp knowledge is not the best.
Regards,
Thomas Viehweger
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
ACTIVITY SUMMARY (2013-04-23 - 2013-04-30)
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.
558 open ( +0) / 296 closed ( +0) / 854 total ( +0)
Open issues with patches: 13
Average duration of open issues: 1424 days.
Median duration of open issues: 1522 days.
Open Issues Breakdown
new 239 ( +0)
deferred 6 ( +0)
napping 3 ( +0)
verified 57 ( +0)
assigned 152 ( +0)
committed 19 ( +0)
documented 3 ( +0)
done/needs work 17 ( +0)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hello
I use this function a lot, but I also checkin jumping branches
1.1 1.2 1.3 1.4
2.1 2.2
But then (vc-annotate-revision-previous-to-line) can go back from 2.2 to
2.1 but not to 1.4.
Anybody knows about a hack to achieve jumping from 2.1 to 1.4.
thanks
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message
Hey Everyone!
I heard that you guys were applying to be a mentoring organisation in
this year's Google Summer of Code. That's awesome, and we all (SXEmacs)
hope it works out great for you.
I got together with my guys to see if there was anything that we could
do to help out. Not sure if there is much we could do really, but we
did come up with a number of ideas for possible projects.
New Packages:
------------
o A decent git interface. I've heard about this thing called
"magit" that folks like John Wiegley swear by. I had a quick
look at it once and it was very GNU/Emacs-centric.
o Sharing content on social media. For example, you read something
awesome in one of your RSS feeds in Gnus, it'd be cool if you
could post a link to the article on Twitter or Facebook directly
from *Emacs.
o An OAuth package. I think GNU/Emacs has this already, so port.
Oh, and this one would be needed for the previous anyway. :-)
o A CalDav package so I can sync my Google Calendar with my calendar
in SXEmacs.
o A spreadsheet package.
o A Dropbox client. The Tramp folks are thinking of doing something
with this.
o An Evernote package. Save buffers, files, regions to Evernote.
Also view/edit existing notes.
o An Mplayer client/skin/player to watch and control video from
mplayer embedded into an XEmacs buffer.
Core Enhancements:
-----------------
o Convert to/from various open document formats.
o LLVM compiled elisp, instead of bytecode.
I had to ask what "LLVM" was, so for the benefit of anyone else
that might not know, the answer I got was:
It's stands for "Low Level Virtual Machine", but the neat feature
of it is that there is a whole set of tools that then allow you to
do just in time compile and optimization.
Port From SXEmacs:
-----------------
(a lot of this I simply yanked directly from our website)
o FFI
o OpenSSL support
o Enhanced Number Types. Where we took XEmacs' "bignum" to the next
level. :-) Math is not really my thing, so have a look at...
http://www.sxemacs.org/docs/lispref/Enhanced-Number-Types.html
o Support for 256 colour XTerms and compatible terminals, and much
improved TTY font-locking.
o Embeddable keyboard macros (1a on JWZ' wishlist)
o Our Audio support. A couple parts of it are currently broken
because the ffmpeg folks moved the goal posts again (don't they
always?).
o Network Server Sockets. #'open-network-server-stream
o Cached and compiled regular expressions. You can get significant
speed ups from exhaustive caching of compiled regexps.
o Double Linked Lists. Unlike ordinary lists that only have hooks
into the head of the list (think car, cdr), a doubly linked list
has hooks into both the head and the tail of the list. This
means you can operate on both ends of a doubly linked list. You
can also traverse a dllist in both directions, tail-wards and
head-wards. Ordinary lists only allow for tail-wards traversal.
o Skip Lists. We have a basic implementation of Pugh's skip
lists. Their efficiency is overwhelming when compared to alists
or plists. They also perform better on insertion and removal
than large hash-tables (due to the resizing/rehashing which
takes place). They can be created almost as fast as lisp lists
and thus beat hash-tables there, too.
o Bloom Filters. Bloom filters are a hash-table like data structure
with the purpose of performing membership tests. Unlike hash-tables
bloom filters do not need to be resized despite the fact that they
can carry an arbitrarily large number of objects.
o Recursive directory traversal. SXEmacs has a recursive
implementation of #'directory-files called
#'directory-files-recur. It is amazingly fast, sometimes even
faster than GNU find(1).
OK, then, good luck with it all, guys. I really do hope that amazing
things come of this.
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| SXEmacs - The only _______ you'll ever need. |
| Fill in the blank, yes, it's THAT good! |
|------------------------------------<steve(a)sxemacs.org>---|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Steve Youngs dot Com <http://www.steveyoungs.com/>
Comment: The SXEmacs Project <http://www.sxemacs.org/>
Comment: EMchat - The SXEmacs IM client <http://www.emchat.org/>
Comment: the Reading Lamp <http://www.thereadinglamp.net/>
iEYEARECAAYFAlFiP0gACgkQHSfbS6lLMAMEOgCggZBjzKx2JBihxDXeF6PIEVK4
fUIAn3byKtqh8CdlxunOFcoCMfAnr0k9
=3S0u
-----END PGP SIGNATURE-----
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
ACTIVITY SUMMARY (2013-04-16 - 2013-04-23)
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.
558 open ( +1) / 296 closed ( +0) / 854 total ( +1)
Open issues with patches: 13
Average duration of open issues: 1417 days.
Median duration of open issues: 1515 days.
Open Issues Breakdown
new 239 ( +1)
deferred 6 ( +0)
napping 3 ( +0)
verified 57 ( +0)
assigned 152 ( +0)
committed 19 ( +0)
documented 3 ( +0)
done/needs work 17 ( +0)
Issues Created Or Reopened (1)
______________________________
DOC files should be versioned 2013-04-19
http://tracker.xemacs.org/XEmacs/its/issue856 created stephen
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
* Jerry James <james(a)xemacs.org> writes:
> /***** Bignum: conversions to/from arbitrary integer types *****/
I'm pretty sure that we (SXEmacs) can do something along these lines.
,----[ C-h f coerce-number RET ]
| `coerce-number' is a built-in function
| -- loaded from "/usr/src/sxemacs/sxemacs/src/ent/ent.c"
| (coerce-number NUMBER TYPE &optional PRECISION)
|
| Documentation:
| Convert NUMBER to the indicated type, possibly losing information.
| See `coerce'.
|
| TYPE is one of the symbols:
| - 'fixnum or 'int to convert to built-in integers
| - 'bigz or 'bignum to convert to bigz integers
| - 'integer to convert to the most suitable type out of
| 'bigz or 'int
|
| - 'bigq or 'ratio to convert to bigq fractions
| - 'rational to convert to the most suitable type out of
| 'bigq, 'bigz or 'int
|
| - 'float to convert to built-in floats
| - 'bigf or 'bigfloat to convert to bigf floats
| - 'bigfr to convert to bigfr floats
| - 'real to convert to the type indicated by
| `read-real-as' with a fallback to 'float
|
| - 'bigg to convert to a Gaussian
| - 'bigc to convert to a bigc complex number
|
| - 'quatern to convert to a Quaternion
|
| NOTE: Not all of these types may be supported.
|
| PRECISION is the number of bits of precision to use when converting to
| reals; it is ignored otherwise. If nil, the default precision is used.
|
| Note that some conversions lose information. No error is signaled in such
| cases; the information is silently lost.
`----
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| SXEmacs - The only _______ you'll ever need. |
| Fill in the blank, yes, it's THAT good! |
|------------------------------------<steve(a)sxemacs.org>---|
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Ar an naoú lá déag de mí Aibréan, scríobh Stephen J. Turnbull:
> Aidan Kehoe writes:
>
> > That means usually that the DOC file the binary thinks it should use
> > doesn’t correspond to its version. We should really version the DOC
> > files in the same we we version the .dmp files, and avoid over-writing
> > them.
>
> I agree that sounds plausible, but somebody on emacs-devel was arguing
> against versioning of DOC files any finer than the version of Emacs
> (Emacs uses a build number instead of our "corrupted timestamp").
Do you have a link, or a brief summary of what that person’s argument was?
> Tracker: issue856
--
‘Liston operated so fast that he once accidentally amputated an assistant’s
fingers along with a patient’s leg, […] The patient and the assistant both
died of sepsis, and a spectator reportedly died of shock, resulting in the
only known procedure with a 300% mortality.’ (Atul Gawande, NEJM, 2012)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta