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
Vin Shelton <acs(a)alumni.princeton.edu> writes:
> Michael -
Hi Vin,
> Thanks for the update. Unfortunately, as you suspected, there's an
> issue building the package repo. I'm using latest 21.4 from hg, and
> I'm getting a failure in ediff-vers.el. This compiled fine before
> your changes; I'm guessing it has something to do with autoloads.
>
> The actual error is:
>
> byte-compile-report-error((file-error "Cannot open load file" "executable"))
>
> which seems kinda weird. I'm investigating now, but in case someone
> has some ideas, I'd be happy for any pointers.
In (the new) tramp-compat.el, there is the following code snippet:
--8<---------------cut here---------------start------------->8---
(eval-and-compile
;; Some packages must be required for XEmacs, because we compile
;; with -no-autoloads.
(when (featurep 'xemacs)
(require 'cus-edit)
(require 'env)
(require 'executable)
(require 'outline)
(require 'passwd)
(require 'pp)
(require 'regexp-opt))
(require 'advice)
(require 'custom)
(require 'format-spec)
(require 'shell)
(require 'tramp-loaddefs)
...
--8<---------------cut here---------------end--------------->8---
I have added the "(when (featurep 'xemacs) ..." form, because there were
compilation errors otherwise in my local environment. But I'm open to
any enhancement.
> Thanks,
> Vin
Best regards, Michael.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hello
b
I am desperately looking for another x-symbol user, who could confirm
the following, which I have tested with xemacs -vanilla and then calling
x-symbol-initialize
There is *no* way to have the variable x-symbol-8bits enabled by default.
Every time I open a latex file, this variable is nil.
The variable can be set:
- I have tried to set it via customize to t.
- By using setq in the init file.
- By putting it into the LaTeX-mode-hook
- buy using Local variables like this
,----
|
| %%% Local Variables:
| %%% mode: LaTeX
| %%% TeX-master: t
| %%% x-symbol-8bits: t
| %%% x-symbol-unique: t
| %%% End:
`----
- set the variable interactively in the buffer.
*Only* the last method works, all the other fail, I even get
,----
|
| `x-symbol-8bits' is a variable declared in Lisp.
| -- loaded from "x-symbol-hooks"
|
| Value: nil
|
| This value is specific to the current buffer.
|
| Default-value: t
`----
I am desperate. Any idea?
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Meant to send this to the whole list:
>> > (font-menu-set-font "courier nil 140).
>> > It almost works, except the alignment in shell buffers is not nice.
> Lynn> result is that it doesn't use the right font, and it looks like it's
> Lynn> a proportional font, and when doing something like ls -AF in a
> Lynn> large directory it doesn't line up in columns the right way.
> Since you've configured with xft, we should figure out why
> fc-name-unparse doesn't seem to exist for you.
Okay, I'm game. Not today or maybe even the rest of this week,
but this list has been so helpful in getting me over to the beta the
least I can do is do a little more testing. (Like the good old days.)
> set up fonts for xft has fixed most of the font issues I've had.
> (I've had to tweak it a bit on Ubuntu because some fonts were coming
> up too big.
Speaking of which, I tried to compile on my Ubuntu machine, and
it flat out didn't compile. I've been ignoring it. I need to rerun the
exercise and take notes on what actually happened. I'll get around
to that another time. I have worse problems on my Ubuntu machine
than just XEmacs. It's marginally functional.
But first, if someone could tell me what sorts of things I can do to test
for what's wrong on my iMac, I should have some cycles free to dig
in sometime early next week.
Thanks.
--
Lynn David Newton
Columbus, Ohio
neologisticsediting.comlynndavidnewton.com
--
Lynn David Newton
Columbus, Ohio
neologisticsediting.comlynndavidnewton.com
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Like most fairly advanced users, I'm barely conscious that the menus and toolbar
are even there. Once in a while I'll explore them. The only thing I've ever used
them for is to go to the Options menu, particularly to set faces and the like.
And when I do, some sort of sausage is ground out the other end.
So my question, a general one with a specific case in mind is: Is there a way
to find out, even if it means prowling around in source somewhere, what
elisp is executed when a user selects a given menu choice?
This last couple of weeks I've spent combing over my XEmacs configuration
from top to bottom has been extremely productive for me, buit there is just
one more thing that I can't figure out. Everything looks right when I come
up except the font is too small in pretty much all buffers. I've found that
if I go to Options => Font Size and select 14, everything is fine from then
on. It seems logical to suppose if I knew what elisp magic happens when
I do that, I can put that at the end of my init files and not have to do it
with the menus.
And in case anyone is wondering, yes I have the default face set with
the size. In fact, in every face I've customized, I have the size set, but
it doesn't make any difference until I do it from that menu option.
(custom-set-faces
'(default ((t (:foreground "gray65" :background "black" :size "14"
:family "courier"))) t) ... more )
I'm down to the nitpicky stuff now.
--
Lynn David Newton
Columbus, Ohio
neologisticsediting.comlynndavidnewton.com
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
ACTIVITY SUMMARY (2013-01-22 - 2013-01-29)
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.
553 open ( +0) / 294 closed ( +0) / 847 total ( +0)
Open issues with patches: 13
Average duration of open issues: 1349 days.
Median duration of open issues: 1432 days.
Open Issues Breakdown
new 233 ( +0)
deferred 6 ( +0)
napping 3 ( +0)
verified 57 ( +0)
assigned 153 ( +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