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
Hello
In GNU emacs I can use the following setting
(custom-set-faces
'(default ((t (:family "DejaVu Sans Mono" :foundry "unknown" :slant
normal :weight normal :height 143 :width normal)))))
And Emacs uses the DejaVu font which is installed in my Ubuntu
distribution. I can also use the font in a xterm.
However when I run xfontsel I do not find this font and therefore do not
know how to use in it Xemacs.
Did anybody in a similar environment get this font to work in Xemacs?
Thanks
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Is there a gdb mode that works with lldb? OSX no longer has gdb and
uses lldb instead. Is there some way to get gdb mode on xemacs to
work with lldb?
--
Ray
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hi,
* Background
Yesterday I had a look at the latest version of go-mode.el. Support
for different IDEs have been move out of the golang source tree and
go-mode.el is now it is own repo at github.
To my delight some small adjustments for XEmacs are still in there so
I'm considering upgrading our version in the package tree to this
version. However there is a small but. It has now a dependency on a
file find-file.el which we don't have.
To give you a quick feel for what it does.
;;; find-file.el --- find a file corresponding to this one given a pattern
[...]
;; PURPOSE:
;; This package features a function called ff-find-other-file, which performs
;; the following function:
;;
;; When in a .c file, find the first corresponding .h file in a set
;; of directories and display it, and vice-versa from the .h file.
[...]
* Questions
- Any views or comments on adding this file to the edit-utils?
- The easiest thing would be to just take the current version, which
is GPLV3 or later, and use that. We do these things at such a low
frequency so I forget how we reasoned the last time we added files
from GNU Emacs. It seems we already have GPLV3 or later files in
the tree so that would be considered OK since that is the way we
are heading. Right?
- Just byte compiling the file reveals only warnings about
purecopy. We seem to keep calls to purcopy in other files so I
suppose that is how we should do it now also?
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
ACTIVITY SUMMARY (2015-08-18 - 2015-08-25)
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: 2171 days.
Median duration of open issues: 2358 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
Uwe Brauer writes:
> Ok, so I have to dig more into the code or hope that somebody in
> xemacs-beta could point me out what is the GNU emacs equivalent to those
> functions. I still wonder how x-symbol could have worked under GNU
> emacs 21, given that extents and specifiers did not exist neither for
> emacs 21.
AFAIK you're the only user left, and you've spent quite a bit of time,
both yours and others', on trying to keep this code working (which was
idiosyncratic when written, to say the least). I'm giving up. This
is my last post, ever, on x-symbol (except if necessary to veto
changes to XEmacs :-/ ).
Extents are a unification[1] of Emacs's overlays and text properties,
with a similar API. Most likely you want to use the text property API
rather than the overlay API.
Specifiers are a unification and generalization of buffer-local and
frame-local variables[2], but with a rather different API that has to
be invoked explicitly to reference and mutate them, rather than being
a special type of variable that is referenced and mutated in the usual
way. I suppose that you can probably ignore the specifier stuff,
however, and just use Customize to define the appropriate faces
(defface) which are selected for the x-symbol charset.
Another problem you'll run into in more recent GNU Emacs is that the
internal encoding (a UTF-8 extension) no longer has charsets in the
sense that Mule encoding did, as part of each character. So you will
need to define a charset to hold the x-symbol characters (a Unicode
block, possibly in Unicode private space but perhaps outside of the
official range of Unicode scalars) using an API that is not relevant
to XEmacs, I suspect.
Note that it's probably possible to achieve what x-symbol does in 1/5
the code and without defining a new charset or glyphs by simply taking
advantage of the fact that most (all?) of those symbols are already in
Unicode. I believe there are TeX add-ons that allow you to use them
instead of the traditional macros, as well, so you might not even need
to fiddle the display of the TeX file at all, and x-symbol would be
completely irrelevant.
Footnotes:
[1] IIRC, there's a corner case involving text properties that can't
be properly simulated using only extent properties, but it's otherwise
equivalent.
[2] ISTR frame-locals have been deprecated or removed in recent Emacs?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Uwe Brauer <oub(a)mat.ucm.es> writes:
> > What features are those you don't see elsewhere in Emacs? (I'm
> > specifically asking about GNU Emacs, not XEmacs.)
>
> I think a picture says more than 1000 words, here is a screenshot. (I
> hope it will not be blocked).
Actually, it doesn't. This screenshot is not dissimilar what you'll get
from using AUCTeX, preview-latex and TeX-fold-mode.
The main "not elsewhere" category I see are XEmacs' extensive input
modes (grid which is sort of a buffer-based menu, keyboard input methods
quite better sorted and convenient than what Quail offers and with
better feedback). Its buffer reencoding is a rather mixed blessing, but
it works with more than just TeX modes.
--
David Kastrup
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
>>>>> "Tassilo" == Tassilo Horn <tsdh(a)gnu.org> writes:
> Uwe Brauer <oub(a)mat.ucm.es> writes:
>> > What features are those you don't see elsewhere in Emacs? (I'm
>> > specifically asking about GNU Emacs, not XEmacs.)
>>
>> I think a picture says more than 1000 words, here is a screenshot. (I
>> hope it will not be blocked).
> Well, I guess you could use Emacs' built-in `prettify-symbols-mode' in
> order to display TeX macros using some unicode characters (or
> preview-latex of course).
I just switched `prettify-symbols-mode' on in a latex buffer but nothing
happens to \int or \alpha
>> > GNU Emacs doesn't have extents and specifiers.
>>
>> But what would provide a similar feature? I hoped somebody on the
>> list could tell me.
> Emacs' overlays serve the same purpose as XEmacs' extents, and I think
> there is or has been some 3rd-party package providing a unified API for
> overlays and extents.
> But I have no clue what specifiers are...
>> > My suggestion is to use the equivalent features provided by GNU
>> > Emacs. If you tell which features you miss, people here could
>> > advise you about the replacements, either in core or in add-on
>> > packages.
>>
>> Ok, so I have to dig more into the code or hope that somebody in
>> xemacs-beta could point me out what is the GNU emacs equivalent to
>> those functions. I still wonder how x-symbol could have worked under
>> GNU emacs 21, given that extents and specifiers did not exist neither
>> for emacs 21.
> I just downloaded x-symbol 4.5.1, and in its x-symbol-emacs.el there are
> several aliases defined for things that error for you. For example,
> `map-extents' is made an alias for `cl-map-overlays'. So you have to
> load that first.
I thought that as well, I had a (require 'x-symbol-emacs) in my init
file, but it seemed not to have worked. I will give it again a try.
> Well, eventually when loading x-symbol.el I also got an
> wrong-number-of-arguments error but that's probably an incompatibility
> which is easy to fix.
Do you mean the
- x-symbol-set-face-font: Wrong type argument: listp,
"-adobe-helvetica-medium-r-normal-*-14-*-*-*-*-*-iso8859-1"
error? I hoped this is a wrong-number-of-arguments error but I don't
know how to fix it.
I will try again to load x-symbol-emacs manually and then will see.
Thanks
Uwe
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
> What features are those you don't see elsewhere in Emacs? (I'm
> specifically asking about GNU Emacs, not XEmacs.)
I think a picture says more than 1000 words, here is a screenshot. (I
hope it will not be blocked).
> GNU Emacs doesn't have extents and specifiers.
But what would provide a similar feature? I hoped somebody on the list
could tell me.
> My suggestion is to use the equivalent features provided by GNU
> Emacs. If you tell which features you miss, people here could advise
> you about the replacements, either in core or in add-on packages.
Ok, so I have to dig more into the code or hope that somebody in
xemacs-beta could point me out what is the GNU emacs equivalent to those
functions. I still wonder how x-symbol could have worked under GNU
emacs 21, given that extents and specifiers did not exist neither for
emacs 21.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta