After several years of not updating my XEmacs from 21.4.17, I built and
installed 21.4.22 and upgraded all my packages. Whoa is me!
I have several problems:
1) If I grep for something I get the following:
Error in process sentinel: (wrong-type-argument stringp nil)
2) If I execute vc-print-log I get the following:
Error in process sentinel: (error Marker does not point anywhere)
3) If do a compiler, at the end of the compiler I get the following:
Error in process sentinel: (wrong-type-argument stringp nil)
What's going on here? Have things broken so badly?
I built XEmacs on SPARC Solaris-10 with the GCC 7.7.0 compiler.
Thanks!
...Jake
--
Jake Colman | Director, Software Development
Principia Partners LLC
101 West Elm Street | Conshohocken | PA 19428 | +1 (610) 755 9770
t: +1 (610) 755 9786 | c: +1 (610) 348 2788 | f: +1 (201) 221 8929
e: colman(a)ppllc.com | w: www.principiapartners.com
Credit technology innovation awards winner 2008, 2009 & 2010
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
ACTIVITY SUMMARY (2012-06-12 - 2012-06-19)
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.
544 open ( +0) / 286 closed ( +0) / 830 total ( +0)
Open issues with patches: 11
Average duration of open issues: 1153 days.
Median duration of open issues: 1215 days.
Open Issues Breakdown
new 221 ( +0)
deferred 6 ( +0)
napping 3 ( +0)
verified 55 ( +0)
assigned 152 ( +0)
committed 18 ( +0)
documented 3 ( +0)
done/needs work 17 ( +0)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
I came across an old post that indicated that the XEmacs X11 application
class was rename from Emacs to XEmacs to avoid conflicts with GNU
Emacs. But I just ran some quick tests and it looks like XEmacs honors
both class names. Is this correct?
--
Jake Colman | Director, Software Development
Principia Partners LLC
101 West Elm Street | Conshohocken | PA 19428 | +1 (610) 755 9770
t: +1 (610) 755 9786 | c: +1 (610) 348 2788 | f: +1 (201) 221 8929
e: colman(a)ppllc.com | w: www.principiapartners.com
Credit technology innovation awards winner 2008, 2009 & 2010
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
I upgraded my packages for the first time in quite sometime and it looks
like 'vc' is no longer working correctly.
When I execute vc-print-log I now see the following message in the
*warnings* buffer:
(2) (error/warning) Error in process sentinel: (error Marker does not point anywhere)
Point used to move to the entry in the CVS log that corresponds to the
revision of the file in the buffer for which I executed the command.
Now, I get this warning and point remains at the top of the
*vc-change-log* buffer.
I am using XEmacs 21.4.22.
Any ideas?
...Jake
--
Jake Colman | Director, Software Development
Principia Partners LLC
101 West Elm Street | Conshohocken | PA 19428 | +1 (610) 755 9770
t: +1 (610) 755 9786 | c: +1 (610) 348 2788 | f: +1 (201) 221 8929
e: colman(a)ppllc.com | w: www.principiapartners.com
Credit technology innovation awards winner 2008, 2009 & 2010
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
ACTIVITY SUMMARY (2012-06-05 - 2012-06-12)
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.
544 open ( +0) / 286 closed ( +0) / 830 total ( +0)
Open issues with patches: 11
Average duration of open issues: 1146 days.
Median duration of open issues: 1208 days.
Open Issues Breakdown
new 221 ( +0)
deferred 6 ( +0)
napping 3 ( +0)
verified 55 ( +0)
assigned 152 ( +0)
committed 18 ( +0)
documented 3 ( +0)
done/needs work 17 ( +0)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
ACTIVITY SUMMARY (2012-05-29 - 2012-06-05)
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.
544 open ( +1) / 286 closed ( +0) / 830 total ( +1)
Open issues with patches: 11
Average duration of open issues: 1139 days.
Median duration of open issues: 1201 days.
Open Issues Breakdown
new 221 ( +1)
deferred 6 ( +0)
napping 3 ( +0)
verified 55 ( +0)
assigned 152 ( +0)
committed 18 ( +0)
documented 3 ( +0)
done/needs work 17 ( +0)
Issues Created Or Reopened (1)
______________________________
excessive indentation in w3 1.37+ 2012-06-03
http://tracker.xemacs.org/XEmacs/its/issue832 created mike.kupfer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
I used macports to install xemacs on my Mac Pro. I've appended hardware and software information about the computer, as well as the installation info below.
I get a segmentation fault when I try to open a file called ProcessImage.py. If I copy ProcessImage.py to a new file named "foo", the file opens without a problem. If I copy ProcessImage.py to a new file named "foo.py", I get a segmentation error. If I copy ProcessImage.py to a new file named "foo.cc", I get a segmentation error. The segmentation error I get when I run xemacs ProcessImage.py is given below. I'm guessing the problem is something to do with the fontification of the programming languages.
I've looked hard for a core file but have had no luck. "ls -a ~" does not show any file with core in its name, and doing "ls-a ~ | grep core" returns nothing. Similarly, there is no file with "core" in its name in the directory from which xemacs was executed.
ls -a /cores returns nothing.
find /opt -name "core" -print | grep xemacs returns nothing.
find /opt -name "core.*" -print | grep xemacs returns nothing.
find /opt -name "core.*" -print returns a variety of file names related to python (they either have .py, .pyc, in their names or are in a python directory)
find /opt -name "core.*" -print | grep -v py returns nothing
If you can suggest another place to search for a core file, please let me know.
I have also done a fairly extensive search for a file called PROBLEMS in the /opt directory, including using the commands:
find /opt -name "*PROBLEMS*" -print
find /opt -name "*Problems*" -print
find /opt -name "*problems*" -print
The first two commands returned nothing, and the last returned the file: /opt/local/lib/xemacs-21.4.22/xemacs-packages/man/auctex/preview-problems.texi, but I didn't see anything relevant in that file.
Here is the xemacs output:
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 necessary, send
ordinary email to `xemacs-beta(a)xemacs.org'. *MAKE SURE* to include 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 /opt/local/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 recurrance of the crash.
Lisp backtrace follows:
dispatch-non-command-events()
# (condition-case ... . ((nil)))
progress-feedback-dispatch-non-command-events()
# bind (tmsg top frame value message label)
append-progress-feedback(font-lock "Fontifying ProcessImage.py..." 0 nil)
# bind (frame value message label)
display-progress-feedback(font-lock "Fontifying ProcessImage.py..." 0)
# bind (str)
# (unwind-protect ...)
# bind (args value fmt label)
progress-feedback-with-label(font-lock "Fontifying %s..." 0 "ProcessImage.py")
# bind (maybe-loudly end beg)
font-lock-default-unfontify-region(1 66730 t)
# bind (loudly end beg)
font-lock-unfontify-region(1 66730 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()
run-hooks(font-lock-set-defaults)
# bind (nomodes after-find-file-from-revert-buffer noauto warn error)
after-find-file(nil t)
byte-code("..." [buffer-file-number number truename buffer-file-truename buf buffer-file-name set-buffer-major-mode erase-buffer nil (byte-code ?????? ??\"???????? ??\"????" [rawfile filename insert-file-contents-literally t insert-file-contents] 3) ((file-error ...)) abbreviate-file-name file-name-directory make-local-variable backup-inhibited t after-find-file find-file-use-truenames default-directory backup-enable-predicate rawfile error nowarn] 3)
# (condition-case ... . ((t (byte-code "?!???? @ A\"??" ... 3))))
# (unwind-protect ...)
# bind (error number truename buf rawfile nowarn filename)
find-file-noselect("/Users/hogden/Documents/Changing/Programming/Python/ProcessImage/ProcessImage.py")
# bind (codesys filename)
find-file("/Users/hogden/Documents/Changing/Programming/Python/ProcessImage/ProcessImage.py")
# bind (dir file-count line end-of-options file-p arg tem)
command-line-1()
# bind (command-line-args-left)
command-line()
# (condition-case ... . ((t (byte-code " ??" ... 1))))
# bind (error-data)
normal-top-level()
# (condition-case ... . error)
# (catch top-level ...)
Segmentation fault
Computer info:
Model Name: Mac Pro
Model Identifier: MacPro4,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 2.66 GHz
Number Of Processors: 2
Total Number Of Cores: 8
L2 Cache (per core): 256 KB
L3 Cache (per processor): 8 MB
Memory: 20 GB
Processor Interconnect Speed: 6.4 GT/s
Boot ROM Version: MP41.0081.B08
SMC Version (system): 1.39f5
SMC Version (processor tray): 1.39f5
Serial Number (system): H00253XX20H
Serial Number (processor tray): C070206007RDCVHAE
Hardware UUID: 4B7EDD0C-AE94-5A11-924C-90D32D96C2FE
System Software Overview:
System Version: Mac OS X 10.6.8 (10K549)
Kernel Version: Darwin 10.8.0
Boot Volume: Macintosh HD
Boot Mode: Normal
Computer Name: embedded.lanl.gov
User Name: hogden (hogden)
Secure Virtual Memory: Enabled
64-bit Kernel and Extensions: No
Time since boot: 5 days 2:13
results from M-x describe-installation:
uname -a: Darwin embedded.lanl.gov 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 i386
./configure '--prefix=/opt/local' '--mandir=/opt/local/share/man' '--without-postgresql' '--without-ldap' '--with-sound=none' '--pdump' '--site-prefixes=/opt/local' '--with-tty' '--with-dialogs=athena' '--with-widgets=athena' '--with-athena=3d' '--with-database=gdbm' '--with-mule'
XEmacs 21.4.22 "Instant Classic" configured for `i386-apple-darwin10.8.0'.
Compilation / Installation:
Source code location: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_editors_xemacs/xemacs/work/xemacs-21.4.22
Installation prefix: /opt/local
Additional prefixes: /opt/local
Operating system description file: `s/darwin.h'
Not using any machine description file
Compiler: /usr/bin/gcc-4.2 -pipe -O2 -arch x86_64
Compiler version: /usr/bin/gcc-4.2 on i386-apple-darwin10.8.0
Relocating allocator for buffers: no
GNU version of malloc: no
- The GNU allocators don't work with this system configuration.
libc: system-provided libc on i386-apple-darwin10.8.0
Window System:
Compiling in support for the X window system:
- X Windows headers location: /usr/X11/include
- X Windows libraries location:
- Handling WM_COMMAND properly.
Compiling in support for the Athena widget set:
- Athena headers location: X11/Xaw3d
- Athena library to link: Xaw3d
Using Lucid menubars.
Using Lucid scrollbars.
Using Athena dialog boxes.
Using Athena native widgets.
TTY:
Compiling in support for ncurses.
Images:
Compiling in support for GIF images (builtin).
Compiling in support for XPM images.
Compiling in support for PNG images.
Compiling in support for JPEG images.
Compiling in support for TIFF images.
Compiling in support for X-Face message headers.
Sound:
Databases:
Compiling in support for GNU DBM.
Internationalization:
Compiling in support for Mule (multi-lingual Emacs).
Compiling in support for XIM (X11R5+ I18N input method).
- Using raw Xlib to provide XIM support.
Mail:
Compiling in support for "dot-locking" mail spool file locking method.
Other Features:
Inhibiting IPv6 canonicalization at startup.
Compiling in support for dynamic shared object modules.
Using the new portable dumper.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hello
I sent this mail to the list via gmane and it did not pass it seems, so I
send it again.
>From time to time I receive documents or mail in which the
symbol ’ is used, as in j’ai instead of j'ai.
Now this is perfectly displayed (en encoded via UTF8) in
21.5.31 Mule, however I cannot find any input method for
this symbol.
Well this is not entirely true. latin-ltx includes it:
typing \rq results in ’
but this looks cumbersome.
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta