GPLv3|L8R -- Status report - ready for inspection?
7 years, 6 months
Mats Lidell
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
[Bug: 21.5-b34] smtpmail only works after eval'ing
9 years, 2 months
Marcus Harnisch
Marcus Harnisch
================================================================
Dear Bug Team!
During debugging the root cause of unexplicable SMTP authentication
failures it turned out that after eval'ing the buffer "smtpmail.el"
things suddenly started working :-/
This behavior is reproducible.
Some variables from smtpmail.el receive their settings via
customize. Anything else I can help with? I guess I could check which
parts of smtpmail.el really need to be eval'ed.
Cheers
Marcus
================================================================
System Info to help track down your bug:
---------------------------------------
uname -a: Linux dipsy 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
./configure '--with-pop' '--with-sound=alsa' '--enable-menubars=lucid' '--enable-scrollbars=athena' '--enable-dialogs=athena' '--enable-widgets=athena' '--with-athena=3d' '--without-gpm' '--without-ldap' '--without-postgresql' '--with-mule' '--without-xim' '--without-canna' '--with-xft=emacs,tabs,gauges,menubars' '--with-zlib' '--without-bignum' '--with-kkcc' '--with-newgc' '--without-error-checking' '--with-modules' '--with-database=berkdb' '--with-ncurses'
XEmacs 21.5-b34 "kale" configured for `x86_64-unknown-linux'.
Compilation Environment and Installation Defaults:
Source code location: /home/marcus/Downloads/xemacs-21.5.34
Installation prefix: /usr/local
Operating system description file: `s/linux.h'
Not using any machine description file
Compiler version: gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2
- GCC specs file: specs.
- Compiler command: gcc -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts -Wpacked -Wshadow -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wdeclaration-after-statement -Wunused-parameter -g
libc version: GNU libc 2.19-0ubuntu6.32.19-0ubuntu6.3 (Debian)
Relocating allocator for buffers: no
GNU version of malloc: yes
- Using Doug Lea's new malloc from the GNU C Library.
Package Search (a 'root' contains '{xemacs,mule,site}-packages'):
User package roots: ~/.xemacs
System package roots: /usr/local/share/xemacs
WARNING: /usr/local/share/xemacs was specified, but doesn't exist.
WARNING: XEmacs functionality will be noticably limited until
WARNING: some packages are installed.
Window System:
Compiling in support for the X window system:
- X Windows headers location:
- X Windows libraries location:
- Handling WM_COMMAND properly.
- Using fontconfig to manage fonts.
- Compiling in support for Xft antialiased fonts (EXPERIMENTAL).
Compiling in support for the Athena widget set:
- Athena headers location: X11/Xaw3d
- Athena library to link: Xaw3d
Using Lucid menubars.
- Using Xft to render antialiased fonts in menubars.
WARNING: This Xft feature will be replaced with a face.
Using Athena scrollbars.
Using Athena dialog boxes.
Using Athena native widgets.
- Using Xft to render antialiased fonts in tab controls.
WARNING: This Xft feature will be replaced with a face.
- Using Xft to render antialiased fonts in progress bars.
WARNING: This Xft feature will be replaced with a face.
WARNING: This Xft feature not yet implemented; setting ignored.
TTY:
Compiling in support for ncurses.
Images:
Compiling in support for XPM images.
Compiling in support for PNG images.
Compiling in support for JPEG images.
Compiling in support for X-Face message headers.
Sound:
Compiling in support for sound (native).
Compiling in support for ALSA (Advanced Linux Sound Architecture).
Databases:
Internationalization:
Compiling in support for Mule (multi-lingual Emacs).
Mail:
Compiling in support for POP mail retrieval.
Compiling in support for "file" mail spool file locking method.
Other Features:
Inhibiting IPv6 canonicalization at startup.
Compiling in support for dynamic shared object modules.
Using the new GC mark algorithms (KKCC).
WARNING: ---------------------------------------------------------
WARNING: The new algorithms are experimental. They are enabled by
WARNING: default for this release. Use `--disable-kkcc' to
WARNING: turn it off.
WARNING: ---------------------------------------------------------
Using the new incremental garbage collector and the new allocator.
Using POSIX sigaction() to install fault handler.
Using the new portable dumper.
Compiling in support for extra debugging code.
Load-Path Lisp Shadows:
----------------------
(/usr/local/share/xemacs/xemacs-packages/lisp/cedet-common/working
/usr/local/share/xemacs/xemacs-packages/lisp/semantic/working
/usr/local/share/xemacs/xemacs-packages/lisp/cedet-common/sformat
/usr/local/share/xemacs/xemacs-packages/lisp/semantic/sformat
/usr/local/share/xemacs/xemacs-packages/lisp/gnus/format-spec
/usr/local/share/xemacs/xemacs-packages/lisp/text-modes/format-spec
/usr/local/share/xemacs/xemacs-packages/lisp/mule-base/ethio-util
/usr/local/share/xemacs-21.5-b34/lisp/mule/ethio-util
/usr/local/share/xemacs/xemacs-packages/lisp/mule-base/japan-util
/usr/local/share/xemacs-21.5-b34/lisp/mule/japan-util
/usr/local/share/xemacs/xemacs-packages/lisp/mule-base/korea-util
/usr/local/share/xemacs-21.5-b34/lisp/mule/korea-util
/usr/local/share/xemacs/xemacs-packages/lisp/mule-base/china-util
/usr/local/share/xemacs-21.5-b34/lisp/mule/china-util
/usr/local/share/xemacs/xemacs-packages/lisp/leim/hebrew
/usr/local/share/xemacs-21.5-b34/lisp/mule/hebrew
/usr/local/share/xemacs/xemacs-packages/lisp/mule-base/viet-util
/usr/local/share/xemacs-21.5-b34/lisp/mule/viet-util
/usr/local/share/xemacs/xemacs-packages/lisp/mule-ucs/unicode
/usr/local/share/xemacs-21.5-b34/lisp/unicode
/usr/local/share/xemacs/xemacs-packages/lisp/build/build-report
/usr/local/share/xemacs-21.5-b34/lisp/build-report
/usr/local/share/xemacs/xemacs-packages/lisp/xemacs-base/easy-mmode
/usr/local/share/xemacs-21.5-b34/lisp/easy-mmode
/usr/local/share/xemacs/xemacs-packages/lisp/xemacs-base/regexp-opt
/usr/local/share/xemacs-21.5-b34/lisp/regexp-opt
/usr/local/share/xemacs/xemacs-packages/lisp/apel/alist
/usr/local/share/xemacs-21.5-b34/lisp/alist)
Internationalization Settings:
-------------------------
Environment:
Value of LC_ALL : nil
Value of LC_COLLATE : nil
Value of LC_CTYPE : nil
Value of LC_MESSAGES : nil
Value of LC_MONETARY : de_DE.UTF-8
Value of LC_NUMERIC : de_DE.UTF-8
Value of LC_TIME : de_DE.UTF-8
Value of LANG : en_US.UTF-8
Lisp locale settings:
current-language-environment => "English (UTF-8)"
default-buffer-file-coding-system => utf-8
default-process-coding-system => (undecided . utf-8)
(current-locale) => "en_US.UTF-8"
keyboard-coding-system => utf-8
terminal-coding-system => utf-8
(coding-priority-list) =>
(utf-8 iso-8-1 utf-16-little-endian-bom utf-16-bom utf-8-bom iso-7
no-conversion iso-8-2 iso-8-designate iso-lock-shift shift-jis
big5 utf-16-little-endian utf-16 ucs-4)
Coding system aliases:
'native is aliased to utf-8
'file-name is aliased to utf-8
'mswindows-multibyte-system-default is not a coding system alias
Installed XEmacs Packages:
-------------------------
(zenirc ver: 1.18 upstream: 2.112)
(xwem ver: 1.25 upstream: lg(a)xwem.org--2005/xwem--main--2.1--versionfix-1)
(xslt-process ver: 1.14 upstream: 1.2.1)
(xslide ver: 1.11 upstream: 0.2.2)
(xlib ver: 1.16 upstream: lg(a)xwem.org--2005/xlib--main--2.1--version-0)
(xetla ver: 1.04 upstream: steve(a)eicq.org--2005/xetla--main--1.1--version-0)
(xemacs-devel ver: 1.84 upstream: No-Upstream-Ver)
(xemacs-base ver: 2.43 upstream: No-Upstream-Ver)
(x-symbol ver: 1.16 upstream: 4.5.1)
(w3 ver: 1.41 upstream: 4.0pre47)
(vm ver: 8.109999999999999 upstream: 8.0.12-devo)
(viper ver: 1.69 upstream: 3.09)
(view-process ver: 1.15 upstream: 2.4)
(vhdl ver: 1.24 upstream: 3.33.12)
(vc-cc ver: 1.24 upstream: No-Upstream-Ver)
(vc ver: 1.5 upstream: No-Upstream-Ver)
(tramp ver: 1.53 upstream: 2.2.11)
(tpu ver: 1.16 upstream: 4.2X)
(tooltalk ver: 1.17 upstream: No-Upstream-Ver)
(tm ver: 1.42 upstream: No-Upstream-Ver)
(time ver: 1.16 upstream: 1.17)
(textools ver: 1.17 upstream: No-Upstream-Ver)
(text-modes ver: 2.05 upstream: No-Upstream-Ver)
(texinfo ver: 1.32 upstream: No-Upstream-Ver)
(supercite ver: 1.23 upstream: 3.55x3)
(strokes ver: 1.12 upstream: No-Upstream-Ver)
(speedbar ver: 1.32 upstream: 1.0pre4)
(sounds-wav ver: 1.14 upstream: No-Upstream-Ver)
(sounds-au ver: 1.14 upstream: No-Upstream-Ver)
(sml-mode ver: 0.14 upstream: 3.9.5)
(slider ver: 1.18 upstream: 0.3x1)
(skk ver: 1.27 upstream: 10.62a)
(sieve ver: 1.2 upstream: No-Upstream-Ver)
(sh-script ver: 1.26 upstream: 2.0f)
(sgml ver: 1.13 upstream: No-Upstream-Ver)
(semantic ver: 1.23 upstream: 2.0pre4)
(scheme ver: 1.22 upstream: No-Upstream-Ver)
(sasl ver: 1.18 upstream: 1.14.4)
(ruby-modes ver: 1.07 upstream: 1.8.7)
(rmail ver: 1.16 upstream: No-Upstream-Ver)
(riece ver: 1.26 upstream: 3.1.2)
(reftex ver: 1.36 upstream: 4.21)
(re-builder ver: 1.07 upstream: 1.20)
(python-modes ver: 1.16 upstream: 5.0.0)
(psgml-dtds ver: 1.05 upstream: No-Upstream-Ver)
(psgml ver: 1.49 upstream: 1.3.2)
(ps-print ver: 1.14 upstream: 6.5.6)
(prog-modes ver: 2.31 upstream: No-Upstream-Ver)
(pgg ver: 1.1 upstream: 0.1)
(perl-modes ver: 1.16 upstream: No-Upstream-Ver)
(pcomplete ver: 1.08 upstream: 1.1.6)
(pcl-cvs ver: 1.73 upstream: R-2_9_9)
(pc ver: 1.3 upstream: No-Upstream-Ver)
(os-utils ver: 1.44 upstream: No-Upstream-Ver)
(oo-browser ver: 1.07 upstream: 4.08)
(ocaml ver: 0.1 upstream: 3.06)
(net-utils ver: 1.61 upstream: N/A)
(mule-ucs ver: 1.21 upstream: 0.84)
(mule-base ver: 1.6 upstream: No-Upstream-Ver)
(mmm-mode ver: 1.08 upstream: 0.4.8)
(misc-games ver: 1.25 upstream: No-Upstream-Ver)
(mine ver: 1.18 upstream: 1.9)
(mh-e ver: 1.35 upstream: 7.4.2)
(mew ver: 1.22 upstream: 1.94.2)
(mailcrypt ver: 2.16 upstream: 3.5.8)
(mail-lib ver: 1.83 upstream: No-Upstream-Ver)
(lookup ver: 1.17 upstream: 1.0)
(locale ver: 1.3 upstream: No-Upstream-Ver)
(leim ver: 1.38 upstream: No-Upstream-Ver)
(latin-unity ver: 1.23 upstream: 1.23)
(latin-euro-standards ver: 1.11 upstream: 1.11)
(jde ver: 1.54 upstream: 2.3.5.1)
(ispell ver: 1.37 upstream: 3.6)
(ilisp ver: 1.38 upstream: 5.12.0)
(igrep ver: 1.18 upstream: 2.111)
(idlwave ver: 1.34 upstream: 5.1)
(ibuffer ver: 1.12 upstream: No-Upstream-Ver)
(hyperbole ver: 1.22 upstream: 5.0.5)
(hm--html-menus ver: 1.26 upstream: 5.9)
(haskell-mode ver: 1.14 upstream: 2.1)
(guided-tour ver: 0.54 upstream: No-Upstream-Ver)
(gnus ver: 2.0 upstream: 5.10.10)
(gnats ver: 1.19 upstream: 3.101)
(general-docs ver: 1.08 upstream: No-Upstream-Ver)
(games ver: 1.23 upstream: 2.00)
(fsf-compat ver: 1.24 upstream: No-Upstream-Ver)
(frame-icon ver: 1.13 upstream: No-Upstream-Ver)
(fortran-modes ver: 1.07 upstream: No-Upstream-Ver)
(forms ver: 1.17 upstream: 2.37)
(footnote ver: 1.18 upstream: 0.18x)
(eudc ver: 1.43 upstream: 1.32)
(eterm ver: 1.2 upstream: No-Upstream-Ver)
(eshell ver: 1.2 upstream: 0fc80a3f6bb3bb59f42e9ff83cc8b89bf90fe658)
(escreen ver: 1.03 upstream: 1.16)
(erc ver: 0.26 upstream: Version 5.1.2 Revision: 1.796.2.6)
(emerge ver: 1.13 upstream: No-Upstream-Ver)
(elib ver: 1.15 upstream: 1.0)
(eieio ver: 1.09 upstream: 1.0pre4)
(egg-its ver: 1.29 upstream: No-Upstream-Ver)
(efs ver: 1.37 upstream: 1.24)
(edt ver: 1.16 upstream: No-Upstream-Ver)
(edit-utils ver: 2.56 upstream: No-Upstream-Ver)
(ediff ver: 1.84 upstream: 2.75)
(edict ver: 1.19 upstream: 0.9.9)
(edebug ver: 1.24 upstream: No-Upstream-Ver)
(ede ver: 1.06 upstream: 1.0pre4)
(ecrypto ver: 0.23 upstream: 2.0)
(ecb ver: 1.25 upstream: 2.31)
(easypg ver: 1.05 upstream: 0.0.16)
(docbookide ver: 0.1 upstream: 0.1)
(dired ver: 1.22 upstream: 7.17)
(dictionary ver: 1.18 upstream: 1.8)
(debug ver: 1.2 upstream: No-Upstream-Ver)
(crisp ver: 1.17 upstream: 1.34)
(cookie ver: 1.17 upstream: No-Upstream-Ver)
(cogre ver: 1.04 upstream: 0.5)
(clearcase ver: 1.12 upstream: /main/laptop/165)
(cedet-common ver: 1.03 upstream: 1.0pre4)
(cc-mode ver: 1.84 upstream: 5.32.5)
(calendar ver: 1.41 upstream: No-Upstream-Ver)
(calc ver: 1.28 upstream: 2.02fX3)
(c-support ver: 1.24 upstream: No-Upstream-Ver)
(build ver: 1.17 upstream: 2.02)
(bbdb ver: 1.34 upstream: 2.35)
(auctex ver: 1.56 upstream: 11.88)
(apel ver: 1.36 upstream: 10.7)
(ada ver: 1.16 upstream: 2.27)
(Sun ver: 1.19 upstream: No-Upstream-Ver)
Installed Modules:
-----------------
Features:
--------
(field xemacsbug shadow annotations sort gnus-fun gnus-cite pp
gnus-async starttls latin-unity-tables latin-euro-standards
latin-euro-latin10 latin-euro-latin9 latin-euro-latin8
latin-euro-latin7 latin-unity-vars latin-unity gnus-bcklg gnus-draft
gnus-ml disp-table smtpmail gnus-topic nndoc byte-optimize bytecomp
byte-compile parse-time nnfolder utf7 tls nnimap imap nndraft nnmh
bbdb-gnus bbdb-snarf mail-extr bbdb-com encrypt gnus-agent gnus-srvr
gnus-score score-mode nnvirtual gnus-msg gnus-art mm-uu mml2015 pgg
password pgg-parse pgg-def mm-view gnus-sum gnus-group gnus-undo nntp
nnoo nnmail mail-source format-spec gnus-cache gnus-start gnus-spec
gnus-int gnus-range message mml mml-sec mml-smime smime dig mm-decode
mm-bodies mm-encode mailcap lpr mail-parse rfc2231 rfc2047 rfc2045 qp
ietf-drums mail-abbrevs sendmail gmm-utils mailheader canlock sha1
executable hex-util gnus-win gnus gnus-ems gnus-xmas messagexmas
nnheader nnheaderxm gnus-util netrc time-date mail-utils mm-util
mail-prsvr wid-edit guided-tour cal-china lunar solar cal-dst
cal-persia cal-islam cal-julian cal-hebrew holidays efs-cu diary-lib
button timer-funcs lazy-lock mmm-mode mmm-univ mmm-class mmm-region
mmm-utils font-lock pending-del appt calendar cal-xemacs cal-compat
paren mic-paren timer mmm-auto mmm-vars mmm-compat overlay align
mailcrypt rfc822 comint ring bbdb regexp-opt timezone strokes cus-face
atomic-extents advice advice-preload uniquify mwheel zenirc-autoloads
xwem-autoloads xslt-process-autoloads xslide-autoloads xlib-autoloads
xetla-autoloads xemacs-devel-autoloads xemacs-base-autoloads
x-symbol-autoloads w3-autoloads vm-autoloads viper-autoloads
view-process-autoloads vhdl-autoloads vc-cc-autoloads vc-autoloads
tramp-autoloads tpu-autoloads tooltalk-autoloads tm-autoloads
time-autoloads textools-autoloads text-modes-autoloads
texinfo-autoloads supercite-autoloads strokes-autoloads
speedbar-autoloads sounds-wav-autoloads sounds-au-autoloads
sml-mode-autoloads slider-autoloads skk-autoloads sieve-autoloads
sh-script-autoloads sgml-autoloads semantic-autoloads scheme-autoloads
sasl-autoloads ruby-modes-autoloads rmail-autoloads riece-autoloads
reftex-autoloads re-builder-autoloads python-modes-autoloads
psgml-dtds-autoloads psgml-autoloads ps-print-autoloads
prog-modes-autoloads pgg-autoloads perl-modes-autoloads
pcomplete-autoloads pcl-cvs-autoloads pc-autoloads os-utils-autoloads
oo-browser-autoloads ocaml-autoloads net-utils-autoloads
mule-ucs-autoloads mule-base-autoloads mmm-mode-autoloads
misc-games-autoloads mine-autoloads mh-e-autoloads mew-autoloads
mailcrypt-autoloads mail-lib-autoloads lookup-autoloads
locale-autoloads leim-autoloads latin-unity-autoloads
latin-euro-standards-autoloads jde-autoloads ispell-autoloads
ilisp-autoloads igrep-autoloads idlwave-autoloads ibuffer-autoloads
hyperbole-autoloads hm--html-menus-autoloads haskell-mode-autoloads
guided-tour-autoloads gnus-autoloads gnats-autoloads
general-docs-autoloads games-autoloads fsf-compat-autoloads
frame-icon-autoloads fortran-modes-autoloads forms-autoloads
footnote-autoloads eudc-autoloads eterm-autoloads eshell-autoloads
escreen-autoloads erc-autoloads emerge-autoloads elib-autoloads
eieio-autoloads egg-its-autoloads efs-autoloads edt-autoloads
edit-utils-autoloads ediff-autoloads edict-autoloads edebug-autoloads
ede-autoloads ecrypto-autoloads ecb-autoloads easypg-autoloads
docbookide-autoloads dired-autoloads dictionary-autoloads
debug-autoloads crisp-autoloads cookie-autoloads cogre-autoloads
clearcase-autoloads cedet-common-autoloads cc-mode-autoloads
calendar-autoloads calc-autoloads c-support-autoloads build-autoloads
bbdb-autoloads tex-site auctex-autoloads apel-autoloads ada-autoloads
Sun-autoloads modules-autoloads mule-autoloads auto-autoloads
auto-show fontl-hooks canna-leim tibetan thai slovenian czech romanian
lao devanagari indian cyrillic code-cmds gutter-items menubar-items
x-menubar mode-motion mouse behavior itimer auto-save lisp-mode
easymenu easy-mmode iso8859-1 page buff-menu lib-complete loadhist
cus-file derived newcomment rsz-minibuf env text-props fontconfig
frame obsolete packages cus-start widget custom cl-extra cl backquote
unicode font-mgr athena-scrollbars cut-buffer xft-fonts lucid-menubars
athena-dialogs x c-balloon-help tty-frames tty toolbar native-sound
alsa-sound scrollbar unix-processes multicast network-streams
subprocesses modules menu-accelerator-support menubar md5 xemacs mule
gutter png jpeg xface xpm xbm lisp-float-type file-coding linux dialog
devices debug-xemacs window-system base64)
Recent keystrokes:
-----------------
down down down down down down down down down down down
down down down down down down down down down down SPC
SPC C-x C-right down SPC down down down down down down
up up up up down down down down down SPC up up up up
down down down down down SPC down SPC down SPC up SPC
down SPC SPC down down down down down down down down
down down SPC down SPC up SPC SPC down SPC button1
button1up button1 button1up button1 button1up M-x r
e p o r e t BS BS TAB x TAB RET
Recent messages (most recent first):
-----------------------------------
Fontifying *mail to XEmacs Beta*... done.
Fontifying *mail to XEmacs Beta*...
Loading xemacsbug...done
Loading xemacsbug...
Loading annotations...done
Loading annotations...
C-x C-right not defined.
Notice: Unable to instantiate font for charset japanese-jisx0208, face gnus-summary-normal-read
Parsing BBDB... (frobnicating...done)
Parsing BBDB... (frobnicating...)
Parsing BBDB... (reading...)
Parsing BBDB...
Loading gnus-fun...done
Loading gnus-fun...
Loading gnus-cite...done
Loading gnus-cite...
nntp read: 12k
nntp read: 11k
Generating summary...done
Generating summary...
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 2 participants
- 5 comments
Re: Building an X86 binary with Visual Studio Community 2013
9 years, 6 months
Vin Shelton
Vin Shelton
Dear Biswajit,
On Sun, May 31, 2015 at 3:52 PM, Biswajit Khandai <b_khandai(a)yahoo.com> wrote:
>
> Vin,
> This is where my original comment of "the build will fail in a heartbeat" had come from.
>
> I thought this time around you or someone might work with me if I wanted to give it an initial spin. Is that (or not) the case ?
>
> I wonder : Is xemacs still a serious and live project ? If it is, is Window native binary considered a serious enough part of the project ?
(I've copied xemacs-beta as that is the medium for communication among
the XEmacs developers and maybe someone else will want to chime in.)
I don't really understand your points; I'll explain the situation as I see it:
1. I am currently making Windows installation kits. Those kits are
built with VS6. The Windows Installation kits, at least in part
thanks to your prodding/encouragement, are an ongoing activity. I
generally create a new installation kit with each update to the 21.5
development branch.
2. If someone else wants to build Windows Installation kits using a
different version of Visual Studio (or a different toolchain
altogether), he or she is welcome to work through the issues
necessary. I am happy to advise/help in that effort, but I do not
currently have a copy of VS2012 or VS2013, so my advise will be
somewhat theoretical in nature. You (or whoever else wants to take
this on) will have to roll up your sleeves and struggle with various
issues (manifest files among them).
Whether or not XEmacs is serious and alive, is, IMO, in the eye of the beholder.
Thanks for the bug report on paren highlighting. Since you narrowed
the failure down to the menu, I will take a look at that.
- Vin
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 2 participants
- 1 comments
Re: Building an X86 binary with Visual Studio Community 2013
9 years, 6 months
Vin Shelton
Vin Shelton
Dear Biswajit,
Thanks for your efforts. Manifest files are one of the annoyance of
updating to a newer version of VS.
Good luck, and please keep xemacs-beta informed of your progress.
- Vin
On Sat, May 30, 2015 at 1:29 AM, Biswajit Khandai <b_khandai(a)yahoo.com> wrote:
> Vin,
> I tried to build a native binary using VS Community 2013. The
> underlying VS is the 2012 version.
>
> First I ran into the problem of mismatching versions of optional libs. The
> config.inc was expecting different versions from the versions installed by
> optional_libs.exe . I changed the versions in config.inc ,. That was easy.
>
> Next I started running into real problems.
>
> I see two kinds of errors. One kind is to do with missing manifest files.
> Another kind has to do with keywords being used in macros (or something like
> that).
>
> Doing some Googling, I saw that adding a pragma (as follows) may help with
> the second kind of error, I added the following pragma to config.h.in
> (around line # 899) but it didn't seem to help really.
>
> #pragma warning (1 : 4005)
>
> Anyways, here is the log file from the build attempt.
>
> -Biswajit
>
>
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
make-overlay and endpoints
9 years, 6 months
Marcus Harnisch
Marcus Harnisch
Hi all
I have encountered an issue with respect to compatibility between
Emacs overlays and our extents. Here's what the GNU Emacs List
Reference Manual says:
“The arguments front-advance and rear-advance specify the marker
insertion type for the start of the overlay and for the end of the
overlay, respectively. See Marker Insertion Types. If they are both
nil, the default, then the overlay extends to include any text
inserted at the beginning, but not text inserted at the end.”
This appears to be the same as with extents.
However, when creating an overlay in Emacs that has identical start
and end positions and the default endpoint properties, then deleting
characters at that position does not delete the overlay.
In XEmacs 21.5.34 doing the same with an extent
(start-closed/end-open) removes the extent from the buffer.
“Deletion of a character on a side of a zero-length extent whose
corresponding endpoint is closed causes the extent to be detached if
its `detachable' property is set; if the corresponding endpoint is
open, the extent remains in the buffer, moving as necessary.”
What exactly does “a character on a side” mean. I can only delete a
character “at” the extent. In which case the start-closed seems to
have a higher priority.
In the case at hand this is easy enough to work around, but I am
wondering if that difference is deliberate, whether it may make sense
to change the behavior or whether to tell authors to not rely on
either behavior since it is a nasty corner case scenario anyway.
Thanks
Marcus
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 2 participants
- 3 comments
Re: Innosetup binaries for 21.5.32 and later
9 years, 6 months
Vin Shelton
Vin Shelton
Biswajit -
Not to be too thick, but what is paren-highlighting supposed to do? I
haven't used it for a long time. How did you turn it on?
The standard approach for reporting bugs is:
1. This is what I did. It's always best to start from some known
minimal place, like "xemacs -vanilla".
2. This is what I expected. E.g. When I opened this file and moved my
cursor to the first curly brace, I expected the curly brace to change
into a dancing hippo.
3. This is what I got. E.g. The curly brace didn't change
When you wrote: "the build fail very quickly" what does that mean?
Did you try to use VS6? See the 3 simple steps above.
- Vin
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 2 participants
- 1 comments
Re: Innosetup binaries for 21.5.32 and later
9 years, 7 months
Vin Shelton
Vin Shelton
Dear Biswajit,
On Thu, May 28, 2015 at 5:09 PM, Biswajit Khandai <b_khandai(a)yahoo.com> wrote:
> Thanks, Vin. Here is what I find.
>
> 1. Paren-highlighting does not work in the various flavors of
> 21.5.34 .
OK, so please start "xemacs -vanilla" and tell xemacs-beta(a)xemacs.org
what steps are necessary to reproduce the problem. Please be sure to
describe a simple test case, including a simple file that exhibits the
problem. Often by stripping the problem down to a basic test case,
the problem will become obvious to you and/or others.
> Exactly where should I get the build instructions for native X86
> binary ? Can these build instructions be ported to a more recent VS
> version ?
the file nt/README in the source has some (slightly bit-rotted)
instructions.
> BTW, I just learned that "Visual Studio Community 2013" is a
> full-featured visual studio that is made available FREE by Microsoft
> starting Nov 2014.
That's terrific. If you can build against Visual Studio Community
2013, and document the steps you take, that would be great.
I will review the information and get the necessary changes
checked in.
Regards,
Vin
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 2 participants
- 1 comments
Re: Innosetup binaries for 21.5.32 and later
9 years, 7 months
Vin Shelton
Vin Shelton
Biswajit -
Does http://ftp.xemacs.org/pub/windows/testing/XEmacs_Setup_21.5.34.exe
(or http://ftp.xemacs.org/pub/windows/testing/XEmacs_Setup_21.5-2015-05-18.exe)
work for you?
The instructions (based on the non-free Visual Studio 6 - what're you
staring at? It was released in 1998!) work for me. If someone wants
to update the instructions, patches will be reviewed and approved. :-)
Regards,
Vin
On Wed, May 27, 2015 at 12:55 PM, Biswajit Khandai <b_khandai(a)yahoo.com> wrote:
> Vin had made an experimental 21.5.34 innosetup build for me, back in 2014.
>
> I have been using it since. I have not seen any issues yet, other than that
> paren-highlighting does not seem to work.
>
> Would it be possible to fix this, and release an official 21.5.34 beta
> innosetup build ?
>
> There was one more request from me at the time - to dust off the build
> instructions for a native X86 build using free tools (including free
> versions of Microsoft tools), so that people can download and build binaries
> easily. May I raise the same request again ?
>
> Thanks a lot.
>
> -Biswajit
>
> ________________________________
> From: Vin Shelton <acs(a)xemacs.org>
> To: Biswajit Khandai <b_khandai(a)yahoo.com>
> Cc: XEmacs developers <xemacs-beta(a)xemacs.org>
> Sent: Thursday, November 6, 2014 11:44 AM
> Subject: Re: Innosetup binaries for 21.5.32 and later
>
> Dear XEmacs Developers,
>
> I recently got a large roundtuit dropped in my lap (my startup company
> imploded), so I've spent a few days working on XEmacs native Windows
> setup kits.
>
> On Fri, Oct 31, 2014 at 8:45 PM, Biswajit Khandai <b_khandai(a)yahoo.com>
> wrote:
>> I was assuming that the stable channel native windows binary will be built
>> by "someone".... If that assumption is right, then the same "someone"
>> could
>> build the beta channel native windows binary. It may not be you,
>> necessarily.
>
> Your assumption is correct, but I am the only someone who builds these
> kits. I will try to make a setup kit for every release, but it is
> difficult for me to know how much time I will have for making setup
> kits in between releases.
>
>> However, if that assumption is wrong, I would like you to know that a heck
>> of a lot of people use xemacs on Windows - maybe you underestimate the
>> number of such people.
>
> Dear Biswajit - thank you for your kind words. They certainly made me
> feel like my efforts in this area have been well worthwhile.
>
> I have re-made setup kits for 21.4.22, 21.5.34 and 21.4 latest and
> 21.5 latest. I will upload them this afternoon to ftp.xemacs.org.
>
> I will be sending a small patch to XEmacs-patches to work around a
> couple of difficulties building without TLS on native Windows. I have
> not attempted to build with TLS as of yet.
>
>
>
>
> - Vin
>
>
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 2 participants
- 1 comments
Re: Innosetup binaries for 21.5.32 and later
9 years, 7 months
Vin Shelton
Vin Shelton
Dear XEmacs Developers,
I recently got a large roundtuit dropped in my lap (my startup company
imploded), so I've spent a few days working on XEmacs native Windows
setup kits.
On Fri, Oct 31, 2014 at 8:45 PM, Biswajit Khandai <b_khandai(a)yahoo.com> wrote:
> I was assuming that the stable channel native windows binary will be built
> by "someone".... If that assumption is right, then the same "someone" could
> build the beta channel native windows binary. It may not be you,
> necessarily.
Your assumption is correct, but I am the only someone who builds these
kits. I will try to make a setup kit for every release, but it is
difficult for me to know how much time I will have for making setup
kits in between releases.
> However, if that assumption is wrong, I would like you to know that a heck
> of a lot of people use xemacs on Windows - maybe you underestimate the
> number of such people.
Dear Biswajit - thank you for your kind words. They certainly made me
feel like my efforts in this area have been well worthwhile.
I have re-made setup kits for 21.4.22, 21.5.34 and 21.4 latest and
21.5 latest. I will upload them this afternoon to ftp.xemacs.org.
I will be sending a small patch to XEmacs-patches to work around a
couple of difficulties building without TLS on native Windows. I have
not attempted to build with TLS as of yet.
- Vin
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 2 participants
- 1 comments
Xemacs (Mule) and GNU Emacs, problem with drafts and encoding.
9 years, 7 months
Uwe Brauer
Uwe Brauer
The following message is a courtesy copy of an article
that has been posted to gmane.emacs.gnus.general as well.
Hello
I use gnus with both Emacsen. However the drafts which are saved are not
compatible with each other.
According to the documentation"
,----
|
| `message-draft-coding-system' is a variable declared in Lisp.
| -- loaded from "message"
|
| Value: escape-quoted
|
| Documentation:
| *Coding system to compose mail.
| If you'd like to make it possible to share draft files between XEmacs
| and Emacs, you may use `iso-2022-7bit' for this value at your own risk.
| Note that the coding-system `iso-2022-7bit' isn't suitable to all data.
`----
I tried that but this coding setting but alas it does not make the
drafts compatible.
Why does Xemacs not support the utf-8 coding for drafts, although in
general it does support this format?
regards
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments