Raymond Toy writes:
> I have not changed anything X-related, but there is some kind of
> managed updating system that could have. I'm running on Ubuntu
> 10.04 using whatever the stock window manager is for Gnome.
If that is still Metacity, I'm not surprised you had problems.
Metacity assumes that applications will follow a very narrow
interpretation of the ICCCM, and gets quite confused if they don't. I
suppose I can't entirely blame them since these conventions are
embedded in either the GNOME libraries or perhaps even lower-level in
GTK+ itself, but they're undocumented.
Maybe if I get some time I'll set up Xen or KVM somewhere so I can
easily install other OSes.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
On Wed, Aug 17, 2011 at 12:26 AM, Stephen J. Turnbull <stephen(a)xemacs.org>wrote:
>
> Do you have a plan that this question blocks you from following up?
>
Some additional information. This is easily reproduced using M-x
customize-variable user-mail-address (for want of a better variable). There
is a problem when customize is creating the push-button. It's crashing in
(widget-apply widget :create) when the widget is a push-button. There's no
problem creating the info-link widget.
Ray
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Also, with the latest build, I'm now getting this message whenever I exit:
Warning: XtRemoveGrab asked to remove a widget not on the list
Just run xemacs -vanilla and press C-x C-c to exit. XEmacs exits and prints
out the warning.
Ray
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
After updating to the latest code (3bc58dc9d688+), I notice that now I'm
getting lots of X Errors like so:
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 18 (X_ChangeProperty)
Resource id in failed request: 0x2a0015e
Serial number of failed request: 7637
Current serial number in output stream: 7638
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 25 (X_SendEvent)
Resource id in failed request: 0x2a0015e
Serial number of failed request: 7638
Current serial number in output stream: 7638
These are 100% repeatable, and here's the recipe.
Run xemacs -vanilla. In the *scratch* buffer, type in a few characters.
Then press M-BS (backward-kill-word). This will generate the two X error
messages above. You don't have to do M-BS. You can do M-x
backward-kill-word too. forward-kill-word also causes an X error. So does
kill-ring-save (M-w) and kill-line (C-k). But BS and C-d do not cause an
error.
Ray
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
ACTIVITY SUMMARY (2011-09-06 - 2011-09-13)
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.
527 open ( +1) / 272 closed ( +0) / 799 total ( +1)
Open issues with patches: 12
Average duration of open issues: 915 days.
Median duration of open issues: 960 days.
Open Issues Breakdown
new 206 ( +0)
deferred 6 ( +0)
napping 4 ( +0)
verified 54 ( +0)
assigned 150 ( +0)
committed 19 ( +0)
documented 3 ( +0)
done/needs work 18 ( +0)
Issues Created Or Reopened (1)
______________________________
: file.el compiles to null file.elc 2011-09-09
http://tracker.xemacs.org/XEmacs/its/issue801 created aidan
Top Issues Most Discussed (1)
_____________________________
3 : file.el compiles to null file.elc 4 days
None http://tracker.xemacs.org/XEmacs/its/issue801
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hi, XEmacs!
Yes, I've just released CC Mode 5.32.1. A link to download it can be
found at <http://cc-mode.sourceforge.net/release.php>.
It will now compile properly on XEmacs (thanks, Aidan). Apart from
that, there are one or two minor-ish bugs fixed. Oh, and the proper
copyright/license statements are now in place. ;-(
--
Alan Mackenie (Nuremberg, Germany).
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Nelson Ferreira writes:
> Ok, I may have been mislead by Mike's email that anonscm.debian.org
> was to be the permanent replacement of alioth.
Yes, that *was* correct, and the replacement of CVS by Mercurial was a
long-term project. But anonscm.debian.org only works for anonymous
checkouts and updates. There is no working replacement for
cvs.alioth.debian.org (the old domain for r/w CVS), and it seems that
Debian is not going to do anything about that. So the transition to
Mercurial became pretty urgent.
> As far as I'm concern as a developer of SXEmacs, no harm done, and
> I also apologize if my message was interpreted in a harsher tone
> than just a wish.
Not at all, it's just that the messages from Mats and me crossed in
the mail so maybe it looks like we're more sensitive than we are.
And in any case, we consider SXEmacs a very friendly fork and we'd
like to keep it that way.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Michael Sperber <sperber(a)deinprogramm.de> writes:
> Aidan Kehoe <kehoea(a)parhasard.net> writes:
>
>> Ar an triú lá déag de mí Meitheamh, scríobh Michael Sperber:
>>
[...]
>>
>> Any progress on this? I’m still getting the above message.
>
> They finally got back to me:
>
> cvs.alioth.debian.org offers only read-only access per design,
> apparently. We're now supposed to use
>
> cvs.debian.org
>
> Seems to work for me ...
alioth is not working for anonymous checkout (or update):
njsf@neumann:~/Projects/XEmacs/packages$ cvs update
cvs [update aborted]: unrecognized auth response from cvs.alioth.debian.org: cvs [pserver aborted]: /cvsroot/xemacs: no such repository
njsf@neumann:~/Projects/XEmacs$ cvs -z3 -d :pserver:anonymous@cvs.alioth.debian.org:/cvsroot/xemacs \
> checkout packages
cvs [checkout aborted]: unrecognized auth response from cvs.alioth.debian.org: cvs [pserver aborted]: /cvsroot/xemacs: no such repository
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Ar an deichiú lá de mí Méan Fómhair, scríobh Alan Mackenzie:
> On Fri, Sep 09, 2011 at 11:14:29PM +0100, Aidan Kehoe wrote:
>
> > In general, there’s no particular problem with it, but you’re
> > interfering with the guts of byte-compilation in cc-defs.el, we don’t
> > (and can’t really) guarantee that functions with side effects like
> > #'set-buffer won’t cause problems if those side effects aren’t wrapped,
> > when you do something like that.
>
> OK. But cc-defs.el is included in every other cc-*.el, yet only causes
> (?appears to cause?) problems in cc-align.el. This worries me a bit.
It causes problems in cc-align.el because that’s the first file compiled and
the sequence of buffers made current is slightly different for the first
file compiled than for later files. I can equally provoke the (new) error
message like so:
$ /Sources/xemacs-21.5-buffer-warning/src/xemacs -batch -no-site-file -q -f batch-byte-compile cc-engine.el
Compiling /tmp/aidan/cc-mode-5.32/cc-engine.el...
While compiling toplevel forms in file /tmp/aidan/cc-mode-5.32/cc-engine.el:
!! Invalid state (("byte compiling didn't save-excursion appropriately" #<buffer "*Compile-Log*">))
>>Error occurred processing cc-engine.el: Invalid state: byte compiling didn't save-excursion appropriately, #<buffer "*Compile-Log*">
Killing the current buffer is analogous to this:
(let ((old-buffer (current-buffer)))
(set-buffer (other-buffer old-buffer))
(kill-buffer old-buffer))
and #'other-buffer doesn’t offer any guarantee that it will be particularly
predictable, neither in its documentation nor in its implementation. Wrap
your #'set-buffers.
> And it doesn't interfere with M-x byte-compile-file. That might worry
> you a bit. ;-)
Right now it throws the error for me if I call M-x byte-compile-file RET;
I’m glad it no longer fails silently.
> The cc-defs.el fix does indeed work for me. I'll get CC Mode 5.32.1
> released as soon as I can, which might be the middle of next week.
Great!
--
‘Iodine deficiency was endemic in parts of the UK until, through what has been
described as “an unplanned and accidental public health triumph”, iodine was
added to cattle feed to improve milk production in the 1930s.’
(EN Pearce, Lancet, June 2011)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Ar an deichiú lá de mí Méan Fómhair, scríobh Stephen J. Turnbull:
> [...]
OK, I’ve reproduced, and committed the below. Thank you both!
APPROVE COMMIT
NOTE: This patch has been committed.
# HG changeset patch
# User Aidan Kehoe <kehoea(a)parhasard.net>
# Date 1315657049 -3600
# Node ID d19b6e3bdf91e4e1f99857e9973c86fa2bebb40c
# Parent b039c0f018b81507efbf95589e9ad11eaae6d45f
#'cl-defsubst-expand; avoid mutually-recursive symbol macros.
lisp/ChangeLog addition:
2011-09-10 Aidan Kehoe <kehoea(a)parhasard.net>
* cl-macs.el (cl-defsubst-expand):
Change set 2a6a8da4dd7c of
http://mid.gmane.org/19966.17522.332164.615228@parhasard.net
wasn't sufficiently comprehensive, symbol macros can be mutually
rather than simply recursive, and they can equally hang. Thanks
for the bug report, Michael Sperber, and for the test case,
Stephen Turnbull.
diff -r b039c0f018b8 -r d19b6e3bdf91 lisp/ChangeLog
--- a/lisp/ChangeLog Fri Sep 09 22:50:31 2011 +0100
+++ b/lisp/ChangeLog Sat Sep 10 13:17:29 2011 +0100
@@ -1,3 +1,13 @@
+2011-09-10 Aidan Kehoe <kehoea(a)parhasard.net>
+
+ * cl-macs.el (cl-defsubst-expand):
+ Change set 2a6a8da4dd7c of
+ http://mid.gmane.org/19966.17522.332164.615228@parhasard.net
+ wasn't sufficiently comprehensive, symbol macros can be mutually
+ rather than simply recursive, and they can equally hang. Thanks
+ for the bug report, Michael Sperber, and for the test case,
+ Stephen Turnbull.
+
2011-09-09 Aidan Kehoe <kehoea(a)parhasard.net>
* bytecomp.el (byte-compile-from-buffer):
diff -r b039c0f018b8 -r d19b6e3bdf91 lisp/cl-macs.el
--- a/lisp/cl-macs.el Fri Sep 09 22:50:31 2011 +0100
+++ b/lisp/cl-macs.el Sat Sep 10 13:17:29 2011 +0100
@@ -3236,10 +3236,20 @@
(let* ((symbol-macros nil)
(lets (mapcan #'(lambda (argn argv)
(if (or simple (cl-const-expr-p argv))
- (progn (or (eq argn argv)
- (push (list argn argv)
- symbol-macros))
- (and unsafe (list (list argn argv))))
+ (progn
+ ;; Avoid infinite loop on symbol macro
+ ;; expansion, make sure none of the argvs
+ ;; refer to the symbols in the argns.
+ (or (block find
+ ;; Can't use cl-expr-contains, that
+ ;; doesn't descend lambdas:
+ (subst nil argn argvs :test
+ #'(lambda (elt tree)
+ (if (eq elt tree)
+ (return-from find t))))
+ nil)
+ (push (list argn argv) symbol-macros))
+ (and unsafe (list (list argn argv))))
(list (list argn argv))))
argns argvs)))
`(let ,lets
--
‘Iodine deficiency was endemic in parts of the UK until, through what has been
described as “an unplanned and accidental public health triumph”, iodine was
added to cattle feed to improve milk production in the 1930s.’
(EN Pearce, Lancet, June 2011)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta