Re: pui-list broke for me
25 years, 10 months
Enrico Scholz
Enrico Scholz
Gleb Arshinov <gleb(a)broadbase.com> writes:
> Somewhere between 21.0.59 and 21.0.62. I get the following error (in
> both 21.0 and 21.2):
>
> Signaling: (wrong-type-argument stringp nil)
> string-match("＠" nil)
> (if (string-match "＠" (car search)) "/" "/anonymous＠")
> )
> [...]
I think the error is in package-get.el:316.
There should be
(unless (and no-remote (not (caar entries)))
instead of
(unless (and no-remote (caar entries))
Enrico
--
eMail: enrico.scholz(a)wirtschaft.tu-chemnitz.de
talk: ensc(a)ultra.csn.tu-chemnitz.de
- 1 participants
- 0 comments
extent-data in BBDB
25 years, 10 months
Gleb Arshinov
Gleb Arshinov
extent-data is obsoleted in 21.0 and is not available in 21.2. I'd
get error when trying to pop-up BBDB pop-up menu. How about the
following:
=== cd c:\src2\xemacs\cvs\xemacs-packages\comm\bbdb\lisp\
=== cvs diff -u bbdb-xemacs.el
Index: bbdb-xemacs.el
===================================================================
RCS file: /usr/CVSroot/XEmacs/xemacs-packages/comm/bbdb/lisp/bbdb-xemacs.el,v
retrieving revision 1.2
diff -u -r1.2 bbdb-xemacs.el
--- bbdb-xemacs.el 1998/10/13 02:38:09 1.2
+++ bbdb-xemacs.el 1999/02/02 07:16:43
＠＠ -56,7 +56,7 ＠＠
(set-specifier scrollbar-height (cons (current-buffer) 0)))
;; first delete existing extents
(map-extents (function (lambda (x y)
- (if (eq (extent-data x) 'bbdb)
+ (if (eq (extent-property x 'data) 'bbdb)
(delete-extent x))))
(current-buffer) (point-min) (point-max) nil)
(let ((rest bbdb-records)
＠＠ -273,7 +273,7 ＠＠
(let ((extent (or (extent-at (point) (current-buffer) 'highlight)
(error "")))
record field face)
- (or (eq (extent-data extent) 'bbdb)
+ (or (eq (extent-property extent 'data) 'bbdb)
(error "not a bbdb extent"))
(highlight-extent extent t) ; shouldn't be necessary...
(goto-char (extent-start-position extent))
=== Exit status: OK
In XEmacs 21.2 "Artemis" [Lucid] (i586-pc-win32) of Mon Feb 01 1999 on SLOTH
configured using `configure UNKNOWN'
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
Recent keystrokes:
C-f C-f C-f C-f C-f C-f C-f C-f C-f C-f C-f C-f C-f
C-f C-f C-f C-f C-f RET C-n C-n C-n C-n C-n C-n C-n
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-p C-p C-p C-p
C-p C-p C-p C-p C-p C-p C-p C-p C-p C-x k RET C-a C-x
k RET M-x x e TAB s u TAB BS TAB M-BS M-BS M-BS TAB
TAB C-g misc-user misc-user misc-user misc-user
Recent messages (most recent first):
Loading emacsbug...done
Quit
Loading emacsbug...
Making completion list...
Following cross-reference Known Bugs...done
Following cross-reference Known Bugs...
Selecting menu item Mailing Lists...done
Selecting menu item Mailing Lists...
Selecting menu item Thanks...done
Selecting menu item Thanks...
- 1 participants
- 0 comments
Re: Displaying pictures jogs disk
25 years, 10 months
Lars Magne Ingebrigtsen
Lars Magne Ingebrigtsen
Valdis.Kletnieks(a)vt.edu writes:
> Umm.. the kernel allocating swap pages to backing-store the pages
> of the X server that the image ends up in?
Yes, something like that seems to be the case. I've now switched
backing store off, and the machine is now silent all the time.
Thanks!
--
(domestic pets only, the antidote for overdose, milk.)
larsi(a)ifi.uio.no * Lars Magne Ingebrigtsen
- 1 participants
- 0 comments
Displaying pictures jogs disk
25 years, 10 months
Lars Magne Ingebrigtsen
Lars Magne Ingebrigtsen
This may be somewhat off topic.
Anyway.
I'm using a laptop computer as my X terminal, while I run XEmacs
(21.2) on a different machine. I have set the disk on the laptop to
go to "standby" mode when there is no disk activity. (I think
computers should be seen and not heard.)
The only two things that make the disk do something is when I read
text that requires new fonts to be loaded (which the X server on the
laptop is responsible for), and when I view pictures in XEmacs (for
instance, picons). I guess this is because the X server is doing
something or other, but why does XEmacs displaying pictures require
the X server to fiddle with the disk?
--
(domestic pets only, the antidote for overdose, milk.)
larsi(a)ifi.uio.no * Lars Magne Ingebrigtsen
- 2 participants
- 1 comments
pui-list broke for me
25 years, 10 months
Gleb Arshinov
Gleb Arshinov
Somewhere between 21.0.59 and 21.0.62. I get the following error (in
both 21.0 and 21.2):
Signaling: (wrong-type-argument stringp nil)
string-match("＠" nil)
(if (string-match "＠" (car search)) "/" "/anonymous＠")
)
(concat (if (string-match "＠" ...) "/" "/anonymous＠") (car search) ":" (if (string-match "/$" dir) dir (concat dir "/")) filename)
)
(let ((dir ...)) (concat (if ... "/" "/anonymous＠") (car search) ":" (if ... dir ...) filename))
)
(if (efs-ftp-path filename) filename (let (...) (concat ... ... ":" ... filename)))
)
package-get-remote-filename((nil "C:\\dl\\xemacs\\packages") "package-index.LATEST.pgp")
(let ((expn ...)) (if (and expn ...) (setq entries nil expanded expn)))
)
(if (and no-remote (caar entries)) nil (let (...) (if ... ...)))
)
(unless (and no-remote (caar entries)) (let (...) (if ... ...)))
)
(while entries (unless (and no-remote ...) (let ... ...)) (setq entries (cdr entries)))
)
(let ((entries package-get-remote) (expanded nil)) (while entries (unless ... ...) (setq entries ...)) (or expanded (and ... file)))
)
(if (file-name-absolute-p file) file (let (... ...) (while entries ... ...) (or expanded ...)))
)
package-get-locate-file("package-index.LATEST.pgp" t nil)
(or (package-get-locate-file package-get-base-filename t no-remote) (locate-data-file package-get-base-filename) package-get-base-filename)
)
package-get-locate-index-file(nil)
(or db-file (package-get-locate-index-file (not force-current)))
)
(expand-file-name (or db-file (package-get-locate-index-file ...)))
)
(setq db-file (expand-file-name (or db-file ...)))
)
package-get-update-base(nil t)
(if (and (boundp ...) package-get-base (or ... package-get-was-current)) nil (package-get-update-base nil force-current))
)
(unless (and (boundp ...) package-get-base (or ... package-get-was-current)) (package-get-update-base nil force-current))
)
package-get-require-base(t)
(lambda nil "List all packages and package information.\nThe package name, version, and description are displayed. From the displayed\nbuffer, the user can see which packages are installed, which are not, and\nwhich are out-of-date (a newer version is available). The user can then\nselect packages for installation via the keyboard or mouse." (interactive) (package-get-require-base t) (let (... ... start) (message "Creating package list ...") (sit-for 0) (set-buffer outbuf) (setq buffer-read-only nil) (buffer-disable-undo outbuf) (erase-buffer outbuf) (kill-all-local-variables) (use-local-map pui-display-keymap) (setq major-mode ...) (setq mode-name "Packages") (setq truncate-lines t) (unless package-get-remote ...) (if pui-list-verbose ... ...) (insert sep-string) (setq start ...) (mapcar ... ...) (insert sep-string) (insert ...) (set-buffer-modified-p nil) (setq buffer-read-only t) (pop-to-buffer outbuf) (delete-other-windows) (goto-char start) (setq pui-selected-packages nil) (setq pui-deleted-packages nil) (when ... ... ... ...) (clear-message)))()
call-interactively(pui-list-packages)
command-execute(pui-list-packages t)
execute-extended-command(nil)
call-interactively(execute-extended-command)
My package setting in .emacs are:
;;{{{ XEmacs package stuff
;; We want to cache packages locally, so don't delete them after
;; downloading
(setq package-get-remove-copy nil)
(setq package-get-dir "C:\\dl\\xemacs\\packages")
;; List of remote sites to contact for downloading packages
(setq package-get-remote
'(
(nil "C:\\dl\\xemacs\\packages") ; use package-get-dir as cache
("ftp.xemacs.org"
"/pub/xemacs/packages") ;real location of new packages
))
;; This function is called to install a package Package comes in the
;; form of .tar.gz file, so, this function just calls MKS tar to
;; expand it in the specified directory
(defun package-admin-install-function-gleb (file pkg-dir buf)
"Install function for MSK tar"
(let ( (default-directory pkg-dir) )
(call-process "tar" nil buf t "xzvf" file)
))
(setq package-admin-install-function
'package-admin-install-function-gleb)
;;}}}
;;{{{ EFS
'(efs-disable-netrc-security-check t t)
;'(efs-gateway-type (quote (proxy "ftp" ("-i" "-n" "-g" "-v"))))
'(efs-tmp-name-template "/tmp/efs")
; '(efs-gateway-host "engine.ecf.teradyne.com")
'(efs-use-passive-mode nil)
; '(efs-ftp-program-name "C:\\WinNT\\System32\\Ftp.exe")
'(efs-umask 22)
;;}}}
Reverting back to the older state of this function fixes the problem:
=== cd c:\src2\xemacs\cvs\xemacs-21.2\lisp\
=== cvs diff -u package-get.el
Index: package-get.el
===================================================================
RCS file: /usr/CVSroot/XEmacs/xemacs/lisp/package-get.el,v
retrieving revision 1.13.2.14
diff -u -r1.13.2.14 package-get.el
--- package-get.el 1999/01/13 19:12:51 1.13.2.14
+++ package-get.el 1999/02/02 06:29:08
＠＠ -946,9 +946,7 ＠＠
(if (efs-ftp-path filename)
filename
(let ((dir (cadr search)))
- (concat (if (string-match "＠" (car search))
- "/"
- "/anonymous＠")
+ (concat "/"
(car search) ":"
(if (string-match "/$" dir)
dir
=== Exit status: OK
Gleb
- 1 participants
- 0 comments
Pointer images wrong at 16bpp?
25 years, 10 months
Hrvoje Niksic
Hrvoje Niksic
In my .emacs, I have a variation of default.emacs code that sets the
gc glyph to `recycle.xpm':
(set-glyph-image gc-pointer-glyph
(expand-file-name "recycle.xpm" data-directory))
However, the colors don't come out right -- the recycle symbol pointer
comes out in a single sickly darkish green tone, instead of the nice
color. In fact, it looks the way it used to look look on my 8bit
display when I would run out of colors. As I run under a 16bpp
TrueColor display, that should be moderately impossible.
To prove the latter point, inserting it in a buffer results in nice
colors. So I wonder if there is an explanation for that. Does the
code that instantiates pointers differ from the code that handles
buffer images?
Oh yes, I've also tried replacing "recycle.xpm" with "recycle2.xpm";
the result was a smaller *black* recycle symbol instead of green. :-(
- 3 participants
- 3 comments
Re: Pointer images wrong at 16bpp?
25 years, 10 months
Raymond Toy
Raymond Toy
>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes:
Hrvoje> Glynn Clements <glynn(a)sensei.co.uk> writes:
>> XCreatePixmapCursor only accepts pixmaps of depth 1, so the cursor
>> can only have two colours (plus a mask).
Hrvoje> This is strange. How come this worked right under my old, 8bit
Hrvoje> display?
>> My guess (and it is just that) is that on an PseudoColor display,
>> the foreground and background colours would often be allocated
>> adjacent colourmap cells, resulting in one being odd and the other
>> being even, whilst on a DirectColor display, the values would be
>> fixed.
Hrvoje> I'm not sure I can follow you, and I'm not strong on the X terminology
Hrvoje> either, so please bear with me. As far as I know, my old visual was
Hrvoje> 8bit PseudoColor, while my new visual is 16bit TrueColor (the latter
Hrvoje> is reported by xdpyinfo.) It continues to amaze me that on a
Hrvoje> TrueColor display XEmacs is unable to get the pointer drawn right.
Hrvoje> Can this really be right?
I'm with Hrvoje here. If I remember right (my linux box is dead right
now with a scrambled partition table), my 16-bit truecolor Linux
box shows the recycle icon with the fluorescent green. My 24-bit
truecolor Sun box shows it as a puke green. My only guess is the Sun's
openwin X11 server can't do the right thing. I'm running X11R6.3 on
the Sun with the openwin X11 server, and XFree 3.xx (Redhat 5.1) on my
Linux box.
It would bother me less if they were the same color, but they're not.
Ray
- 1 participants
- 0 comments
Re: Pointer images wrong at 16bpp?
25 years, 10 months
Hrvoje Niksic
Hrvoje Niksic
Glynn Clements <glynn(a)sensei.co.uk> writes:
> XCreatePixmapCursor only accepts pixmaps of depth 1, so the cursor
> can only have two colours (plus a mask).
This is strange. How come this worked right under my old, 8bit
display?
> My guess (and it is just that) is that on an PseudoColor display,
> the foreground and background colours would often be allocated
> adjacent colourmap cells, resulting in one being odd and the other
> being even, whilst on a DirectColor display, the values would be
> fixed.
I'm not sure I can follow you, and I'm not strong on the X terminology
either, so please bear with me. As far as I know, my old visual was
8bit PseudoColor, while my new visual is 16bit TrueColor (the latter
is reported by xdpyinfo.) It continues to amaze me that on a
TrueColor display XEmacs is unable to get the pointer drawn right.
Can this really be right?
- 2 participants
- 1 comments
[crash] 21.2-b8 SEGV in purification
25 years, 10 months
Karl Kleinpaste
Karl Kleinpaste
I haven't seen one of these before. XEmacs was running Gnus which was
in the middle of acquiring new mail; my mailbox had been moved to
.gnus-crash-box but its contents had not yet been split out.
XEmacs 21.2-b8, RH5.2 Linux w/2.2.1, XFree 3.3.3.1. The particular
process was quite recent; it had only been started about an hour before.
Program received signal SIGSEGV, Segmentation fault.
0x8085816 in marked_p (obj=149284140) at alloc.c:4117
4117 return PURIFIED (lheader) || MARKED_RECORD_HEADER_P (lheader);
(gdb) bt
#0 0x8085816 in marked_p (obj=149284140) at alloc.c:4117
#1 0x80b7c11 in finish_marking_weak_hash_tables (
obj_marked_p=0x80857e0 <marked_p>, markobj=0x80823b8 <mark_object>)
at elhash.c:1178
#2 0x80841bb in garbage_collect_1 () at alloc.c:4477
#3 0x80c1202 in Ffuncall (nargs=4, args=0xbfffd724) at eval.c:3135
#4 0x8090eec in execute_optimized_program (
program=0x88faac4 "\212\b\t\nÃÄÅÆÇ!ÆÈ!Ã\036\t\036\n\036\013\036\f\036\r\036\016\032\031\030ÏÐ!\210\016\021§«\a\016\021ÒV«\005ÓÔ!\210\016\013q\210\016\025Ö±\002\210e\026\t×\016\td\"\210\016\tb\210Ø\bÃÙ#«\tÚÖÃÙ#\210ªò\016\tb\210Ø\tÃÙ#«\tÚÖÃÙ#\210ªò\016\tb\210Ø\nÃÙ#«\tÚÅÃÙ#\210ªòÛÃ\016\td#\210\016\tb\210ÜÖ!«\aÝÞ!\210ªöm¬?Ä\026\rßÞàÃwá\\{P\026\f\016\tb\210Ø\016\fÃÙ#«\016ÚÅÃÙ#\210\016\rT\026\rªì\016\râY«Ñr\016\nq\210ã"..., stack_depth=9, constants_data=0x8838b68)
at bytecode.c:750
#5 0x809081d in funcall_compiled_function (fun=142815592, nargs=2,
args=0xbfffd84c) at bytecode.c:530
#6 0x80c1589 in Ffuncall (nargs=3, args=0xbfffd848) at eval.c:3221
#7 0x8090eec in execute_optimized_program (
program=0x88faa24 "\212À\211\211\211\211\031\032\e\034\035eb\210ÆÇÀÈ#\211\024®\002e\023\f®\002d\024db\210ÉÊÀÈ#®\002d\022Ë\013\n\"\211\021\016\fV«\023\t\016\rW«\rÎÏÐÑ\013\n{\"Ò#ª\002Ó\211\025Ó\230?5\214e\f}\210eb\210ÆÔÀÈ#«\006À\177\210ª\022db\210ÕÖ!\210×y\210Øc\210ÙÖ!\210iÚU«\004Óª\002Û\rPc\210~).\006\207ofA\001", stack_depth=7, constants_data=0x8644438) at bytecode.c:750
#8 0x809081d in funcall_compiled_function (fun=142815648, nargs=0,
args=0xbfffda38) at bytecode.c:530
#9 0x80c1589 in Ffuncall (nargs=1, args=0xbfffda34) at eval.c:3221
#10 0x80c230a in run_hook_with_args_in_buffer (buf=0x8c6e888, nargs=1,
args=0xbfffda34, cond=RUN_HOOKS_TO_COMPLETION) at eval.c:3671
#11 0x80c2387 in run_hook_with_args (nargs=1, args=0xbfffda34,
cond=RUN_HOOKS_TO_COMPLETION) at eval.c:3684
#12 0x80c1ff6 in Frun_hooks (nargs=1, args=0xbfffda34) at eval.c:3539
#13 0x80c153b in Ffuncall (nargs=2, args=0xbfffda30) at eval.c:3206
#14 0x8090eec in execute_optimized_program (
program=0x83caf5c "ÀÁ!\210Â\013!\034Å\036\006\f\031\016\aÈs«\005\016\aª\017É\016\a!«\a\016\a\013!ª\003\016\a\036\nË\036\f\f¬\023\016\rÎ\016\017!\237\211\026\f!\210Ð\013!\210ªB\016\nÑa«\006Ë\026\fª7\016\nÒa«%Å\036\006eb\210ÓÔËÅ#\210Õy\210Ö\013×±\003\210\016\rÎ\016\017!\237\211\026\f!\210)ª\r\016\rÎ\016\017!\237\211\026\f!\210\016\f«\013\016\f\016\030B\211\026\030ª\004ed|,\207pabd)",
stack_depth=4, constants_data=0x87e0608) at bytecode.c:750
#15 0x809081d in funcall_compiled_function (fun=142474516, nargs=3,
args=0xbfffdb3c) at bytecode.c:530
#16 0x80c1589 in Ffuncall (nargs=4, args=0xbfffdb38) at eval.c:3221
#17 0x8090eec in execute_optimized_program (
program=0x88fa8b4 "ÀÁ\211\211\211\211\211\032\e\034\035\036\006\036\a\036\beb\210ÉÊÁÀ#«\006Ë\224b¬\016ÌÍ\016\016!!\210ÏÐ!\202#\001m?\205\036\001`\026\aÁ\024\016\aÑÒÁÀ#«\005`Sª\017ÓÔ!«\tm¬\006Õy\210ªô`}\210eb\210ÉÖÁÀ#«\b×Õ!\026\006ª\035\212ÉØÁÀ#«\aËy\210Ùc\210)Õy\210ÚÛ \211\026\006ܱ\003\210eb\210ÉÝÁÀ#¬\005Á\025ª\rÞ×Õ!!\025Ëy\210ßc\210àá!\210db\210~\210`\022\r«/Õy\210`\r\\\211\023b\210\013dU¬\a\013TdU«\005d\024ª\026Óâ!«\005\013"..., stack_depth=8,
constants_data=0x875f140) at bytecode.c:750
#18 0x809081d in funcall_compiled_function (fun=142421124, nargs=2,
args=0xbfffdc54) at bytecode.c:530
#19 0x80c1589 in Ffuncall (nargs=3, args=0xbfffdc50) at eval.c:3221
#20 0x8090eec in execute_optimized_program (
program=0x88f2064 "\b«\022\tÂa¬\004\013«\n\f¬\a\bÅDCª\003\016\006\036\006\212ÇÈ!q\210É \210\016\n\036\013Ì\016\r!\210)Î ÏU¬2eb\210\212ÐÑ!\210)ÒÓ!¬\006ÒÔ!«\nÕ\016\026\016\027\"\210ª\026ÒØ!«\nÙ\016\026\016\027\"\210ª\bÚ\016\026\016\027\"\210\016\e«\005\016\e \210Üp!*\207", stack_depth=3, constants_data=0x866cef8)
at bytecode.c:750
#21 0x809081d in funcall_compiled_function (fun=142421180, nargs=5,
args=0xbfffdd58) at bytecode.c:530
#22 0x80c1589 in Ffuncall (nargs=6, args=0xbfffdd54) at eval.c:3221
#23 0x8090eec in execute_optimized_program (
program=0x88ee7f4 "À\t!\032\t\eÄ\035Ä\036\006Ä\036\aÄ\036\bÉÊ\016\013\"\205", stack_depth=9, constants_data=0x87e06b0) at bytecode.c:750
#24 0x809081d in funcall_compiled_function (fun=142474572, nargs=4,
args=0xbfffde74) at bytecode.c:530
#25 0x80c1589 in Ffuncall (nargs=5, args=0xbfffde70) at eval.c:3221
#26 0x8090eec in execute_optimized_program (
program=0x877b944 "À\021Â\013\f\"\210ÅÆÇ\016\b\013$\207", stack_depth=5,
constants_data=0x886d720) at bytecode.c:750
#27 0x809081d in funcall_compiled_function (fun=143545080, nargs=2,
args=0xbfffdf80) at bytecode.c:530
#28 0x80c1589 in Ffuncall (nargs=3, args=0xbfffdf7c) at eval.c:3221
#29 0x8090eec in execute_optimized_program (
program=0x88ee5cc "\b.\t«\006Â\t!ª\002\013Ä\035\eÆ\013Ç\"\t\026\t\036\bÉÊ\016\b\"«\t\016\bË\225ÌOª\003\016\b)\013A＠\"*\207 usingQ", stack_depth=4,
constants_data=0x8628d20) at bytecode.c:750
#30 0x809081d in funcall_compiled_function (fun=140709760, nargs=2,
args=0xbfffe088) at bytecode.c:530
#31 0x80c1589 in Ffuncall (nargs=3, args=0xbfffe084) at eval.c:3221
#32 0x8090eec in execute_optimized_program (
program=0x8746544 "\b®_\tÂ\e\031\f®W\t¬\004\r®Q\013®\tÆÇ\t\016\b\"J8Â\030\211\e«\rÉ\0138\211\020«\006\bÊk«\004\rª0\b;«\006Ë\b!ª\016\bA＠;«\aÌ\t\b\"ª\002\b\211\020A＠Ík«\004\bª\017\bA＠¬\a\b＠ÍDª\004Î\b!**Â\036\017\211\030Â\036\020\211\030®\002\r\211\030;«\005Ë\b!\020Ñ\b!«\004Òª+\016\020¬\030ÓÔÕ\b＠Ö\b8Ík«\004ͪ\a×ØÖ\b8\"$\210ÙÚ!\210Û\b!\016\020¬\005ÜÍ!\210+G\016\035«\rÞß\b＠\"«\006à\t\b\"\210Âáâ\2171ã \211\026\017"..., stack_depth=9, constants_data=0x87ebd30)
at bytecode.c:750
#33 0x809081d in funcall_compiled_function (fun=142450436, nargs=2,
args=0xbfffe1a4) at bytecode.c:530
#34 0x80c1589 in Ffuncall (nargs=3, args=0xbfffe1a0) at eval.c:3221
#35 0x8090eec in execute_optimized_program (
program=0x8814714 "\bA\031\n®\006\013®\003\fT\032\r«\t\r§¬\005\fTª\t\r§«\004\rª\002Æ\n^\036\aÈ\036\tÈ\036\nÈ\036\013È\036\fÍÎÏ\"\210\t\203m\005Ð\t\211A\021＠\211\026\t＠\211\026\n\016\021\"J\026\013Ò\016\t8\211\026\f\203Y\002\016\023È\016\f\036\f\036\n\016\f;«\aÔ\016\f!ª6\016\f\016\023k«\005\016\023ª+\016\f＠;«\r\016\n«\tÕ\016\n\016\f\"ª\031\016\f«\021\016\n¬\r\016\fA＠Ök«\005\016\fª\005×\016\f!*\211\026\f\036\030\211\036\031¬\005\016\023ª\016\016\031;«\aÔ\016\031!ª\003\016\031\016\030¬\005\016\023ª\016\016\030;«\aÔ"..., stack_depth=7,
constants_data=0x87eeec0) at bytecode.c:750
#36 0x809081d in funcall_compiled_function (fun=142450492, nargs=1,
args=0xbfffe2b8) at bytecode.c:530
#37 0x80c1589 in Ffuncall (nargs=2, args=0xbfffe2b4) at eval.c:3221
#38 0x8090eec in execute_optimized_program (
program=0x84f0664 "À\031ÂÃ!\210\f¬\004Å \210\016\006«\b\016\a¬\004È \210\016\a«\031\016\a§¬\024À\036\tÉ \210)Ê\026\a\016\013Ìa«\004Í \210Î\016\aÀ\"\026\a\016\t«\017\016\a¬\013É \210Ï\016\a!\210ª\020\016\a?\003\016\t\036\tÏ\016\a!\210)ÂÐ!\210Ñ\016\a§\a\016\022＠\016\a]!)\207ñ\004\211", stack_depth=3,
constants_data=0x88ba798) at bytecode.c:750
#39 0x809081d in funcall_compiled_function (fun=143368084, nargs=1,
args=0xbfffe34c) at bytecode.c:530
#40 0x80c0d0f in Feval (form=145225624) at eval.c:3045
#41 0x80bc3bc in Fprogn (args=145225612) at eval.c:761
#42 0x80b20c8 in Fsave_excursion (args=145225612) at editfns.c:404
#43 0x80c0851 in Feval (form=145225576) at eval.c:2958
#44 0x80bc046 in Fif (args=149970128) at eval.c:677
#45 0x80c0851 in Feval (form=149970116) at eval.c:2958
#46 0x80c0e76 in Feval (form=145225540) at eval.c:3066
#47 0x80bc3bc in Fprogn (args=145225672) at eval.c:761
#48 0x80b20c8 in Fsave_excursion (args=145225672) at editfns.c:404
#49 0x80c0851 in Feval (form=145225528) at eval.c:2958
#50 0x80bc3bc in Fprogn (args=145225684) at eval.c:761
#51 0x81ed60a in Fsave_window_excursion (args=145225684) at window.c:5369
#52 0x80c0851 in Feval (form=145225516) at eval.c:2958
#53 0x80bdd78 in Funwind_protect (args=145225696) at eval.c:1485
#54 0x80c0851 in Feval (form=145225504) at eval.c:2958
#55 0x80bc3bc in Fprogn (args=145225744) at eval.c:761
#56 0x80bce94 in Flet (args=145225492) at eval.c:926
#57 0x80c0851 in Feval (form=145225432) at eval.c:2958
#58 0x80bc3bc in Fprogn (args=145225420) at eval.c:761
#59 0x80c1f91 in funcall_lambda (fun=145225768, nargs=1, args=0xbfffeb70)
at eval.c:3508
#60 0x80c0fa2 in Feval (form=145225840) at eval.c:3092
#61 0x80bc3bc in Fprogn (args=145225828) at eval.c:761
#62 0x80c1f91 in funcall_lambda (fun=145225876, nargs=0, args=0xbfffed0c)
at eval.c:3508
#63 0x80c15ac in Ffuncall (nargs=1, args=0xbfffed08) at eval.c:3229
#64 0x8090eec in execute_optimized_program (
program=0xbfffed50 "\b＠ \207ÿ\001", stack_depth=1,
constants_data=0x85d5ba8) at bytecode.c:750
#65 0x8094d9c in Fbyte_code (instructions=140877660, constants=140336024,
stack_depth=3) at bytecode.c:2400
#66 0x80c09ee in Feval (form=140723860) at eval.c:2986
#67 0x80be041 in condition_case_1 (handlers=140724028, bfun=0x80c0148 <Feval>,
barg=140723860, hfun=0x80be0b8 <run_condition_case_handlers>,
harg=137762196) at eval.c:1640
#68 0x80be480 in condition_case_3 (bodyform=140723860, var=137762196,
handlers=140724028) at eval.c:1718
#69 0x8091a0b in execute_rare_opcode (stack_ptr=0xbfffefa0,
program_ptr=0x84f01ca "\210\016\fAÑ\016\f＠\016\022·A＠! \210ª¤Î\016\f8\211\026\n«\233\016\n§¬\fÀ «\bÃÓÔ\217\210ª\213\016\f＠\fs¬\204\016\n\tW\203~ÿÀ \203yÿÃÕÖ\217\210\016\f＠\fB\024\202kÿ-\207-", opcode=Bcondition_case) at bytecode.c:1275
#70 0x8090cb0 in execute_optimized_program (
program=0x84f0154 "À «\006\tT\021ª\005Â\021Ã\024ÅÆ !?\205°",
stack_depth=6, constants_data=0x8607ea8) at bytecode.c:660
#71 0x809081d in funcall_compiled_function (fun=142475216, nargs=0,
args=0xbffff03c) at bytecode.c:530
#72 0x80c0d0f in Feval (form=145223108) at eval.c:3045
#73 0x80bc3bc in Fprogn (args=145223120) at eval.c:761
#74 0x80c1f91 in funcall_lambda (fun=145223144, nargs=0, args=0xbffff1d4)
at eval.c:3508
#75 0x80c15ac in Ffuncall (nargs=1, args=0xbffff1d0) at eval.c:3229
#76 0x8090eec in execute_optimized_program (
program=0xbffff224 "À \031Â\216\013\034Å\036\006Å\036\aÅ\036\bÉ\f!«\fÊË\f!Ì\f!\"\210ª\006Ë\f! \210.\006Å\207", stack_depth=4, constants_data=0x82ea2ac)
at bytecode.c:750
#77 0x8094d9c in Fbyte_code (instructions=137273920, constants=137274012,
stack_depth=9) at bytecode.c:2400
#78 0x80c09ee in Feval (form=137273896) at eval.c:2986
#79 0x80be041 in condition_case_1 (handlers=137274128, bfun=0x80c0148 <Feval>,
barg=137273896, hfun=0x80be0b8 <run_condition_case_handlers>,
harg=138887300) at eval.c:1640
#80 0x80be480 in condition_case_3 (bodyform=137273896, var=138887300,
handlers=137274128) at eval.c:1718
#81 0x8091a0b in execute_rare_opcode (stack_ptr=0xbffff4e4,
program_ptr=0x82ea586 "\210)\016\013A\211\026\013\204sÿ\t\211\026\013«\023\016\tÕ\016\013＠!^\026\t\016\013A\211\026\013¬ïÜÝ!\211\036\036«\fß\016\036!«\006\212à \210))\016\t.\a\207", opcode=Bcondition_case) at bytecode.c:1275
#82 0x8090cb0 in execute_optimized_program (
program=0x82ea4c0 "À\t!ÂÃÂ\211\211Ä\035\036\006\036\a\036\b\036\t\036\n\036\013Ã\026\tÌÍ!«\032\016\r:«\025\016\r＠\016\rAÎE\026\aÏÐ \016\a\"\026\bª\aÑ\026\aÎ\026\b\016\013\203\221", stack_depth=8, constants_data=0x82ea0e4)
at bytecode.c:660
#83 0x809081d in funcall_compiled_function (fun=137273516, nargs=1,
args=0xbffff5f8) at bytecode.c:530
#84 0x80c1589 in Ffuncall (nargs=2, args=0xbffff5f4) at eval.c:3221
#85 0x8090eec in execute_optimized_program (
program=0x82eaeb8 "\b?/Á\032Á\030Ã \034Å\f\016\006\"\036\aÈ\036\t\f\026\006Ê\016\a!\026\tË\016\f!\210\016\t\026\rÎ\016\tÏÈÐ$\211\026\f-\207",
stack_depth=5, constants_data=0x82eae60) at bytecode.c:750
#86 0x809081d in funcall_compiled_function (fun=137276956, nargs=1,
args=0xbffff700) at bytecode.c:530
#87 0x80c1589 in Ffuncall (nargs=2, args=0xbffff6fc) at eval.c:3221
#88 0x80c258f in call1 (fn=138887552, arg0=137762196) at eval.c:3834
#89 0x8105bcc in execute_internal_event (event=145033028)
at event-stream.c:3043
#90 0x8109352 in Fdispatch_event (event=145033028) at event-stream.c:4689
#91 0x80a01c8 in Fcommand_loop_1 () at cmdloop.c:578
#92 0x809ff59 in command_loop_1 (dummy=137762196) at cmdloop.c:493
#93 0x80be041 in condition_case_1 (handlers=137762308,
bfun=0x809ff0c <command_loop_1>, barg=137762196,
hfun=0x809f3f8 <cmd_error>, harg=137762196) at eval.c:1640
#94 0x80a03e0 in command_loop_2 (dummy=137762196) at cmdloop.c:255
#95 0x80bdc34 in internal_catch (tag=137837240,
func=0x80a03ac <command_loop_2>, arg=137762196, threw=0x0) at eval.c:1315
#96 0x809f837 in initial_command_loop (load_me=137762196) at cmdloop.c:304
#97 0x80b9af1 in xemacs_21_2_b8_i686_pc_linux (argc=5, argv=0xbffffa14,
envp=0xbffffa2c, restart=0) at emacs.c:1718
#98 0x80ba265 in main (argc=5, argv=0xbffffa14, envp=0xbffffa2c)
at emacs.c:2147
(gdb) list
4112 {
4113 struct lrecord_header *lheader = XRECORD_LHEADER (obj);
4114 #if defined (ERROR_CHECK_GC) && defined (USE_INDEXED_LRECORD_IMPLEMENTATION)
4115 assert (lheader->type <= last_lrecord_type_index_assigned);
4116 #endif
4117 return PURIFIED (lheader) || MARKED_RECORD_HEADER_P (lheader);
4118 }
4119 #ifndef LRECORD_STRING
4120 case Lisp_Type_String:
4121 {
(gdb) p lheader
No symbol "lheader" in current context.
(gdb) up
#1 0x80b7c11 in finish_marking_weak_hash_tables (
obj_marked_p=0x80857e0 <marked_p>, markobj=0x80823b8 <mark_object>)
at elhash.c:1178
1178 if (obj_marked_p (e->value))
(gdb) list
1173 break;
1174
1175 case HASH_TABLE_VALUE_WEAK:
1176 for (; e < sentinel; e++)
1177 if (!HENTRY_CLEAR_P (e))
1178 if (obj_marked_p (e->value))
1179 MARK_OBJ (e->key);
1180 break;
1181
1182 case HASH_TABLE_KEY_CAR_WEAK:
(gdb) p e->value
$1 = 149284140
(gdb) p/x e->value
$2 = 0x8e5e52c
uname -a: Linux beaver.jprc.com 2.1.131 #5 SMP Thu Dec 17 16:46:02 EST 1998 i686 unknown
./configure '--with-pop' '--with-mule' '--with-png'
XEmacs 21.2-b8 "Artemis" configured for `i686-pc-linux'.
Where should the build process find the source code? /home/karl/src/x/xemacs-21/xemacs-21.2.8
What installation prefix should install use? /usr/local
What operating system and machine description files should XEmacs use?
`s/linux.h' and `m/intel386.h'
What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch
Should XEmacs use the GNU version of malloc? yes
(Using Doug Lea's new malloc from the GNU C Library.)
Should XEmacs use the relocating allocator for buffers? yes
What window system should XEmacs use? x11
Where do we find X Windows header files? /usr/X11R6/include
Where do we find X Windows libraries? /usr/X11R6/lib
Compiling in support for XAUTH.
Compiling in support for XPM images.
Compiling in support for PNG image handling.
Compiling in support for (builtin) GIF image handling.
Compiling in support for JPEG image handling.
Compiling in support for TIFF image handling.
Compiling in native sound support.
Compiling in support for Berkeley DB.
Compiling in support for GNU DBM.
Compiling in support for ncurses.
Compiling in support for GPM (General Purpose Mouse).
Compiling in Mule (multi-lingual) support.
Compiling in XIM (X11R5+ I18N input method) support.
Using raw Xlib to provide XIM support.
Compiling in support for proper session-management.
Using Lucid menubars.
Using Lucid scrollbars.
Using Athena dialog boxes.
Compiling in DLL support.
movemail will use "dot-locking" for locking mail spool files.
Using POP for mail access.
Using Lisp_Objects with minimal tagbits.
Compiling in extra code for debugging.
Compiling in code for checking XEmacs memory usage.
WARNING: ---------------------------------------------------------
WARNING: Compiling in support for runtime error checking.
WARNING: XEmacs will run noticeably more slowly as a result.
WARNING: Error checking is on by default for XEmacs beta releases.
WARNING: ---------------------------------------------------------
- 1 participants
- 0 comments
Re: Pointer images wrong at 16bpp?
25 years, 10 months
Hrvoje Niksic
Hrvoje Niksic
SL Baur <steve(a)xemacs.org> writes:
> Hey! I like that shade of green. I like it a lot better than the
> fluourescent puke green. :-)
>
> I consider this a feature not a bug ...
I hope you are joking here. If you really like that shade of green,
we should make an icon of it and distribute it by default.
Anyway, through the years, I grew kind of attached to the fluorescent
puke green...
- 1 participants
- 0 comments