Re: sync auctex mercurial
10 years
The XEmacs Package Smoketest
The XEmacs Package Smoketest
>>>>> Uwe Brauer <oub(a)mat.ucm.es> writes:
> I think I have succeeded here comes the patch
> # HG changeset patch
[...]
I could apply the patch fine with just some rejects:
./Makefile.rej (Version number missmatch)
./preview/prv-emacs.el.rej (deleted!?)
./ChangeLog.auctex.rej (Some changes in respect to upstream.)
The good news is that building the package works fine. Now what? How
do I test this? Do you have some easy test descriptions that I can
follow?
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 3 participants
- 3 comments
Summary of XEmacs Issue Tracking System Issues
10 years
XEmacs Issue Tracking System
XEmacs Issue Tracking System
ACTIVITY SUMMARY (2014-12-02 - 2014-12-09)
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.
563 open ( +0) / 317 closed ( +0) / 880 total ( +0)
Open issues with patches: 13
Average duration of open issues: 1937 days.
Median duration of open issues: 2103 days.
Open Issues Breakdown
new 255 ( +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
- 1 participants
- 0 comments
sync auctex mercurial
10 years
Uwe Brauer
Uwe Brauer
Hi
It seems that I have at least a working synchronisation of our package
with auctex 11.88. However I have never used mercurial (and git for that
matter)
Can somebody please give me a pointer (mercurial in a nutshell)
especially I need,
- two remove 2 el files
- add around 70 new files
- commit but I prefer it either into a branch that someone could
check or as pre-release.
BTW would be good if we settle the numeration scheme.
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 3 participants
- 3 comments
xemacs crash
10 years
Ulrich Deiters
Ulrich Deiters
Dear friends,
after upgrading my OS from openSUSE 13.1 to 13.2, xemacs crashes
immediately after invocation. Here is the printout:
ukd＠iridium:~> architex/bin/architex UUU
Warning: Missing charsets in String to FontSet conversion
Warning: Missing charsets in String to FontSet conversion
Fatal error (11).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.
Your version of XEmacs was distributed with a PROBLEMS file that may
describe
your crash, and with luck a workaround. Please check it first, but do
report
the crash anyway.
Please report this bug by invoking M-x report-emacs-bug, or by selecting
`Send Bug Report' from the Help menu. If that won't work, send ordinary
email to `xemacs-beta(a)xemacs.org'. *MAKE SURE* to include this entire
output from this crash, especially including the Lisp backtrace, as well as
the XEmacs configuration from M-x describe-installation (or equivalently,
the file `Installation' in the top of the build tree).
*Please* try *hard* to obtain a C stack backtrace; without it, we are
unlikely
to be able to analyze the problem. Locate the core file produced as a
result
of this crash (often called `core' or `core.<process-id>', and located
in
the directory in which you started XEmacs or your home directory), and type
gdb /usr/bin/xemacs core
then type `where' at the debugger prompt. No GDB on your system? You may
have DBX, or XDB, or SDB. (Ask your system administrator if you need help.)
If no core file was produced, enable them (often with `ulimit -c unlimited')
in case of future reoccurrence of the crash.
Lisp backtrace follows:
# (unwind-protect ...)
# (unwind-protect ...)
# bind (inhibit-quit)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
redisplay-frame(#<x-frame "XEmacs" on #<x-device on ":0.0" 0x2> 0x2>)
# bind (ext gutter-string val inhibit-read-only frame value message)
raw-append-progress-feedback("Fontifying *scratch*..." 0 #<x-frame
"XEmacs" on #<x-device on ":0.0" 0x2> 0x2>)
# bind (tmsg top frame value message label)
append-progress-feedback(font-lock "Fontifying *scratch*..." 0 nil)
# bind (frame value message label)
display-progress-feedback(font-lock "Fontifying *scratch*..." 0)
# bind (str)
# (unwind-protect ...)
# bind (args value fmt label)
progress-feedback-with-label(font-lock "Fontifying %s..." 0 "*scratch*")
# bind (maybe-loudly end beg)
font-lock-default-unfontify-region(1 1 t)
# bind (loudly end beg)
font-lock-unfontify-region(1 1 t)
# bind (was-on font-lock-verbose font-lock-message-threshold aborted)
# (unwind-protect ...)
font-lock-default-fontify-buffer()
# bind (font-lock-verbose)
font-lock-fontify-buffer()
# bind (on-p maximum-size arg)
font-lock-mode(1)
turn-on-font-lock()
# bind (explicit-defaults)
font-lock-set-defaults()
# (unwind-protect ...)
# bind (command-line-args-left)
command-line()
# (condition-case ... . ((t (byte-code " ��" [error-data data
nil] 1))))
# bind (error-data)
normal-top-level()
# (condition-case ... . error)
# (catch top-level ...)
architex/bin/architex: Zeile 108: 2290 Speicherzugriffsfehler xemacs
-l $ATXHOME/interface/init.el -geometry +0+0
some background information: "ArchiTeX" is a text processor that abuses
XEmacs to write/edit XML documents, and then produces LaTeX and
ultimately PostScript code.
Here is the debugger analysis of the core file:
ukd＠iridium:~> gdb /usr/bin/xemacs core
GNU gdb (GDB; openSUSE 13.2) 7.8
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://bugs.opensuse.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
warning: /etc/gdbinit.d/gdb-heap.py: Datei oder Verzeichnis nicht gefunden
Reading symbols from /usr/bin/xemacs...(no debugging symbols found)...done.
[New LWP 2438]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `xemacs'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f6aa3fb2457 in kill () from /lib64/libc.so.6
Missing separate debuginfos, use: zypper install
xemacs-debuginfo-21.5.34-5.1.11.x86_64
(gdb) where
#0 0x00007f6aa3fb2457 in kill () from /lib64/libc.so.6
#1 0x00000000004a2a53 in fatal_error_signal ()
#2 <signal handler called>
#3 0x00007f6aa540d64e in XDrawLine () from /usr/lib64/libX11.so.6
#4 0x0000000000615bc0 in ?? ()
#5 0x00007f6aa595a4d4 in ?? () from /usr/lib64/libXt.so.6
#6 0x00007f6aa595c0ea in XtDispatchEventToWidget () from
/usr/lib64/libXt.so.6
#7 0x00007f6aa595c618 in ?? () from /usr/lib64/libXt.so.6
#8 0x00007f6aa595c769 in XtDispatchEvent () from /usr/lib64/libXt.so.6
#9 0x00007f6aa5967c7e in XtAppProcessEvent () from /usr/lib64/libXt.so.6
#10 0x00000000005e3fc1 in ?? ()
#11 0x00000000005e910d in check_if_pending_expose_event ()
#12 0x00000000005f7007 in ?? ()
#13 0x000000000057a863 in redisplay_output_window ()
#14 0x000000000057235d in ?? ()
#15 0x0000000000572f24 in redisplay_frame ()
#16 0x0000000000573bde in Fredisplay_frame ()
#17 0x00000000004adcf4 in Ffuncall ()
#18 0x0000000000473061 in execute_optimized_program ()
#19 0x00000000004adeae in Ffuncall ()
#20 0x0000000000473061 in execute_optimized_program ()
#21 0x00000000004adeae in Ffuncall ()
#22 0x0000000000473061 in execute_optimized_program ()
---Type <return> to continue, or q <return> to quit---
Can you make sense out of this?
Kind regards,
Ulrich Deiters
--
Prof. Dr. Ulrich K. Deiters ______________________________________
Institut f. Physikalische Chemie \ Luxemburger Str. 116, D-50939 Koeln
Universitaet zu Koeln /\/\... \ Tel. +49 (0)221 470-4543, Fax -4900
_______________________L|L|__|_____\ http://www.uni-koeln.de/deiters/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 2 participants
- 1 comments
Coverity scan
10 years
Jerry James
Jerry James
A few years ago, Vladimir Ivanovic created a project for XEmacs on
scan.coverity.com. He unfortunately never had time to do much with
it, though, so it has been dormant for awhile. I have taken over as
administrator from him and have uploaded new sources to scan. The
goods news is that there all only 197 defects in the resulting report.
It could have been more!
Anyway, I'm going to submit a few patches for issues found by
Coverity. If anyone else would like to join in, sign up on
scan.coverity.com and drop me a line to let me know.
Regards,
--
Jerry James
http://www.jamezone.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Summary of XEmacs Issue Tracking System Issues
10 years
XEmacs Issue Tracking System
XEmacs Issue Tracking System
ACTIVITY SUMMARY (2014-11-25 - 2014-12-02)
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.
563 open ( +0) / 317 closed ( +0) / 880 total ( +0)
Open issues with patches: 13
Average duration of open issues: 1930 days.
Median duration of open issues: 2096 days.
Open Issues Breakdown
new 255 ( +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
- 1 participants
- 0 comments