July 2014 - 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

TLS implementation 9 years, 10 months

Jerry James

I've been working on TLS support for a little while, and now have what seems to be working nss, openssl, and gnutls lstream implementations. The next challenge is making those available via the Emacs interface, since that is what consuming packages expect. I thought I'd give you a snapshot of what I've done so far (attached), just in case I get abducted by aliens who need some operating system work done. If you see anything that seems wrong or wrong-headed, let me know. It's still early enough to change direction if I'm doing something gratuitously stupid. -- Jerry James http://www.jamezone.org/ _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

4 participants
12 comments

Cygwin 64-bit compilation experience? 9 years, 10 months

Henry S. Thompson

New machine, trying 64-bit cygwin, but no joy so far in compiling from latest sources. Too soon to say if I've just not got my environment right yet - so at this point just checking -- has anyone made this work yet? 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

7 participants
35 comments

Redisplay issues 10 years, 2 months

Raymond Toy

I've had minor redisplay issues for a very long time where sometimes when I C-v parts of the old line are displayed instead of the new. This was fairly rare. However, in the last couple of months, this has become much worse. C-v around a large file ends up with incorrect lines being displayed. I haven't really changed anything on my end, but I have updated xemacs to the most recent code along with various updates to the packages. Haven't come up with a repeatable test case and perhaps it's related to my fonts[1] or syntax highlighting[2]. But whatever, it's much worse than before and is now causing me to mis-edit somethings because what I see isn't what is actually there. Pressing C-l usually fixes this, fortunately. -- Ray Footnotes: [1] I reported this before, but on startup the window is big and I change my font in my xemacs to BitStream Vera Sans. The window shrinks in size. I click on the window and it suddenly gets wider but not everything is wider. XEmacs still thinks the window is not that wide. When I manually drag the right window edge, everything is resized correctly and things are working with the correct window size now. [2] Sometimes if I wait a bit, xemacs will redraw parts of the screen with the correct lines. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

2 participants
2 comments

Re: [AUCTeX-devel] [define-minor-mode] 10 years, 3 months

Uwe Brauer

> Hi Uwe, > 2014-07-27 18:49 GMT+02:00 Uwe Brauer <oub(a)mat.ucm.es>: > I confirm > (add-hook 'LaTeX-mode-hook 'TeX-source-correlate-mode) > doesn't work on XEmacs 21.4.22, but > (add-hook 'LaTeX-mode-hook (lambda () (TeX-source-correlate-mode 1))) Thanks, however I will not use a anonymous function (since it is difficult to remove it from the hook) but instead write a trivial function for turning the mode on. If somebody on Xemacs beta reads this, maybe there is an explanation for this behavior? Uwe _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

[define-minor-mode] (was: [hook does not work]) 10 years, 4 months

Uwe Brauer

>> "Tassilo" == Tassilo Horn <tsdh(a)gnu.org> writes: > Uwe Brauer <oub(a)mat.ucm.es> writes: > Hi Uwe, >> Well well >> >> (add-hook 'LaTeX-mode-hook 'TeX-source-correlate-mode) >> >> This does not work >> ,---- >> | >> | `LaTeX-mode-hook' is a variable declared in Lisp. >> | -- loaded from "latex" >> | >> | Value: (preview-mode-setup turn-on-auto-revert-mode >> | turn-on-my-footnote-mode turn-on-flyspell my-install-latex-toolbar >> | my-set-auto-capitalize turn-on-auto-capitalize-mode turn-on-cdlatex >> | my-latex-xsymbol-8bit turn-on-reftex my-LaTeX-TeX-add-symbols >> | TeX-source-correlate-mode my-latex-mode-key) >> | >> | Documentation: >> | A hook run in LaTeX mode buffers. >> `---- >> >> But in a Latex buffer I obtain >> >> ,---- >> | >> | `TeX-source-correlate-mode' is a variable declared in Lisp. >> | -- loaded from "tex" >> | >> | Value: nil >> | >> | Documentation: >> | Non-nil if Tex-Source-Correlate mode is enabled. >> | See the command `TeX-source-correlate-mode' for a description of this minor-mode. >> | Setting this variable directly does not take effect; >> | use either M-? C or the function `TeX-source-correlate-mode'. >> `---- >> >> Is this a bug? > I can't reproduce that. With a fresh emacs on a test account with > auctex from ELPA, with no settings in ~/.emacs except for > (add-hook 'LaTeX-mode-hook 'TeX-source-correlate-mode) > emacs foo.tex will activate `TeX-source-correlate-mode', i.e., its value > is t. > Could be a specific of XEmacs maybe? I did the same as you did for emacs, and indeed it is different TeX-source-correlate-mode is nil! I now that `define-minor-mode' always was sort of problematic in Xemacs, for example I almost never got an entry in the modline, although the mode was on. That is why I CC to Xemcas-beta. > For (at least recent) Emacs versions, all minor mode obey this calling > convention: > ,---- > | When called from Lisp, the mode command toggles the mode if the > | argument is `toggle', disables the mode if the argument is a > | non-positive integer, and enables the mode otherwise (including > | if the argument is omitted or nil or a positive integer). > `---- > I think with older emacs versions and XEmacs, calling a minor mode > function without argument toggles it. So maybe you have > `TeX-source-correlate-mode' in two hooks that are run for tex files, > e.g., in both `TeX-mode-hook' and `LaTeX-mode-hook', so that the first > toggles it on and the second off again? No, this is not the case and as I said I did what you to, xemacs -q evaluate the line with the hook and the mode is *not* turned on. Uwe _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

2 participants
1 comments

Re: Crash in bytecode.c:1823 unknown opcode: 0 10 years, 4 months

Aidan Kehoe

Ar an t-ochtú lá déag de mí Iúil, scríobh Stephen J. Turnbull: > Thanks for the follow-up! > > Aidan Kehoe writes: > > > I’ve seen similar crashes on 64-bit FreeBSD, but not on 32-bit OS X > > (yes, I’m still using my 2006 32-bit Mac Mini and am happy with > > it); some of your snipped boilerplate would have been handy! > > Well, it's 64-bit Gentoo Linux, 4-core AMD Opteron system, starting to > age (4-5 years?) now. > > > What XEmacs was your w3-display.el compiled under? It should say in > > the .elc file. > > No, it doesn't: > > ;ELC > ;;;###coding system: raw-text-unix > > (or (and (featurep 'xemacs) (null (function-max-args 'throw))) > (error "Loading this file requires xemacs, (null (function-max-args 'throw))")) > > I think this is likely from the last SUMO, so presumably it was > compiled by Norbert using 21.4. I guess this doesn't have anything to > do with (recent) changes to the byte-compiler after all (but I'd like > it to go away!! :-) Whoops, no, that is 21.5 bytecode. I am working on syncing GNU’s bytecomp.el and will include a version string in the output there; I should have done it earlier, I was trying to maximise the space in the prologue available for the version checks, and my first drafts didn’t adjust the amount of metadata output accordingly. It may be possible to find the exact issue with some C code based on the bytecode interpreter that sanity checks all the compiled function objects in memory. Lot of work, though, and might involve the halting problem. -- ‘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

1 participants
0 comments

Crash in bytecode.c:1823 unknown opcode: 0 10 years, 4 months

Stephen J. Turnbull

Aidan, you wouldn't happen to know anything about this? You're main person working on the bytecompiler recently. I *think* the abort fingered the line and file given above, but since I was -nw, I lost the stdout when XEmacs crashed. Lisp trace follows. steve＠uwakimon 07:33 ~ $ /playpen/src/XEmacs/xemacs/+clang/src/xemacs -nw -f vm Fatal error (6). [Boilerplate delete.] Lisp backtrace follows: # (unwind-protect ...) # bind (buff) w3-parse-buffer(#<buffer " *w3-region*">) # (unwind-protect ...) # (unwind-protect ...) # bind (#:G10252 parse w3-display-same-buffer source nd st) w3-region(3118 35151) # bind (layout end start) vm-mime-display-internal-emacs-w3-text/html(3118 #<marker at 35152 in INBOX Presentation 0x5fa12> [("text/html" "charset=utf-8") ("text/html" "charset=utf-8") "base64" nil nil nil nil #<marker at 206412511 in INBOX 0x5f614> #<marker at 206415736 in INBOX 0x5f615> #<marker at 206415737 in INBOX 0x5f616> #<marker at 206459429 in #INBOX 0x5f617> nil #:<<c>> #:<<m>> nil nil nil]) # (unwind-protect ...) # bind (#:G44433) # (unwind-protect ...) # bind (start charset buffer-read-only end buffer-size) byte-code("..." [buffer-size charset vm-mime-text/html-handler layout start end vm-mime-get-parameter "charset" "us-ascii" nil vm-emit-mime-decoding-message "Inlining text/html by %s..." vm-mime-insert-mime-body "\n" point-marker vm-mime-transfer-decode-region vm-mime-charset-decode-region t re-search-forward 0 insert-before-markers "z" ((byte-code b??????!??" [end delete-char -1] 2)) current-window-configuration ((set-window-configuration #1=#:G44433)) intern format "vm-mime-display-internal-%s-text/html" "Inlining text/html by %s... done." buffer-read-only case-fold-search %vm-mime-text/html-blocker #1#] 5) # (condition-case ... . ((error (byte-code "?? ?ŀ?\n?? !#\"???Ȁɀʀˀ!?? !%???Ώ?" [vm-mail-buffer error-data vm-mime-text/html-handler layout vm-set-mm-layout-display-error format "Inline text/html by %s display failed: %s" error-message-string vm-warn 0 2 "%s: %s" buffer-name vm-mm-layout-display-error nil] 7)))) # bind (layout) vm-mime-display-internal-text/html([("text/html" "charset=utf-8") ("text/html" "charset=utf-8") "base64" nil nil nil nil #<marker at 206412511 in INBOX 0x5f614> #<marker at 206415736 in INBOX 0x5f615> #<marker at 206415737 in INBOX 0x5f616> #<marker at 206459429 in #INBOX 0x5f617> nil #:<<c>> #:<<m>> nil nil nil]) # bind (handler primary-type type layout) vm-mime-display-internal([("text/html" "charset=utf-8") ("text/html" "charset=utf-8") "base64" nil nil nil nil #<marker at 206412511 in INBOX 0x5f614> #<marker at 206415736 in INBOX 0x5f615> #<marker at 206415737 in INBOX 0x5f616> #<marker at 206459429 in INBOX 0x5f617> nil #:<<c>> #:<<m>> nil nil nil] "text/html" "text") # (unwind-protect ...) # bind (modified handler new-layout file type primary-type # infered-type infered-primary-type extent dont-honor-c-d layout) vm-decode-mime-layout(#<extent (35153, 35225) HD vm-mime-function vm-mime-layout vm-mime-disposable vm-button balloon-help keymap in buffer INBOX Presentation 0x90f6d> t) # bind (vm-mime-auto-displayed-content-types # vm-mime-auto-displayed-content-type-exceptions) # (unwind-protect ...) # bind (layout) vm-mime-display-generic(#<extent (35153, 35225) HD vm-mime-function vm-mime-layout vm-mime-disposable vm-button balloon-help keymap in buffer INBOX Presentation 0x90f6d>) # bind (extent retval) # (unwind-protect ...) # bind (function) #<compiled-function (from vm-mime-run-display-function-at-point) #(&optional function) "...(40)" [function retval message #vm-message-pointer major-mode extent (vm-mode vm-virtual-mode) 3 22 #error "Message must be loaded to view attachments" #vm-find-layout-extent-at-point nil vm-extent-property #vm-mime-function] 4 #("/usr/local/lib/xemacs/xemacs-packages/lisp/vm/vm-mime.elc" #. 95791) nil 0x202a>() call-interactively(vm-mime-run-display-function-at-point) # (condition-case ... . error) # (catch top-level ...) Aborted _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

2 participants
1 comments

org-8.X and org-link-minor-mode 10 years, 4 months

Uwe Brauer

Hello There are two issues I would like to discuss. - I am using so far successfully org 7.8 under Xemacs 21.5.33 Mule, but could not get org 8.X to work, xemacs complains about a function called declare-function which GNU emacs posses and we don't. I have attached the error trace. - The other issue concerns an add-on to the org pkg called org-link-minor-mode, which allows to display org-links in a convenient way. It works nicely in GNU emacs 24 (with org-8), that is: it works say in fundamental and in LaTeX mode, but it does not work smoothly in xemacs 21.5.33 with org-7. It works sort of in fundamental mode but not in LaTeX mode at all. So I don't know who is here the culprit: missing functionality of org 8 or something deeper, that is some features org-link-minor requires but Xemacs does not posses? If somebody has any idea I would appreciate this very much. regards Uwe Brauer _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

3 participants
4 comments

Summary of XEmacs Issue Tracking System Issues 10 years, 4 months

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2014-07-08 - 2014-07-15) 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) / 311 closed ( +0) / 869 total ( +0) Open issues with patches: 13 Average duration of open issues: 1821 days. Median duration of open issues: 1957 days. Open Issues Breakdown new 247 ( +0) deferred 6 ( +0) napping 3 ( +0) verified 58 ( +0) assigned 147 ( +0) committed 19 ( +0) documented 3 ( +0) done/needs work 16 ( +0) _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 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 July 2014