XEmacs-Beta August 2017

xemacs-beta@xemacs.org

5 participants
18 discussions

Summary of XEmacs Issue Tracking System Issues 6 years, 8 months

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2017-08-22 - 2017-08-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. 572 open ( +0) / 323 closed ( +0) / 895 total ( +0) Open issues with patches: 13 Average duration of open issues: 2890 days. Median duration of open issues: 3093 days. Open Issues Breakdown new 264 ( +0) deferred 6 ( +0) napping 3 ( +0) verified 57 ( +0) assigned 145 ( +0) committed 19 ( +0) documented 3 ( +0) done/needs work 15 ( +0)

1 participants
0 comments

Re: nil has a plist, of course. 6 years, 8 months

Sebastian Freundt

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 "Stephen J. Turnbull" <stephen(a)xemacs.org> writes: > Aidan Kehoe writes: > > > And on two non-vanilla invocations of mine it’s non-nil. These seem like > > bugs: > > Easy to reproduce: > > (with-temp-buffer ;; let's not be visting a file > (defcustom junk nil "junk custom") > (assq 'junk (cadr (object-plist nil)))) > => (junk custom-variable) > > Easy to prevent: > > (with-temp-buffer > (defgroup trash-group nil "just for laughs") > (defcustom trash nil "trash custom") > (cons (assq 'trash (cadr (object-plist nil))) > (assq 'trash (cadr (object-plist 'trash-group))))) > => (nil trash custom-variable) > > Question: Should we *require* that customizations be in a group (ie, > defcustom barfs if there's no :group argument and (custom-current-group) > is nil)? Or should we force `custom-current-group' to return something > global like 'xemacs rather than nil? Or should we allow anti-social > customizations, that avoid all groups? > > I think option 2 is probably safest and least invasive, although the > pedant in me hankers after option 1. Option 3 strikes me as rather > risky given the general fragility of customize. How about a mild mixture between 2 and 1? Instead of barfing I think about a warning or something. Sebastian -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.0 (GNU/Linux) iD8DBQFFeF57lMmhrILJOQ4RAuFbAJ9emMRwm/EPB7VOnSmCv9gE3nlTSQCgiPFM sNJGPvRa2FaTiNpc9tYXqZw= =5fx/ -----END PGP SIGNATURE----- _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

2 participants
2 comments

Summary of XEmacs Issue Tracking System Issues 6 years, 8 months

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2017-08-15 - 2017-08-22) 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. 572 open ( +0) / 323 closed ( +0) / 895 total ( +0) Open issues with patches: 13 Average duration of open issues: 2883 days. Median duration of open issues: 3086 days. Open Issues Breakdown new 264 ( +0) deferred 6 ( +0) napping 3 ( +0) verified 57 ( +0) assigned 145 ( +0) committed 19 ( +0) documented 3 ( +0) done/needs work 15 ( +0)

1 participants
0 comments

Patch problem: xemacs-21.5.11-21.5.12-patch.gz 6 years, 8 months

Solignac

Hello everybody, I tried to update my xemacs-21.5.11 tree to 21.5.12 with the diff file found in ftp mirrors, but all attempts failed (patch said "patch: **** malformed patch at line 315"). I tried to skip several parts of the diff file without success (the main problem ends in the part of "configure", which could not be skipped). Did anyone encoutered the same problem? Could it be possible to re-generate the patch file? \bye S. -- MAKING MILHOUSE CRY IS NOT A SCIENCE PROJECT. MAKING MILHOUSE CRY IS NOT A SCIENCE PROJECT. MAKING MILHOUSE CRY IS NOT A SCIENCE PROJECT. -+- Bart Simpson on chalkboard, episode #213

4 participants
4 comments

Summary of XEmacs Issue Tracking System Issues 6 years, 8 months

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2017-08-08 - 2017-08-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. 572 open ( +0) / 323 closed ( +0) / 895 total ( +0) Open issues with patches: 13 Average duration of open issues: 2876 days. Median duration of open issues: 3079 days. Open Issues Breakdown new 264 ( +0) deferred 6 ( +0) napping 3 ( +0) verified 57 ( +0) assigned 145 ( +0) committed 19 ( +0) documented 3 ( +0) done/needs work 15 ( +0)

1 participants
0 comments

[21.4] Build problem 6 years, 8 months

Hauke Fath

Hi, an interesting problem has been plaguing the pkgsrc editors/xemacs build for a while. Some time ago, I updated editors/xemacs-packages to deploy the pre-release packages from beta/experimental/packages. Since that update, rebuilding xemacs with editors/xemacs{,-packages} installed will fail with [...] Loading loadhist.el... Loading loaddefs.el... Loading site-load.el... Bootstrapping from temacs... Compiling /usr/pkg/lib/xemacs/xemacs-packages/lisp/leim/hebrew.el... >>Error occurred processing /usr/pkg/lib/xemacs/xemacs-packages/lisp/leim/hebrew.el: Opening output file: directory not writable or nonexistent, /usr/pkg/lib/xemacs/xemacs-packages/lisp/leim/hebrew.elc Done + exit 1 *** [update-elc.stamp] Error code 1 make[1]: stopped in /var/obj/pkgsrc/editors/xemacs/work/xemacs-21.4.24/src 1 error [...] That is, there is no compiled equivalent for hebrew.el % > ls -l /usr/pkg/lib/xemacs/xemacs-packages/lisp/leim/hebrew.* -rw-r--r-- 1 root wheel 24602 Dec 14 2015 /usr/pkg/lib/xemacs/xemacs-packages/lisp/leim/hebrew.el % and the xemacs build feels called to compile the installed el file, which as an unprivileged build it cannot. Now, is it a problem when packages ship some of their source files uncompiled? And if it isn't, why should the xemacs build system attempt to recompile arbitrary installed el files? And where exactly in the build does that happen? Would the strategy be to make sure that all packages install compiled sources, or to slap the wrist of xemacsens build system when it tries to reach out beyond the build directory? Cheerio, hauke -- The ASCII Ribbon Campaign Hauke Fath () No HTML/RTF in email Institut für Nachrichtentechnik /\ No Word docs in email TU Darmstadt Respect for open standards Ruf +49-6151-16-21344

3 participants
3 comments

Summary of XEmacs Issue Tracking System Issues 6 years, 8 months

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2017-08-01 - 2017-08-08) 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. 572 open ( +0) / 323 closed ( +0) / 895 total ( +0) Open issues with patches: 13 Average duration of open issues: 2869 days. Median duration of open issues: 3072 days. Open Issues Breakdown new 264 ( +0) deferred 6 ( +0) napping 3 ( +0) verified 57 ( +0) assigned 145 ( +0) committed 19 ( +0) documented 3 ( +0) done/needs work 15 ( +0)

1 participants
0 comments

Summary of XEmacs Issue Tracking System Issues 6 years, 8 months

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2017-07-25 - 2017-08-01) 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. 572 open ( +0) / 323 closed ( +0) / 895 total ( +0) Open issues with patches: 13 Average duration of open issues: 2862 days. Median duration of open issues: 3065 days. Open Issues Breakdown new 264 ( +0) deferred 6 ( +0) napping 3 ( +0) verified 57 ( +0) assigned 145 ( +0) committed 19 ( +0) documented 3 ( +0) done/needs work 15 ( +0)

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 August 2017