Fatal error: QUIT called from within redisplay without being properly wrapped
17 years, 3 months
Klaus Reim
Klaus Reim
Hi Gents,
I succeeded in triggering the following assertion:
Fatal error: assertion failed, file signal.c, line 730, QUIT called from within
redisplay without being properly wrapped
I saw this first when trying to switch from a shell buffer
which was receiving process output to another buffer
via buffers pulldown menu selection.
Later when experimenting I found that the assertion can
be triggered by just randomly (frantically) clicking on a menubar item
(i.e. just pulling the menu-pane down and up again
and not selecting any menuitem is sufficient).
The important thing is that a process buffer must be on
display getting filled at a relatively high rate.
When experimenting I used to create a shell process: M-x shell
and ran the following shell commands:
sh
while true; do sleep 0.001; echo 'good by!'; done
(The more bytes are echoed, the better. Just echoing 'good by!' makes reproducing
the effect impossible on my machine ?!)
Then just multi-clicking on the "Buffers" cascade-button triggers the assertion
within seconds.
This assertion is easily reproduced with optimized as well as debug versions,
with today's HEAD version, as well as with a CVS date-tagged version
"-D 2005-01-27", i.e. a version having received the above assertion-code
about one day before:
revision 1.29
date: 2005/01/26 10:33:42; author: ben; state: Exp; lines: +22 -156
Fix some race conditions in redisplay/signal
(...)
Seems that adding the assertion was a good thing, since at least one
bad race still seems to go on somewhere ...
Please find more details below,
happy debugging,
and a a happy new year!
Klaus
Here is my configure command:
configure --with-package-path=/home/klr/xemacs/lib/xemacs/xemacs-packages --infodir=/home/klr/xemacs/xemacs-21.5/info --with-infopath=/home/klr/xemacs/xemacs-packages --with-athena=3d --with-xpm --with-png --with-jpeg --with-tiff --with-gif --with-gpm=yes --with-sound=native --with-pop --with-clash-detection --with-canna=yes --with-wnn=yes --with-xim=xlib --with-database=no --with-postgresql=no --with-ldap=no --with-hesiod=no --with-widgets=athena --with-menubars=lucid --with-scrollbars=lucid --with-dialogs=athena --with-msw=no
Lisp backtrace:
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (catch #<INTERNAL OBJECT (XEmacs bug?) (opaque, size=0) 0x84a60ac> ...)
# (unwind-protect ...)
# bind (inhibit-quit)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# bind (inhibit-quit)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
("(in redisplay)" "[internal]")
# (unwind-protect ...)
sit-for(0)
# (unwind-protect ...)
# bind (window)
#<compiled-function (window) "...(123)" [current selected scroll process comint-scroll-show-maximum-output window window-buffer window-point process-mark t all this others set-window-point pos-visible-in-window-p recenter floatp floor window-height 1 -1 sit-for 0 string] 4>(#<window on "*shell*" 0x3163e>)
# bind (walk-windows-current walk-windows-start arg which-devices which-frames minibuf function)
walk-windows(#<compiled-function (window) "...(123)" [current selected scroll process comint-scroll-show-maximum-output window window-buffer window-point process-mark t all this others set-window-point pos-visible-in-window-p recenter floatp floor window-height 1 -1 sit-for 0 string] 4> nil t)
# bind (scroll process current selected string)
comint-postoutput-scroll-to-bottom("good bye\n")
run-hook-with-args(comint-postoutput-scroll-to-bottom "good bye\n")
# bind (obuf opoint obeg oend oprocbuf string process)
comint-output-filter(#<process "bash" pid 27009 state:run> "good bye\n")
("execute_internal_event()" "[internal]")
(dispatch-event "[internal]")
# (condition-case ... . error)
# (catch top-level ...)
[1] Abort xemacs (core dumped)
Core stacktrace:
#0 0xffffe410 in ?? ()
#1 0xbfffb7dc in ?? ()
#2 0x000028d6 in ?? ()
#3 0x00000006 in ?? ()
#4 0x403415f6 in kill () from /lib/tls/libc.so.6
#5 0x080d587b in fatal_error_signal (sig=6) at emacs.c:3734
#6 <signal handler called>
#7 0xffffe410 in ?? ()
#8 0xbfffbad8 in ?? ()
#9 0x00000006 in ?? ()
#10 0x000028d6 in ?? ()
#11 0x403412c1 in raise () from /lib/tls/libc.so.6
#12 0x40342b75 in abort () from /lib/tls/libc.so.6
#13 0x080d7c22 in really_abort () at emacs.c:4596
#14 0x080d594f in assert_failed (file=0x82a9477 "signal.c", line=730,
expr=0x82a9510 "QUIT called from within redisplay without being properly wrapped") at emacs.c:3919
#15 0x08203b6e in check_quit () at signal.c:728
#16 0x08203724 in check_what_happened () at signal.c:458
#17 0x080df714 in Ffuncall (nargs=2, args=0xbfffbd08) at eval.c:3776
#18 0x080e0ff0 in call1 (fn=146269744, arg0=146614668) at eval.c:4497
#19 0x0825adb3 in menu_item_descriptor_to_widget_value_1 (desc=146614668,
menu_type=1, deep_p=1, filter_p=0, depth=0) at menubar-x.c:218
#20 0x0825b119 in protected_menu_item_descriptor_to_widget_value_1 (
gack=0xbfffc0a0) at menubar-x.c:353
#21 0x080e1b41 in call_trapping_problems_2 (opaque=147103872) at eval.c:4885
#22 0x080dc6dc in call_with_condition_handler (
handler=0x80e1a9f <flagged_a_squirmer>, handler_arg=147103872,
fun=0x80e1b0c <call_trapping_problems_2>, arg=147103872) at eval.c:2135
#23 0x080e1b61 in call_trapping_problems_1 (opaque=147103872) at eval.c:4891
#24 0x080dba86 in internal_catch (tag=147103776,
func=0x80e1b46 <call_trapping_problems_1>, arg=147103872,
threw=0xbfffbf8c, thrown_tag=0xbfffbf98, backtrace_before_throw=0xbfffbf90)
at eval.c:1530
#25 0x080e1f7b in call_trapping_problems (warning_class=146388360,
warning_string=0x82b1f35 "Error during menu callback", flags=35,
problem=0x0,
fun=0x825b0e0 <protected_menu_item_descriptor_to_widget_value_1>,
arg=0xbfffc0a0) at eval.c:5164
#26 0x080f4b96 in event_stream_protect_modal_loop (
error_string=0x82b1f35 "Error during menu callback",
bfun=0x825b0e0 <protected_menu_item_descriptor_to_widget_value_1>,
barg=0xbfffc0a0, flags=32) at event-stream.c:1934
#27 0x0825b185 in protected_menu_item_descriptor_to_widget_value (
desc=146614704, menu_type=1, deep_p=1, filter_p=0) at menubar-x.c:382
#28 0x0825b30d in pre_activate_callback (widget=0x8527170, unused_id=65537,
client_data=0x8537200) at menubar-x.c:476
#29 0x0827ef9e in pre_hook (w=0x8527170, client_data=0x8526ff0,
call_data=0x8537200) at lwlib-Xlw.c:82
#30 0x4016b806 in XtCallCallbackList () from /usr/X11R6/lib/libXt.so.6
#31 0x0827a566 in remap_menubar (mw=0x8527170) at xlwmenu.c:2524
#32 0x0827bd87 in handle_single_motion_event (mw=0x8527170, ev=0xbfffc6f0,
select_p=1 '\001') at xlwmenu.c:3269
#33 0x0827be70 in handle_motion_event (mw=0x8527170, ev=0xbfffc6f0,
select_p=1 '\001') at xlwmenu.c:3301
#34 0x0827bf78 in Start (w=0x8527170, ev=0xbfffc6f0, unused_params=0x0,
unused_num_params=0x401b1c64) at xlwmenu.c:3339
#35 0x401a47e7 in XtInstallAllAccelerators () from /usr/X11R6/lib/libXt.so.6
#36 0x401a4bc4 in XtInstallAllAccelerators () from /usr/X11R6/lib/libXt.so.6
#37 0x401a5288 in _XtTranslateEvent () from /usr/X11R6/lib/libXt.so.6
#38 0x4017a7f3 in XtDispatchEventToWidget () from /usr/X11R6/lib/libXt.so.6
#39 0x4017b02a in XtDispatchEventToWidget () from /usr/X11R6/lib/libXt.so.6
#40 0x40179e5f in XtDispatchEvent () from /usr/X11R6/lib/libXt.so.6
#41 0x40187a18 in XtAppProcessEvent () from /usr/X11R6/lib/libXt.so.6
#42 0x0823d4f3 in emacs_Xt_drain_queue () at event-Xt.c:2834
#43 0x0823d56c in check_if_pending_expose_event (dev=0x8c25d20)
at event-Xt.c:2855
#44 0x0824f97a in x_window_output_end (w=0x8ceb440) at redisplay-x.c:307
#45 0x081eb027 in redisplay_output_window (w=0x8ceb440)
at redisplay-output.c:2494
#46 0x081d9587 in redisplay_window (window=147764288, skip_selected=0)
at redisplay.c:6534
#47 0x081d9fd6 in redisplay_frame (f=0x8cea954, preemption_check=1)
at redisplay.c:6940
#48 0x081da472 in redisplay_device (d=0x8c25d20, automatic=1)
at redisplay.c:7021
#49 0x081dabcd in redisplay_without_hooks () at redisplay.c:7096
#50 0x081dae93 in redisplay_no_pre_idle_hook () at redisplay.c:7167
#51 0x081dae4e in redisplay () at redisplay.c:7149
#52 0x080f639b in Fsit_for (seconds=1, nodisplay=146404744)
at event-stream.c:2873
#53 0x080df9b3 in Ffuncall (nargs=2, args=0xbfffcab4) at eval.c:3847
#54 0x0809ac14 in execute_optimized_program (
program=0x862988c "Æ\r!\batÇ\r!È\v!W«3\nÉa¬'\nÊa¬\"\nËa«\006\t\ra¬\030\nÌa«\006\t\ra«\016Ç\r!È\v!\016\027GZY«\bÍ\rÈ\v!\"\210\f6Ç\r!È\v!Y-Îd\r\"?&\212Í\rd\"\210Ï\f¨«\004\fª\021Ð\f!«\vÑÒ\r!\f_Ó\"ª\002Ô\r\"\210ÕÖ!)\207",
stack_depth=4, constants_data=0x860c1a8) at bytecode.c:823
#55 0x080e7225 in funcall_compiled_function (fun=141853772, nargs=1,
args=0xbfffcd08) at eval.c:3457
#56 0x080dfc6f in Ffuncall (nargs=2, args=0xbfffcd04) at eval.c:3886
#57 0x0809ac14 in execute_optimized_program (
program=0x85a7bc8 "Æ\f!«\004\fª\aÇ\v!\002\v\032ÈÉ\n!!«\003Ê\021É\n!\211\030\035Ë\r\t\f\v$\025\016\f\r!\210\r\ba?\003ªí+\207\025`®+1", stack_depth=6,
constants_data=0x8c40620) at bytecode.c:823
#58 0x080e7225 in funcall_compiled_function (fun=147616096, nargs=3,
args=0xbfffcf58) at eval.c:3457
#59 0x080dfc6f in Ffuncall (nargs=4, args=0xbfffcf54) at eval.c:3886
#60 0x0809ac14 in execute_optimized_program (
program=0x85e5588 "Å \032p\034Æ\f!\033\t\030\v\006ÇÈÉÊ#,\207",
stack_depth=4, constants_data=0x85f503c) at bytecode.c:823
#61 0x080e7225 in funcall_compiled_function (fun=141853816, nargs=1,
args=0xbfffd2fc) at eval.c:3457
#62 0x080dfc6f in Ffuncall (nargs=2, args=0xbfffd2f8) at eval.c:3886
#63 0x080e0be2 in run_hook_with_args_in_buffer (buf=0x842a114, nargs=2,
args=0xbfffd2f8, cond=RUN_HOOKS_TO_COMPLETION) at eval.c:4360
#64 0x080e0c92 in run_hook_with_args (nargs=2, args=0xbfffd2f8,
cond=RUN_HOOKS_TO_COMPLETION) at eval.c:4380
#65 0x080e08c6 in Frun_hook_with_args (nargs=2, args=0xbfffd2f8) at eval.c:4255
#66 0x080dfbe2 in Ffuncall (nargs=3, args=0xbfffd2f4) at eval.c:3870
#67 0x0809ac14 in execute_optimized_program (
program=0x85a1b64 "Æ\016\022!\211\036\023\205\227", stack_depth=5,
constants_data=0x860c140) at bytecode.c:823
#68 0x080e7225 in funcall_compiled_function (fun=141853640, nargs=2,
args=0xbfffd554) at eval.c:3457
#69 0x080dfc6f in Ffuncall (nargs=3, args=0xbfffd550) at eval.c:3886
#70 0x080e104d in call2 (fn=141835920, arg0=140559064, arg1=140257088)
at eval.c:4513
#71 0x081c0d16 in read_process_output (process=140559064, read_stderr=0)
at process.c:1095
#72 0x080f67b1 in execute_internal_event (event=140287344)
at event-stream.c:3014
#73 0x080f97a5 in Fdispatch_event (event=140287344) at event-stream.c:4642
#74 0x080a8a8f in Fcommand_loop_1 () at cmdloop.c:600
#75 0x080a884b in command_loop_1 (unused_dummy=146404744) at cmdloop.c:505
#76 0x080dbfcd in condition_case_1 (handlers=146401592,
bfun=0x80a881b <command_loop_1>, barg=146404744,
hfun=0x80a846b <cmd_error>, harg=146404744) at eval.c:1924
#77 0x080a857b in command_loop_3 () at cmdloop.c:262
#78 0x080a859e in command_loop_2 (unused_dummy=146404744) at cmdloop.c:275
#79 0x080dba86 in internal_catch (tag=146168912,
func=0x80a8593 <command_loop_2>, arg=146404744, threw=0x0, thrown_tag=0x0,
backtrace_before_throw=0x0) at eval.c:1530
#80 0x080a868b in initial_command_loop (load_me=146404744) at cmdloop.c:313
#81 0x080d4718 in xemacs_21_5_b24_i686_pc_linux (argc=1, argv=0xbfffdf84,
unused_envp=0x0, restart=0) at emacs.c:2624
#82 0x080d50cc in main (argc=1, argv=0xbfffdf84, unused_envp=0xbfffdf8c)
at emacs.c:3064
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
No sounds other than console beep; what's wrong?
17 years, 3 months
robert delius royar
robert delius royar
I do not know which CVS first exhibited this problem, but it first
showed up when I recompiled XEmacs 21.5.28b after upgrading to Mac OS X
10.5.1. The newest changelog in the tree is dated 2007-12-21, but
version.sh is no longer being updated in CVS.
I have included installation info at the end of this message.
I can no longer get XEmacs to play sounds through my (working) Enlighten
Sound Daemon (v 2.38). I have verified that ESD is working on the
system (launched at startup and plays through 127.0.0.1:16001). I
verified this by playing
/usr/local/share/xemacs/xemacs-packages/etc/sounds/boing.wav with
esdplay; I also verified that sound-extension-list is ".wav" and that
load-default-sounds reports "Loading sounds..." and "Loading
sounds...done".
However, no sounds play in XEmacs other than the system beep. And
device-sound-enabled-p returns nil.
nm xemacs shows
00156710 T _Fdevice_sound_enabled_p
00156a2c T _Fplay_sound
0015726c T _Fplay_sound_file
00156734 T _Fwait_for_sounds
00757b54 S _Q_sound
00754e14 S _Qshow_sounds
00756c70 S _Qsound
00757b5c S _Qsound_error
00201934 d _SFdevice_sound_enabled_p
002018d4 d _SFplay_sound
002018bc d _SFplay_sound_file
00201904 d _SFwait_for_sounds
00757b60 S _Vnative_sound_only_on_console
00757b64 S _Vsound_alist
00757b68 S _Vsynchronous_sounds
00070b18 T _esd_play_sound_data
00070af4 T _esd_play_sound_file
0015677c T _init_device_sound
001574fc T _report_sound_error
00156944 T _syms_of_sound
00156780 T _vars_of_sound
which indicates that XEmacs is including the esd-specific functions.
One thing I wonder about is that Apple changed its designations for X
servers to be the form /tmp/launch-6randomchars/:0 from the older 0:0
format. I only mention this because some software has been reported to
have problems with this change.
What additional information could I supply to help track this down?
Installation File
uname -a: Darwin grendel.frinabulax.org 9.1.0 Darwin Kernel Version 9.1.0: Wed Oct 31 17:48:21 PDT 2007; root:xnu-1228.0.2~1/RELEASE_PPC Power Macintosh
./configure '--with-mule' '--with-widgets=athena' '--with-athena=3d' '--with-dialogs=athena' '--with-scrollbars=lucid' '--without-debug' '--with-union-type' '--without-error-checking' '--with-x11' '--prefix=/Users/royar/usr/local' '--with-png' '--with-jpeg' '--with-tiff' '--with-xmu' '--with-xim=no' '--enable-sound=esd' '--disable-xfs' '--enable-dump-in-exec' '--with-modules' '--enable-external-widget' '--with-dynamic' '--disable-kkcc' '--disable-mc-alloc' '--enable-optimization' '--with-cflags-optimization=-Os -pipe -mcpu=970 -mtune=970 -mpim-altivec' '--with-site-runtime-libraries=/opt/local/lib:/usr/X11/lib' '--with-site-libraries=/opt/local/lib:/usr/X11/lib' '--with-xft=emacs,gauges,notabs,nomenubars' '--with-compiler=gcc-4.2' 'CPPFLAGS=-I/opt/local/include' 'LDFLAGS=-L/opt/local/lib' 'CFLAGS='
XEmacs 21.5-b28 "fuki" (+CVS-20071205) configured for `powerpc-apple-darwin9.1.0'.
Compilation Environment and Installation Defaults:
Source code location: /Users/royar/src/xemacs
Installation prefix: /Users/royar/usr/local
Additional libraries: /opt/local/lib /usr/X11/lib
Operating system description file: `s/darwin.h'
Machine description file: `m/powerpc.h'
Compiler version: powerpc-apple-darwin9-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5531)
- GCC specs file: specs.
- Compiler command: gcc-4.2 -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts -Wpacked -Wpointer-arith -Wunused-parameter -g -Os -pipe -mcpu=970 -mtune=970 -mpim-altivec
libc version:
Relocating allocator for buffers: no
GNU version of malloc: no
- The GNU allocators don't work with this system configuration.
Window System:
Compiling in support for the X window system:
- X Windows headers location: /usr/X11/include
- X Windows libraries location: /usr/X11/lib
- Handling WM_COMMAND properly.
- Using fontconfig to manage fonts.
- Compiling in support for Xft antialiased fonts (EXPERIMENTAL).
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.
- Using Xft to render antialiased fonts in progress bars.
WARNING: This feature will be replaced with a face.
WARNING: This feature not yet implemented; setting ignored.
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.
Sound:
Compiling in support for ESD (Enlightened Sound Daemon).
Databases:
Compiling in support for Berkeley database.
Compiling in support for GNU DBM.
Compiling in support for LDAP.
Internationalization:
Compiling in support for Mule (multi-lingual Emacs).
Mail:
Compiling in support for "file" mail spool file locking method.
Other Features:
Inhibiting IPv6 canonicalization at startup.
Compiling in support for dynamic shared object modules.
Using the union type for Lisp_Objects.
WARNING: ---------------------------------------------------------
WARNING: This tends to trigger compiler bugs, especially when
WARNING: combined with MULE and ERROR_CHECKING. Crashes have
WARNING: been seen with various versions of GCC (up to about 2.95),
WARNING: and recently with Visual C++ as well (mid-2003).
WARNING: More recent versions may be safer, or not.
WARNING: ---------------------------------------------------------
Using the new portable dumper.
Dumping into executable.
--
Dr. Robert Delius Royar Associate Professor of English
Morehead State University Morehead, Kentucky
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
compare input methods: iso-accents-mode and quail
17 years, 3 months
Uwe Brauer
Uwe Brauer
Hello
I do not want to talk about coding systems but about input methods.
I will also presume the use an american keyboard. (Kubuntu 6.10)
I have not really used Mule on a regular base, so maybe what I am
going to ask sounds very basic.
On NoMule Xemacs I am used to iso-accents-mode which allows me to
generate latin1 characters such as "Spanish" and "German" characters
by typing 7bit ASCII code such as
'o --> ó
"a--> ä
Etc. I can restrict that only to Spanish or only to German.
(Although I did not want to talk a about coding these symbols are
later stored as unibyte 8859-1 chars.)
Two things I want to emphasize:
- I can toggle iso-accents-mode ON and OFF.
- I an iso-accentuate and iso-unaccentuate whole regions,
changing 8 bit to 7 bit and back.
In Mule, according to my understanding, the closest thing would be
using quail and there the "german-pre" and "spanish-pre" method (I
think one could still use iso-accents-mode but that is not my point
here.)
Now it seems
- I cannot toggle off these input methods.
- I cannot change the chars back to the 7bit ASCII, that is there
is not equivalent to iso-unaccentuate. I would find this
especially useful for the TeX-input we recently discussed.
Would it be possible to implement these two properties for quail?
thanks
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
- 3 participants
- 3 comments
XEmacs Packages have been pre-released (2007-12-31-11)
17 years, 3 months
Norbert Koch
Norbert Koch
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hey there everyone.
I have just added the following packages to the 'Pre-Releases'
directory:
New Packages in Pre-Release:
===========================
xemacs-devel-1.77-pkg.tar.gz upstream version: none
Previously Announced Packages Still in Pre-Release:
==================================================
apel-1.33-pkg.tar.gz upstream version: 10.6
auctex-1.48-pkg.tar.gz upstream version: 11.55
calendar-1.34-pkg.tar.gz upstream version: none
dired-1.18-pkg.tar.gz upstream version: 7.15
easypg-1.01-pkg.tar.gz upstream version: 0.0.15
ediff-1.72-pkg.tar.gz upstream version: 2.75
edit-utils-2.38-pkg.tar.gz upstream version: none
edt-1.14-pkg.tar.gz upstream version: none
efs-1.34-pkg.tar.gz upstream version: 1.24
elib-1.12-pkg.tar.gz upstream version: 1.0
eshell-1.12-pkg.tar.gz upstream version: 2.4.1
eudc-1.40-pkg.tar.gz upstream version: 1.32
general-docs-1.05-pkg.tar.gz upstream version: none
guided-tour-0.51-pkg.tar.gz upstream version: none
hm--html-menus-1.24-pkg.tar.gz upstream version: 5.9
hyperbole-1.17-pkg.tar.gz upstream version: 5.0
igrep-1.16-pkg.tar.gz upstream version: 2.111
latin-euro-standards-1.08-pkg.ta upstream version: 1.08
leim-1.26-pkg.tar.gz upstream version: none
locale-1.27-pkg.tar.gz upstream version: none
mh-e-1.31-pkg.tar.gz upstream version: 7.4.2
mule-base-1.52-pkg.tar.gz upstream version: none
mule-ucs-1.16-pkg.tar.gz upstream version: 0.84
net-utils-1.54-pkg.tar.gz upstream version: N/A
oo-browser-1.05-pkg.tar.gz upstream version: 4.08
os-utils-1.40-pkg.tar.gz upstream version: none
pcl-cvs-1.68-pkg.tar.gz upstream version: R-2_9_9
perl-modes-1.10-pkg.tar.gz upstream version: none
prog-modes-2.15-pkg.tar.gz upstream version: none
psgml-1.45-pkg.tar.gz upstream version: 1.3.2
python-modes-1.09-pkg.tar.gz upstream version: none
scheme-1.17-pkg.tar.gz upstream version: none
skk-1.24-pkg.tar.gz upstream version: 10.62a
text-modes-1.95-pkg.tar.gz upstream version: none
tramp-1.39-pkg.tar.gz upstream version: 2.0.56
vc-1.45-pkg.tar.gz upstream version: none
viper-1.59-pkg.tar.gz upstream version: 3.09
vm-7.26-pkg.tar.gz upstream version: 7.19
w3-1.34-pkg.tar.gz upstream version: 4.0pre47
xemacs-base-2.13-pkg.tar.gz upstream version: none
Detailed Changes:
================
- ------- ChangeLog Entries from xemacs-packages/xemacs-devel/ChangeLog -------
2007-12-31 Norbert Koch <viteno(a)xemacs.org>
* Makefile (VERSION): XEmacs package 1.77 released.
2007-12-30 Aidan Kehoe <kehoea(a)parhasard.net>
* find-func.el (find-function-C-source):
Accept built-in macros in this function.
Installing These:
================
Manually:
- --------
1) Download the packages that you want to install from:
/ftp.xemacs.org:/pub/xemacs/beta/experimental/packages/
2) Unpack them to: [1]
/usr/local/lib/xemacs/xemacs-packages/
3) Re-start XEmacs.
Using XEmacs Package Tools (XEmacs 21.[245].x):
- ----------------------------------------------
1) Tools -> Packages -> Add Download Site -> Pre-Releases
2) Tools -> Packages -> List and Install
3) Select the packages you wish to install (there are brief
instructions at the bottom of the packages buffer).
4) Packages -> Install/Remove Selected
5) Re-start XEmacs.
Using XEmacs Package Tools (XEmacs 21.1.14):
- -------------------------------------------
1) Options -> Manage Packages -> Add Download Site -> Pre-Releases
2) Options -> Manage Packages -> List and Install
3 - 5) As per XEmacs 21.[245].x.
norbert - XEmacs Package Release Manager.
Footnotes:
[1] Note: Mule packages should be installed into:
/usr/local/lib/xemacs/mule-packages/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHeL92gu3ywdHdhM0RApFHAKDufZijhs70oJ5+x08srW2DNf1ALwCeM8xC
POCoKzhkEn33K23W/BESsH0=
=mPnz
-----END PGP SIGNATURE-----
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Re: [PATCH] Abstract out a display-table-specific API (2)
17 years, 3 months
Stephen J. Turnbull
Stephen J. Turnbull
Mike Kupfer writes:
> >>>>> "ST" == Stephen J Turnbull <stephen(a)xemacs.org> writes:
>
> ST> The real solution is to have a standard-library package (or package
> ST> suite) which is shared between all reasonably recent XEmacs
> ST> versions. (This is the real long-term motivation for the
> ST> "bundled-packages" work.) Versions of XEmacs without C support for
> ST> certain features would have to do without, or perhaps use
> ST> inefficient Lisp versions.
>
> Is the plan that standard-library is available as an unbundled package,
> as well as being delivered with a given version of core?
"Plan"? No plan yet. The "batteries included" distribution (core +
packages) is an old ambition of Martin's, to tell the truth, and I see
it as a really easy way to make it easier for new users to get into
XEmacs.
The general idea is that the standard-library would be the stuff that
is documented in the Lispref but written in Lisp. I'd like to see
advances in font-lock and things like that be available to 21.4 users.
But I haven't thought carefully about how to make it work (thus
gaffes like "oh, go ahead and use functions that won't be available at
runtime, it'll just work...." :-P ).
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Re: [PATCH] Abstract out a display-table-specific API (2)
17 years, 3 months
Stephen J. Turnbull
Stephen J. Turnbull
mike.kupfer(a)xemacs.org writes:
> >>>>> "ST" == Stephen J Turnbull <stephen(a)xemacs.org> writes:
>
> ST> Make them defsubsts. ;-)
>
> ST> I'm not really joking about this case: I think it's a reasonable
> ST> answer even though a bit fragile. However, I acknowledge it's not a
> ST> good generic answer.
>
> I think a good generic answer would be to have 2 "futures" files: one
> for compile-time fixups and one that's available at run time, probably
> as part of xemacs-base.
>
> How does that sound?
The potential problem is that we don't have a good way to inform users
that they need Version X.Y of xemacs-base. If putting
runtime-future.el into xemacs-base was a good solution, I don't see
why we'd need a separate compile-time version.
Also, if you put it into xemacs-base, it gets compiled. The inability
to run uncompiled macros from bytecode means that in principle every
version of XEmacs needs a different compiled version of xemacs-base.
The history of the APEL package shows that this is a practical
problem, too.
The real solution is to have a standard-library package (or package
suite) which is shared between all reasonably recent XEmacs versions.
(This is the real long-term motivation for the "bundled-packages"
work.) Versions of XEmacs without C support for certain features
would have to do without, or perhaps use inefficient Lisp versions.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
- 2 participants
- 1 comments
Re: latin-ltx: works in 21.4.19 but with problems.
17 years, 3 months
Aidan Kehoe
Aidan Kehoe
Ar an triochadú lá de mí na Nollaig, scríobh Uwe Brauer:
> Aidan Kehoe wrote:
> > Ar an chéad lá is fiche de mí na Nollaig, scríobh Uwe Brauer:
>
> >> I boldly installed latin-ltx, form GNU emacs and it works in
> >> xemacs21.4.19 however there are some problems.
> >>
> >> - all Greek symbols are VERY small, I almost need a microscope.
>
> > The X11 font selection for non-Latin-1 non-East-Asian charsets was
> > very crazy, for a very long time. It's improved, but not quite
> > fixed, in XEmacs 21.5 ; see
> > http://mid.gmane.org/17741.4702.584611.225633＠parhasard.net ;
> > certainly this symptom is gone there.
>
> So basically you seem to say, that the problem with that small fonts
> can't be solved in 21.4 (other than rewriting huge part of the UTF8 stuff)?
You can fuck around with (a technical term, meaning, in standard English,
"fuck around with") #'set-face-font and the TAG-SET argument, perhaps using
#'define-specifier-tag as well, and it might be possible with your
particular X server and font path and available fonts, to tell the Mule
redisplay to use a font that's the same size as the Roman font. I believe
Stephen either managed it regularly or didn't care about Greek. I didn't
manage it without an order of magnitude more experimentation than was
sensible, which is why I wrote that patch.
> > Basically, we need to fix your x-symbol-with-21.5 problem and get
> > you transitioned to 21.5. It may be that I'll be procrastinating
> > enough in the new year that I will get to this.
>
> As I told you there had also been a x-symbol-with-21.4 Mule
> problem. Now since a while that seems better (I have the feeling that
> on older PC Xemacs run into memory problems and then did crazy things,
> since hardware has improved that problem might be less severe),
>
> Could you check whether either the setting
>
> x-symbol-8bits: nil
>
> Or
>
> x-symbol-8bits: t
> x-symbol-unique: t
>
> Help somehow in 21.5?
I would need to go back and look through my mail archives to remember what
the details of the problem were. Not tonight, sorry.
> 21.5 uhh, I am tempted since I begin to see that UTF-8 is important
> but I am afraid of getting my tex documents f....
I understand. I've changed the UTF-8 coding system to preserve invalid UTF-8
sequences on decoding and encoding, so any Latin-1 file loaded as UTF-8 and
written as such won't be corrupted--see
http://mid.gmane.org/18100.56639.409193.189959＠parhasard.net . This is also
true of the other Unicode coding systems.
(I want to add some display table magic to display invalid UTF-8 octets as
the corresponding Latin-1 characters, but in a different face; that’s in
progress, but I don’t have an ETA.)
> What do you think (and others) to convince the debian/ubuntu xemacs
> manager to put 21.5 in the experimental branch?
What are his priorities?
--
¿Dónde estará ahora mi sobrino Yoghurtu Nghé, que tuvo que huir
precipitadamente de la aldea por culpa de la escasez de rinocerontes?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Re: [PATCH] Abstract out a display-table-specific API (2)
17 years, 3 months
Aidan Kehoe
Aidan Kehoe
Ar an cúigiú lá is fiche de mí na Nollaig, scríobh mike.kupfer(a)xemacs.org:
> PS. Am I the only person getting bounces for Uwe?
No, you’re not. Stephen’s an ass, he knows many, perhaps most of the
non-XEmacs-internal package maintainer addresses don’t work, and he removed
my CVS access to the packages. I suppose you’ve heard from Robert
Widhopf-Fenk independent of the rest of us, Stephen?
> ----- The following addresses had permanent fatal errors -----
> <oub(a)xemacs.org>
> (reason: 554 <oub(a)ucmail.ucm.es>: Relay access denied)
--
¿Dónde estará ahora mi sobrino Yoghurtu Nghé, que tuvo que huir
precipitadamente de la aldea por culpa de la escasez de rinocerontes?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Re: [PATCH] Abstract out a display-table-specific API (2)
17 years, 3 months
Aidan Kehoe
Aidan Kehoe
Ar an ceathrú lá is fiche de mí na Nollaig, scríobh Mike Kupfer:
> >>>>> "Aidan" == Aidan Kehoe <kehoea(a)parhasard.net> writes:
>
> MikeK> Second, you appear to be introducing multiple copies of
> MikeK> put-display-table and get-display-table, both in this patch set and
> MikeK> in the patches you committed to xemacs-base and misc-games.
> MikeK> Shouldn't there be just one copy in the packages tree, presumably in
> MikeK> xemacs-base?
>
> Aidan> disp-table.el, which provides the display table
> Aidan> code--make-display-table, frob-display-table,
> Aidan> describe-display-table, and in
> Aidan> http://mid.gmane.org/18288.1954.87217.762309＠parhasard.net ,
> Aidan> put-display-table and get-display-table--is in core. Yeah,
> Aidan> there's a decent argument that it might be better in packages,
> Aidan> but it isn't there for the moment.
>
> I'm not sure we're understanding each other. I can understand having
> the functions in core in 21.5, plus a version in packages using
> defun-when-void for 21.4. What I'm saying is that there should only be
> *one* copy in packages, for use by all the packages. But your patches
> introduce duplicates in gnus, xemacs-base, misc-games, etc. Instead,
> put one copy in xemacs-base (case-table.el? new file?), and all the
> other packages can use that copy, yeah?
That introduces new package dependencies, something I’m not in a hurry to do
given how much Mike Sperber fucked up the package build last time he did
so. (And he still hasn’t fixed it!) The Gnus folk will probably approach the
thing differently anyway, and define a mm-put-display-table, but that is
their decision.
--
¿Dónde estará ahora mi sobrino Yoghurtu Nghé, que tuvo que huir
precipitadamente de la aldea por culpa de la escasez de rinocerontes?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Re: Running the carbon branch on 10.5.
17 years, 3 months
Aidan Kehoe
Aidan Kehoe
Ar an t-ochtú lá is fiche de mí na Nollaig, scríobh robert delius royar:
> Thu, 27 Dec 2007 (23:48 +0100 UTC) Aidan Kehoe wrote:
>
> > Ar an seachtú lá is fiche de mí na Nollaig, scríobh Malcolm Purvis:
> >
> > > Has anyone run the Carbon branch under 10.5?
> >
> > I haven’t. I hadn’t planned to buy 10.5, rather to switch to one of the free
> > unixes when support for 10.4 expires.
> >
> > > Building the current tip of the branch on my MacBook Pro, I get the
> > > following:
> > >
> > > $ open XEmacs.app
> > > LSOpenFromURLSpec() failed with error -10661 for the file /Users/malcolmp/builds/xemacs/sandboxen.hg/carbon2-head/carbon/XEmacs.app.
> > >
> > > The identical tree works on my 10.4.10 based PowerMac G5.
>
> Given that X11.app now runs automatically through launchd, what are the
> advantages of the carbon version over the X version?
Eye candy. (Don’t discount it as a factor to attract new users; I’m
impressed by how many Aquamacs users there are, and would really like to
leech that code. Not that we’ll get that many of them.)
Beyond that, the Carbon support for displaying non-ASCII characters is
really good, much better than any other platform we support. And
cut-and-paste with other OS X apps works consistently, whereas it is
unreliably inconsistent with the X11 build.
Also, it should be possible to implement drag and drop interoperability with
native OS X apps, something important for Mac users. Though it’s not yet
available.
--
¿Dónde estará ahora mi sobrino Yoghurtu Nghé, que tuvo que huir
precipitadamente de la aldea por culpa de la escasez de rinocerontes?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments