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 all,
The JDEE project appears to be coming back to life. There has been a
fair amount of discussion recently on their mailing list about a
reboot of the project. Lots of plans are being made. The question
has arisen as to whether they want their new effort to target both
Emacs and XEmacs, or just to target Emacs. Some are saying that
XEmacs support should be dropped, due to a perceived lack of interest
from XEmacs developers.
If any of you are interested in keeping JDEE going, join the discussion here:
https://lists.sourceforge.net/lists/listinfo/jdee-devel
Regards,
--
Jerry James
http://www.jamezone.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Greetings,
not sure whether or not this is the right list ... but here goes anyway:
Since a few days I'm trying in vain to install XEmacs under Cygwin. I
have freshly cloned the source repository from
https://bitbucket.org/xemacs/xemacs
and I have freshly updated Cygwin to its latest release. The problem
starts when compiling "src/alloc.c":
gcc -c -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts -Wpacked -Wpointer-arith -Wshadow -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wdeclaration-after-statement -Wunused-parameter -g -Demacs -I. -I/home/Rainer/repo/xemacs/src -DHAVE_CONFIG_H -fno-caller-saves alloc.c
In file included from events.h:574:0,
from alloc.c:49:
/usr/include/w32api/winnt.h:5170:15: error: two or more data types in declaration specifiers
DWORD64 Status;
^
/usr/include/w32api/winnt.h:5309:13: error: two or more data types in declaration specifiers
DWORD Status;
^
/usr/include/w32api/rpcdce.h:142:88: error: expected ';', ',' or ')' before 'int'
typedef void __RPC_API RPC_OBJECT_INQ_FN(UUID *ObjectUuid,UUID *TypeUuid,RPC_STATUS *Status);
^
In file included from /usr/include/w32api/rpc.h:82:0,
from /usr/include/w32api/wtypes.h:7,
from /usr/include/w32api/accctrl.h:10,
from /usr/include/w32api/aclapi.h:14,
from syswindows.h:206,
from sysfile.h:95,
from alloc.c:61:
/usr/include/w32api/rpcdce.h:210:51: error: unknown type name 'RPC_OBJECT_INQ_FN'
RPCRTAPI RPC_STATUS RPC_ENTRY RpcObjectSetInqFn(RPC_OBJECT_INQ_FN *InquiryFn);
^
In file included from events.h:574:0,
from alloc.c:49:
/usr/include/w32api/rpcdce.h:471:145: error: expected ';', ',' or ')' before 'int'
typedef void (__RPC_API *RPC_AUTH_KEY_RETRIEVAL_FN)(void *Arg,unsigned short *ServerPrincName,unsigned __LONG32 KeyVer,void **Key,RPC_STATUS *Status);
^
In file included from /usr/include/w32api/rpc.h:82:0,
from /usr/include/w32api/wtypes.h:7,
from /usr/include/w32api/accctrl.h:10,
from /usr/include/w32api/aclapi.h:14,
from syswindows.h:206,
from sysfile.h:95,
from alloc.c:61:
/usr/include/w32api/rpcdce.h:473:112: error: unknown type name 'RPC_AUTH_KEY_RETRIEVAL_FN'
RPCRTAPI RPC_STATUS RPC_ENTRY RpcServerRegisterAuthInfoA(RPC_CSTR ServerPrincName,unsigned __LONG32 AuthnSvc,RPC_AUTH_KEY_RETRIEVAL_FN GetKeyFn,void *Arg);
^
/usr/include/w32api/rpcdce.h:474:112: error: unknown type name 'RPC_AUTH_KEY_RETRIEVAL_FN'
RPCRTAPI RPC_STATUS RPC_ENTRY RpcServerRegisterAuthInfoW(RPC_WSTR ServerPrincName,unsigned __LONG32 AuthnSvc,RPC_AUTH_KEY_RETRIEVAL_FN GetKeyFn,void *Arg);
^
In file included from events.h:574:0,
from alloc.c:49:
/usr/include/w32api/rpcdce.h:513:81: error: expected ';', ',' or ')' before 'int'
RPCRTAPI signed int RPC_ENTRY UuidCompare(UUID *Uuid1,UUID *Uuid2,RPC_STATUS *Status);
^
/usr/include/w32api/rpcdce.h:515:72: error: expected ';', ',' or ')' before 'int'
RPCRTAPI int RPC_ENTRY UuidEqual(UUID *Uuid1,UUID *Uuid2,RPC_STATUS *Status);
^
/usr/include/w32api/rpcdce.h:516:69: error: expected ';', ',' or ')' before 'int'
RPCRTAPI unsigned short RPC_ENTRY UuidHash(UUID *Uuid,RPC_STATUS *Status);
^
/usr/include/w32api/rpcdce.h:517:59: error: expected ';', ',' or ')' before 'int'
RPCRTAPI int RPC_ENTRY UuidIsNil(UUID *Uuid,RPC_STATUS *Status);
^
/usr/include/w32api/rpcdce.h:547:140: error: expected ';', ',' or ')' before 'int'
typedef int (__RPC_API *RPC_MGMT_AUTHORIZATION_FN)(RPC_BINDING_HANDLE ClientBinding,unsigned __LONG32 RequestedMgmtOperation,RPC_STATUS *Status);
^
In file included from /usr/include/w32api/rpc.h:82:0,
from /usr/include/w32api/wtypes.h:7,
from /usr/include/w32api/accctrl.h:10,
from /usr/include/w32api/aclapi.h:14,
from syswindows.h:206,
from sysfile.h:95,
from alloc.c:61:
/usr/include/w32api/rpcdce.h:555:59: error: unknown type name 'RPC_MGMT_AUTHORIZATION_FN'
RPCRTAPI RPC_STATUS RPC_ENTRY RpcMgmtSetAuthorizationFn(RPC_MGMT_AUTHORIZATION_FN AuthorizationFn);
^
In file included from events.h:574:0,
from alloc.c:49:
/usr/include/w32api/rpcdcep.h:220:62: error: two or more data types in declaration specifiers
RPCRTAPI __LONG32 RPC_ENTRY I_RpcMapWin32Status(RPC_STATUS Status);
^
/usr/include/w32api/rpcasync.h:118:11: error: two or more data types in declaration specifiers
ULONG Status;
^
/usr/include/w32api/rpcnsip.h:21:81: error: two or more data types in declaration specifiers
RPCNSAPI void RPC_ENTRY I_RpcNsRaiseException(PRPC_MESSAGE Message,RPC_STATUS Status);
^
/usr/include/w32api/rpcndr.h:691:160: error: two or more data types in declaration specifiers
RPCRTAPI RPC_STATUS RPC_ENTRY NdrMapCommAndFaultStatus(PMIDL_STUB_MESSAGE pStubMsg,unsigned __LONG32 *pCommStatus,unsigned __LONG32 *pFaultStatus,RPC_STATUS Status);
^
/usr/include/w32api/aclapi.h:20:58: error: two or more data types in declaration specifiers
typedef VOID (*FN_PROGRESS) (LPWSTR pObjectName, DWORD Status, PPROG_INVOKE_SETTING pInvokeSetting, PVOID Args, WINBOOL SecuritySet);
^
In file included from sysfile.h:95:0,
from alloc.c:61:
syswindows.h:216:18: error: expected identifier or '(' before 'int'
# define Status int
^
In file included from alloc.c:41:0:
alloc.c: In function 'Fmake_byte_code':
lisp.h:2173:23: warning: value computed is not used [-Wunused-value]
((((len & 1) != 0) && (tortoise = XCDR (tortoise), 0)), \
^
I cannot even decide whether this is an XEmacs problem, a Cygwin prob-
lem, or my own problem, in that I'm missing some Cygwin package. Brows-
ing the FAQ and the other XEmacs documentation I found a hint to "in-
stall XFree86, which is available as part of the standard Cygwin in-
stallation", but when I searched the Cygwin packages for "XFree86" I on-
ly got a single match for a package which dates back to 2003 and which
is no longer installable via Cygwin's "setup*.exe". Besides, most (but
not all) libraries originally provided by this package are already in-
stalled in "/usr/lib/" as "*.dll.a" type libraries. Maybe, this part of
the XEmacs documentation is simply outdated.
Anyway, I would be really glad for any pointers shedding some light on
what's wrong or missing here.
Sincerely
Rainer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Installed the above on my Windows 8.1 box, pulled the latest
(cb65bfaf7110) revision, imported the project file, and built it (from
inside VS2015, Debug x86 build).
The attached patch file got me to the point where the compilation
succeeded, but linking is a catastrophe, and I don't understand how to
fix it. Large numbers of _-prefixed fns are showing is unavailable,
but I can't see where they're coming from.
Attached are the patches necessary to get the compilation to complete,
and the config.inc I'm using. Probably some naive mistake there,
needs a new pair of eyes.
Note that I picked VS2015 because it's the latest available, and what
the Python project has chosen, even though all you can download at the
moment is an RC.
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
Mats Lidell <matsl(a)xemacs.org> writes:
> Next thing will be to verify that I have a working native environment.
> Before summer it seems I installed VS2013. What do you think. Will
> that suffice as a test environment or do I need to go for the 2015
> version?
It would probably be better if you could install VS2015, it was pretty
painless (I unchecked _all_ the optional bits). There's clearly some
advantage in working in the same environment as we try to get things
working, as well as sharing with Python going forward. And VS2015
does seem to be what people will be loading if they start from
scratch. . .
Thanks,
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
Dr Rainer Woitok writes:
> On Saturday, 2015-07-25 14:15:23 +0100, you wrote:
>
>> ...
>> Can't reproduce. That is, pulling from bitbucket, tip is revision
>> cb65bfaf7110, compiling with gcc, I get a working xemacs.
>
> $ hg tip
> 5915:cb65bfaf7110 [tip] 2015-03-27 16:05:15 +0100 sperber(a)deinprogramm.de
>
> Speed up XEmacs on X.
>
> Avoid many calls to XQueryColor.
>
> $
>
>> ...
>> or better yet, follow the instructions for bug reporting at
>>
>> https://cygwin.com/problems.html
>>
>> and attach the cygcheck output as described therein.
>
> See attachment below.
OK, my 32-bit install has fallen behind a bit, whereas yours is right
up-to-date. I'll need to refresh mine and retry the xemacs build,
probably not until tomorrow at this point.
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
ACTIVITY SUMMARY (2015-07-14 - 2015-07-21)
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.
570 open ( +0) / 317 closed ( +0) / 887 total ( +0)
Open issues with patches: 13
Average duration of open issues: 2136 days.
Median duration of open issues: 2323 days.
Open Issues Breakdown
new 262 ( +0)
deferred 6 ( +0)
napping 3 ( +0)
verified 58 ( +0)
assigned 145 ( +0)
committed 19 ( +0)
documented 3 ( +0)
done/needs work 15 ( +0)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hi,
[Moved to XEmacs Beta.]
>>>>> Mike Kupfer <mike.kupfer(a)xemacs.org> writes:
> By the way, http://www.xemacs.org/Develop/jobs.html still refers to
> CVS.
What is the status or plan for our web documentation? I have some
vague memory that we said we would focus on that after the move to the
new host for our stuff. And what is the status on that move?
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hi FKtPp --
To deal with your last question first, the integerp change dates from XEmacs
20.0, in the mid-1990s. It is a design decision of most modern programming
languages that it is good and useful to be able to tell at runtime whether a
given object is a character, and thus should be displayed as ?a, ?á, ?گ or ?
南, or whether it is an integer, and thus should be displayed as a numeric
value.
Of the major languages in current use, C and friends don’t make the
distinction, and nor does GNU Emacs Lisp. XEmacs added it because emacs Lisp
is already, compared to C, so slow that the performance impact (checking for
whether something is an integer vs. a character) doesn’t matter, and because
it is very useful for interactive use and for debugging in this *text*
editor. Common Lisp, the other big influence on XEmacs, also has this
distinction; MacLisp, the Lisp that both GNU Emacs Lisp and Common Lisp are
ultimately based on, did not.
The Right Way to handle this kind of incompatible integerp usage is to
decide “is the code interested in this value as an integer, or as a
character?” and, if the latter, to replace #'integerp calls with
#'characterp. If it’s very difficult to tell if the writer is treating the
value as a character or as an integer, consider #'char-or-char-int-p.
The following comment from xsd-regexp.el suggests that it is most interested
in characters:
;;
;; The semantics of XSD regexps are defined in terms of Unicode.
;; Non-Unicode characters are not allowed in regular expressions and
;; will not match against the generated regular expressions. A
;; Unicode character means a character in one of the Mule charsets
;; ascii, latin-iso8859-1, mule-unicode-0100-24ff,
;; mule-unicode-2500-33ff, mule-unicode-e000-ffff, eight-bit-control
;; or a character translateable to such a character (i.e a character
;; for which `encode-char’ will return non-nil).
If it were interested in *Unicode values*, then yes, integerp would still be
appropriate, but there it’s interested in characters. Another hint that the
code is interested in the charater value is when they are compared with
something with character syntax, e.g. like (eq value ?a) or (memq ?b list).
As far as I can see xsd-regexp.el would be fine with characterp wherever
integerp is used; if you’ve any questions about other files, get in touch.
Best,
Aidan
Ar an cúigiú lá déag de mí Iúil, scríobh It's me FKtPp ;):
> Hi Aidian, Stephen,
>
> I find, in nxml code integerp is used to determind if its argument is a
> single character.
>
> To make the code work I changed this kind of intergerp call to characterp.
> Anyway nxml still mix use of character and integer type in someother logic.
> such as #'xsdre-range-list-to-char-alternative which will result a C level
> argument validation error of intergerp.
>
> My question is: how was this kind of incompatible usage of integerp usage
> handled in the past? Are there any good practice to follow?
>
> Would you mind tell the history of intergerp change if possiable? When was
> it change to be incompatible with FSF's one? and why.
>
> Thanks,
> Kai
--
‘Tramadol is further fed to cattle […] when working them […] (as draft
animals) so that the animals do not get tired quickly. …’
— Angewandte Chemie, Sept 2014, describing the social context of
(synthetic) tramadol having been found in Cameroon tree roots.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta