From dak at gnu.org Thu May 1 08:26:32 2008 From: dak at gnu.org (David Kastrup) Date: Thu, 01 May 2008 17:26:32 +0200 Subject: bug#174: 23.0.60; Bug in vc-register with interactive arg Message-ID: <85prs6rqon.fsf@lola.goethe.zz> Please write in English if possible, because the Emacs maintainers usually do not have translators to read other languages for them. Your bug report will be posted to the emacs-pretest-bug at gnu.org mailing list. Please describe exactly what actions triggered the bug and the precise symptoms of the bug: C-u C-x v i Debugger entered--Lisp error: (wrong-type-argument stringp (4)) get-file-buffer((4)) vc-register((4)) call-interactively(vc-register nil nil) In GNU Emacs 23.0.60.8 (i686-pc-linux-gnu, GTK+ Version 2.12.9) of 2008-05-01 on lola Windowing system distributor `The X.Org Foundation', version 11.0.10400090 configured using `configure '--prefix=/usr/local/emacs-21' '--without-toolkit-scroll-bars' 'CFLAGS=-g -O2 -fno-crossjumping'' Important settings: value of $LC_ALL: nil value of $LC_COLLATE: nil value of $LC_CTYPE: nil value of $LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC: nil value of $LC_TIME: nil value of $LANG: en_US.UTF-8 value of $XMODIFIERS: nil locale-coding-system: utf-8-unix default-enable-multibyte-characters: t Major mode: Debugger Minor modes in effect: shell-dirtrack-mode: t TeX-PDF-mode: t desktop-save-mode: t minibuffer-electric-default-mode: t iswitchb-mode: t tooltip-mode: t mouse-wheel-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t blink-cursor-mode: t global-auto-composition-mode: t auto-composition-mode: t auto-encryption-mode: t auto-compression-mode: t line-number-mode: t transient-mark-mode: t Recent input: C-u C-x v i M-x r e p o r t - e m a c s - b u Recent messages: Press C-c C-c when you are done editing. Registering /home/tmp/akt/Historismus_III.tex... Entering debugger... Back to top level. Quit Type C-x 4 C-o RET to restore the other window, C-M-v to scroll help. Entering debugger... -- David Kastrup, Kriemhildstr. 15, 44793 Bochum From dak at gnu.org Thu May 1 10:45:45 2008 From: dak at gnu.org (David Kastrup) Date: Thu, 01 May 2008 19:45:45 +0200 Subject: bug#175: 23.0.60; VCS problem when loading Message-ID: <853ap1c3zq.fsf@lola.goethe.zz> Please write in English if possible, because the Emacs maintainers usually do not have translators to read other languages for them. Your bug report will be posted to the emacs-pretest-bug at gnu.org mailing list. Please describe exactly what actions triggered the bug and the precise symptoms of the bug: This happens when loading the desktop, but is likely not related. Debugger entered--Lisp error: (error "Variable binding depth exceeds max-specpdl-size") find-auto-coding("/home/dak/tex/tr/troeltsch.cls,v" 8192) set-auto-coding("/home/dak/tex/tr/troeltsch.cls,v" 8192) insert-file-contents("/home/dak/tex/tr/troeltsch.cls,v" nil 0 8192) vc-insert-file("/home/dak/tex/tr/troeltsch.cls,v" "^[0-9]") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-fetch-master-state("/home/dak/tex/tr/troeltsch.cls") vc-rcs-checkout-model("/home/dak/tex/tr/troeltsch.cls") vc-rcs-state-heuristic("/home/dak/tex/tr/troeltsch.cls") apply(vc-rcs-state-heuristic "/home/dak/tex/tr/troeltsch.cls") vc-call-backend(RCS state-heuristic "/home/dak/tex/tr/troeltsch.cls") vc-state("/home/dak/tex/tr/troeltsch.cls") vc-default-mode-line-string(RCS "/home/dak/tex/tr/troeltsch.cls") apply(vc-default-mode-line-string RCS "/home/dak/tex/tr/troeltsch.cls") vc-call-backend(RCS mode-line-string "/home/dak/tex/tr/troeltsch.cls") vc-mode-line("/home/dak/tex/tr/troeltsch.cls") vc-find-file-hook() run-hooks(find-file-hook) after-find-file(nil t) find-file-noselect-1(# "~/tex/tr/troeltsch.cls" nil nil "~/tex/tr/troeltsch.cls" (32463 65037)) find-file-noselect("/home/dak/tex/tr/troeltsch.cls") desktop-buffer-preview("/home/dak/tex/tr/troeltsch.cls" "troeltsch.cls" nil) #[nil " ?A??\n \f#?" [desktop-buffer-major-mode desktop-buffer-mode-handlers desktop-buffer-file-name desktop-buffer-name desktop-buffer-misc desktop-restore-file-buffer] 4]() desktop-create-buffer(206 "/home/dak/tex/tr/troeltsch.cls" "troeltsch.cls" latex-mode (auto-fill-mode reftex-mode) 1 (nil nil) nil nil ((indent-tabs-mode) (buffer-file-coding-system . iso-latin-1-unix))) eval-buffer(# nil "/home/dak/.emacs.desktop" nil t) ; Reading at buffer position 66494 load-with-code-conversion("/home/dak/.emacs.desktop" "/home/dak/.emacs.desktop" t t) load("/home/dak/.emacs.desktop" t t t) desktop-read() #[nil "?? ??? \"?)\n?? ????" [key command-line-args desktop-save-mode inhibit-startup-screen "--no-desktop" delete nil desktop-read t] 4]() run-hooks(after-init-hook) command-line() normal-top-level() If Emacs crashed, and you have the Emacs process in the gdb debugger, please include the output from the following gdb commands: `bt full' and `xbacktrace'. If you would like to further debug the crash, please read the file /usr/local/emacs-21/share/emacs/23.0.60/etc/DEBUG for instructions. In GNU Emacs 23.0.60.8 (i686-pc-linux-gnu, GTK+ Version 2.12.9) of 2008-05-01 on lola Windowing system distributor `The X.Org Foundation', version 11.0.10400090 configured using `configure '--prefix=/usr/local/emacs-21' '--without-toolkit-scroll-bars' 'CFLAGS=-g -O2 -fno-crossjumping'' Important settings: value of $LC_ALL: nil value of $LC_COLLATE: nil value of $LC_CTYPE: nil value of $LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC: nil value of $LC_TIME: nil value of $LANG: en_US.UTF-8 value of $XMODIFIERS: nil locale-coding-system: utf-8-unix default-enable-multibyte-characters: t Major mode: Debugger Minor modes in effect: TeX-PDF-mode: t desktop-save-mode: t minibuffer-electric-default-mode: t tooltip-mode: t mouse-wheel-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t blink-cursor-mode: t global-auto-composition-mode: t auto-composition-mode: t auto-encryption-mode: t auto-compression-mode: t line-number-mode: t transient-mark-mode: t Recent input: > < M-x r e p o r t Recent messages: Sorting environment... Removing duplicates... done Applying style hooks... done Applying style hooks... done Sorting environment... Removing duplicates... done Applying style hooks... done Entering debugger... Mark set [2 times] Making completion list... -- David Kastrup, Kriemhildstr. 15, 44793 Bochum From drew.adams at oracle.com Thu May 1 13:20:47 2008 From: drew.adams at oracle.com (Drew Adams) Date: Thu, 1 May 2008 13:20:47 -0700 Subject: bug#176: 23.0.60; comment in dired-x.el Message-ID: <008801c8abc8$d7931a50$c2b22382@us.oracle.com> In dired-x.el: ;;; Brief Description: ;;; ;;; `dired-do-shell-command' is bound to `!' by dired.el. ;;; ;;; * Redefine `dired-do-shell-command' so it calls ;;; `dired-guess-shell-command'. There are no other occurrences of `dired-do-shell-command' in the file, so I don't see how it could be redefined there. In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600) of 2008-04-19 on LENNART-69DE564 Windowing system distributor `Microsoft Corp.', version 5.1.2600 configured using `configure --with-gcc (3.4) --no-opt --cflags -Ic:/g/include -fno-crossjumping' From drew.adams at oracle.com Thu May 1 13:51:07 2008 From: drew.adams at oracle.com (Drew Adams) Date: Thu, 1 May 2008 13:51:07 -0700 Subject: bug#177: 23.0.60; doc for read-from-minibuffer Message-ID: <008f01c8abcd$14683c40$c2b22382@us.oracle.com> Arg DEFAULT can now be a list. This is not reflected in the doc string. And the Elisp manual doc is not clear about what happens with non-nil READ and list-valued DEFAULT: If READ is non-`nil', then DEFAULT is also used as the input to `read', if the user enters empty input. Does this mean the whole list DEFAULT is passed to `read'. Allow me to mention also that letting DEFAULT be a list also breaks code that I have, FWIW... In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600) of 2008-04-19 on LENNART-69DE564 Windowing system distributor `Microsoft Corp.', version 5.1.2600 configured using `configure --with-gcc (3.4) --no-opt --cflags -Ic:/g/include -fno-crossjumping' From drew.adams at oracle.com Thu May 1 14:02:17 2008 From: drew.adams at oracle.com (Drew Adams) Date: Thu, 1 May 2008 14:02:17 -0700 Subject: bug#178: 23.0.60; C-h i puts point at end of dir menu, not start [eom] Message-ID: <009401c8abce$a3f1e1d0$c2b22382@us.oracle.com> Subject says it all. This is a regression. In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600) of 2008-04-19 on LENNART-69DE564 Windowing system distributor `Microsoft Corp.', version 5.1.2600 configured using `configure --with-gcc (3.4) --no-opt --cflags -Ic:/g/include -fno-crossjumping' From dak at gnu.org Thu May 1 14:56:22 2008 From: dak at gnu.org (David Kastrup) Date: Thu, 01 May 2008 23:56:22 +0200 Subject: bug#179: 23.0.60; Menu separators are not displayed Message-ID: <85hcdhadtl.fsf@lola.goethe.zz> Please write in English if possible, because the Emacs maintainers usually do not have translators to read other languages for them. Your bug report will be posted to the emacs-pretest-bug at gnu.org mailing list. Please describe exactly what actions triggered the bug and the precise symptoms of the bug: I have a menu looking like preview-menu's value is shown below. Documentation: This is the menu for preview-latex. Value: (keymap "Preview" (nil menu-item "Generate previews") (\(or\ toggle\)\ at\ point menu-item "(or toggle) at point" preview-at-point ([3 16 16] . " C-c C-p C-p")) (for\ environment menu-item "for environment" preview-environment ([3 16 5] . " C-c C-p C-e")) (for\ section menu-item "for section" preview-section ([3 16 19] . " C-c C-p C-s")) (for\ region menu-item "for region" preview-region ([3 16 18] . " C-c C-p C-r") :enable (preview-mark-active)) (for\ buffer menu-item "for buffer" preview-buffer ([3 16 2] . " C-c C-p C-b")) (for\ document menu-item "for document" preview-document ([3 16 4] . " C-c C-p C-d")) (nil menu-item "---") (nil menu-item "Remove previews") (at\ point menu-item "at point" preview-clearout-at-point ([3 16 3 16] . " C-c C-p C-c C-p")) (from\ section menu-item "from section" preview-clearout-section ([3 16 3 19] . " C-c C-p C-c C-s")) (from\ region menu-item "from region" preview-clearout ([3 16 3 18] . " C-c C-p C-c C-r") :enable (preview-mark-active)) (from\ buffer menu-item "from buffer" preview-clearout-buffer ([3 16 3 2] . " C-c C-p C-c C-b")) (from\ document menu-item "from document" preview-clearout-document ([3 16 3 4] . " C-c C-p C-c C-d")) (nil menu-item "---") (nil menu-item "Turn preamble cache") (on menu-item "on" preview-cache-preamble ([3 16 6] . " C-c C-p C-f")) (off menu-item "off" preview-cache-preamble-off ([3 16 3 6] . " C-c C-p C-c C-f")) (nil menu-item "---") (Customize menu-item "Customize" (keymap "Customize" (Browse\ options menu-item "Browse options" menu-function-194 (nil) :key-sequence nil) (Extend\ this\ menu menu-item "Extend this menu" menu-function-195 (nil) :key-sequence nil))) (Read\ documentation menu-item "Read documentation" preview-goto-info-page ([3 16 9] . " C-c C-p TAB")) (Report\ Bug menu-item "Report Bug" preview-report-bug (nil))) [back] and neither the separator lines nor the separator titles are shown. This menu was generated using (easy-menu-define preview-menu LaTeX-mode-map "This is the menu for preview-latex." '("Preview" "Generate previews" ["(or toggle) at point" preview-at-point] ["for environment" preview-environment] ["for section" preview-section] ["for region" preview-region (preview-mark-active)] ["for buffer" preview-buffer] ["for document" preview-document] "---" "Remove previews" ["at point" preview-clearout-at-point] ["from section" preview-clearout-section] ["from region" preview-clearout (preview-mark-active)] ["from buffer" preview-clearout-buffer] ["from document" preview-clearout-document] "---" "Turn preamble cache" ["on" preview-cache-preamble] ["off" preview-cache-preamble-off] "---" ("Customize" ["Browse options" (customize-group 'preview)] ["Extend this menu" (easy-menu-add-item nil '("Preview") (customize-menu-create 'preview))]) ["Read documentation" preview-goto-info-page] ["Report Bug" preview-report-bug])) In GNU Emacs 23.0.60.8 (i686-pc-linux-gnu, GTK+ Version 2.12.9) of 2008-05-01 on lola Windowing system distributor `The X.Org Foundation', version 11.0.10400090 configured using `configure '--prefix=/usr/local/emacs-21' '--without-toolkit-scroll-bars' 'CFLAGS=-g -O2 -fno-crossjumping'' Important settings: value of $LC_ALL: nil value of $LC_COLLATE: nil value of $LC_CTYPE: nil value of $LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC: nil value of $LC_TIME: nil value of $LANG: en_US.UTF-8 value of $XMODIFIERS: nil locale-coding-system: utf-8-unix default-enable-multibyte-characters: t Major mode: LaTeX Minor modes in effect: reftex-mode: t desktop-save-mode: t minibuffer-electric-default-mode: t tooltip-mode: t mouse-wheel-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t blink-cursor-mode: t global-auto-composition-mode: t auto-composition-mode: t auto-encryption-mode: t auto-compression-mode: t line-number-mode: t transient-mark-mode: t Recent input: C-x k C-x b b o g i f g o f o < C-/ < C-s h y p p e r r e f C-s C-s C-s C-x b p r e v C-g C-x o C-x C-f / h o m e p / t m p / a u c t e x / p r e v i e w / p r v - e m C-x 1 C-g C-s o n C-s m e n u C-s C-s C-s C-x b C-g C-x C-f m e n p r e v i e w . e l C-s m e n u C-s C-s C-s C-s C-s C-s C-h v p r e v i e w - m e n C-x o C-x b b i g f o o t . t e d i s s . t e x Recent messages: Quit Note: file is write protected Undo! Mark set Mark saved where search started Quit [2 times] Mark saved where search started [2 times] Quit Mark saved where search started Type C-x 1 to delete the help window, C-M-v to scroll help. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum From smcracraft at gmail.com Thu May 1 15:59:50 2008 From: smcracraft at gmail.com (Stuart Cracraft) Date: Thu, 01 May 2008 15:59:50 -0700 Subject: bug#180: GNU Emacs Lisp Message-ID: <481A4B66.9020805@cox.net> Hi All, I see that when running a program in GNU Emacs Lisp that errors in the message area below the mode-line but without a line-number corresponding to the line of the error in the source code being run. So, without the line number, it is hunt-and-peck, much harder to find the section of code with the problem. Is there a way to locate the erring S-expression more quickly? I have used edebug, by the way, and am seeking something like the above as well, unless edebug can stop exactly at the line in the source code where the S-expression is broken, without having to single-step it. Thanks ahead (anyone), Stuart From markus.triska at gmx.at Thu May 1 22:29:01 2008 From: markus.triska at gmx.at (Markus Triska) Date: Fri, 2 May 2008 07:29:01 +0200 (CEST) Subject: bug#181: 23.0.60; OSX: Case insensitive file name completion Message-ID: <20080502052901.C805083E036@mt-computer.local> On OSX 10.4.11, I have ~/Desktop and ~/DES.pdf. Until recently, when I did "C-x C-f ~/Des TAB", it would expand to Desktop. Now, both "DES.pdf" and "Desktop" are considered possible expansions of "Des". I see the point, because the default file system on OSX appears to be case insensitive. Still, it is a regression for me: I find the previous default behaviour of Emacs (which is also the default in 22.2) much better, since it often allows faster expansion if you know the stored case of a file. Is there a way to get it back? Thanks! In GNU Emacs 23.0.60.2 (i386-apple-darwin8.11.1, GTK+ Version 2.12.9) of 2008-04-29 on mt-computer.local Windowing system distributor `The XFree86 Project, Inc', version 11.0.40400000 configured using `configure '--disable-font-backend'' From cyd at stupidchicken.com Fri May 2 08:17:03 2008 From: cyd at stupidchicken.com (Chong Yidong) Date: Fri, 02 May 2008 11:17:03 -0400 Subject: bug#180: GNU Emacs Lisp Message-ID: <871w4k91n4.fsf@stupidchicken.com> > I see that when running a program in GNU Emacs Lisp > that errors in the message area below the mode-line but > without a line-number corresponding to the line of the > error in the source code being run. > > So, without the line number, it is hunt-and-peck, much > harder to find the section of code with the problem. Is there > a way to locate the erring S-expression more quickly? Set debug-on-error to t, and you will get a backtrace, which can be used to jump to the function that signalled the error (as well as the functions that called it). From smcracraft at gmail.com Fri May 2 08:29:30 2008 From: smcracraft at gmail.com (Stuart Cracraft) Date: Fri, 02 May 2008 08:29:30 -0700 Subject: bug#180: GNU Emacs Lisp In-Reply-To: <871w4k91n4.fsf@stupidchicken.com> References: <871w4k91n4.fsf@stupidchicken.com> Message-ID: <481B335A.5060400@cox.net> Chong, Thankyou very much. Stuart Chong Yidong wrote: >> I see that when running a program in GNU Emacs Lisp >> that errors in the message area below the mode-line but >> without a line-number corresponding to the line of the >> error in the source code being run. >> >> So, without the line number, it is hunt-and-peck, much >> harder to find the section of code with the problem. Is there >> a way to locate the erring S-expression more quickly? >> > > Set debug-on-error to t, and you will get a backtrace, which can be used > to jump to the function that signalled the error (as well as the > functions that called it). > > From don at donarmstrong.com Fri May 2 09:05:05 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Fri, 2 May 2008 09:05:05 -0700 Subject: Processed: Close In-Reply-To: <87lk2s9031.fsf@stupidchicken.com> References: <87lk2s9031.fsf@stupidchicken.com> Message-ID: Processing commands for control at emacsbugs.donarmstrong.com: > close 180 bug#180: GNU Emacs Lisp 'close' is deprecated; see http://emacsbugs.donarmstrong.com/Developer.html#closing. bug closed, send any further explanations to Stuart Cracraft > thanks Stopping processing here. Please contact me if you need assistance. Don Armstrong (administrator, Emacs bugs database) From don at donarmstrong.com Fri May 2 09:05:07 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Fri, 2 May 2008 09:05:07 -0700 Subject: bug#176: marked as done (23.0.60; comment in dired-x.el) References: <87iqxw8zwq.fsf@stupidchicken.com> <008801c8abc8$d7931a50$c2b22382@us.oracle.com> Message-ID: Your message dated Fri, 02 May 2008 11:54:29 -0400 with message-id <87iqxw8zwq.fsf at stupidchicken.com> and subject line Re: 23.0.60; comment in dired-x.el has caused the Emacs bug report #176, regarding 23.0.60; comment in dired-x.el to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact don at donarmstrong.com immediately.) -- 176: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=176 Emacs Bug Tracking System Contact don at donarmstrong.com with problems -------------- next part -------------- An embedded message was scrubbed... From: "Drew Adams" Subject: 23.0.60; comment in dired-x.el Date: Thu, 1 May 2008 13:20:47 -0700 Size: 5823 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080502/cbdb4fa8/attachment.eml -------------- next part -------------- An embedded message was scrubbed... From: Chong Yidong Subject: Re: 23.0.60; comment in dired-x.el Date: Fri, 02 May 2008 11:54:29 -0400 Size: 1343 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080502/cbdb4fa8/attachment-0001.eml From yazicivo at ttmail.com Fri May 2 07:32:55 2008 From: yazicivo at ttmail.com (Volkan YAZICI) Date: Fri, 02 May 2008 17:32:55 +0300 Subject: bug#182: 23.0.60; Broken C-M-\ after ctrl:swapcaps Message-ID: <871w4khj3c.fsf@alamut.mobiliz.com.tr> Hi, I switched my Caps_Lock and Control_L keys via $ setxkbmap -option "ctrl:swapcaps" command on a Turkish (Q Layout) keyboard because of buggy[1] Ctrl_L key of HP Pavilion dv6580et notebook. But this change broke my C-M-\ combination. In emacs, "C-h k C-M-\" doesn't produce anything, it still waits for an input with "Describe key (or click or menu item):" line. I don't know if this is a emacs specific problem, but xev outputs looks right: Pressed Key | xev keysym ----------------+----------- Caps_Lock | Control_L Alt_L | Alt_L AltGr[2] | ISO_Level3_Shift Asterisk | Asterisk AltGr-Asterisk | Backslash By the way, I know if its related but am running emacs within a screen session inside aterm. Here are some related environment variables: declare -x COLORFGBG="default;default;15" declare -x COLORTERM="rxvt-xpm" declare -x LANG="en_US.UTF-8" declare -x SHELL="/bin/bash" declare -x TERM="screen" declare -x TERMCAP="SC|screen|VT 100/ANSI X3.64 virtual terminal:\\ :DO=\\E[%dB:LE=\\E[%dD:RI=\\E[%dC:UP=\\E[%dA:bs:bt=\\E[Z:\\ :cd=\\E[J:ce=\\E[K:cl=\\E[H\\E[J:cm=\\E[%i%d;%dH:ct=\\E[3g:\\ :do=^J:nd=\\E[C:pt:rc=\\E8:rs=\\Ec:sc=\\E7:st=\\EH:up=\\EM:\\ :le=^H:bl=^G:cr=^M:it#8:ho=\\E[H:nw=\\EE:ta=^I:is=\\E)0:\\ :li#54:co#146:am:xn:xv:LP:sr=\\EM:al=\\E[L:AL=\\E[%dL:\\ :cs=\\E[%i%d;%dr:dl=\\E[M:DL=\\E[%dM:dc=\\E[P:DC=\\E[%dP:\\ :im=\\E[4h:ei=\\E[4l:mi:IC=\\E[%d@:ks=\\E[?1h\\E=:\\ :ke=\\E[?1l\\E>:vi=\\E[?25l:ve=\\E[34h\\E[?25h:vs=\\E[34l:\\ :ti=\\E[?1049h:te=\\E[?1049l:us=\\E[4m:ue=\\E[24m:so=\\E[3m:\\ :se=\\E[23m:mb=\\E[5m:md=\\E[1m:mr=\\E[7m:me=\\E[m:ms:\\ :Co#8:pa#64:AF=\\E[3%dm:AB=\\E[4%dm:op=\\E[39;49m:AX:\\ :vb=\\Eg:G0:as=\\E(0:ae=\\E(B:\\ :ac=\\140\\140aaffggjjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~..--++,,hhII00:\\ :po=\\E[5i:pf=\\E[4i:k0=\\E[10~:k1=\\EOP:k2=\\EOQ:k3=\\EOR:\\ :k4=\\EOS:k5=\\E[15~:k6=\\E[17~:k7=\\E[18~:k8=\\E[19~:\\ :k9=\\E[20~:k;=\\E[21~:F1=\\E[23~:F2=\\E[24~:F3=\\E[25~:\\ :F4=\\E[26~:F5=\\E[28~:F6=\\E[29~:F7=\\E[31~:F8=\\E[32~:\\ :F9=\\E[33~:FA=\\E[34~:kb=:K1=\\EOw:K2=\\EOu:K3=\\EOy:\\ :K4=\\EOq:K5=\\EOs:kB=\\E[Z:kE=\\E[8\\^:*4=\\E[3\$:*7=\\E[8\$:\\ :#2=\\E[7\$:#3=\\E2\$:#4=\\E[d:%c=\\E[6\$:%e=\\E[5\$:%i=\\E[c:\\ :kh=\\E[1~:@1=\\E[1~:kH=\\E[4~:@7=\\E[4~:kN=\\E[6~:kP=\\E[5~:\\ :kI=\\E[2~:kD=\\E[3~:ku=\\EOA:kd=\\EOB:kr=\\EOC:kl=\\EOD:km:" Regards. [1] I don't know experience of others but keyboard totally sucks on HP Pavilion dv6000 series. While pressing Control_L continuosly (think C-f, C-b, C-p, C-n scenarios) it skips Control_L too may times. [2] Just on the right next of the space bar. In GNU Emacs 23.0.60.2 (x86_64-unknown-linux-gnu) of 2008-03-13 on alamut configured using `configure '--without-x'' Important settings: value of $LC_ALL: nil value of $LC_COLLATE: nil value of $LC_CTYPE: nil value of $LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC: nil value of $LC_TIME: nil value of $LANG: en_US.UTF-8 value of $XMODIFIERS: nil locale-coding-system: utf-8-unix default-enable-multibyte-characters: t Major mode: Group Minor modes in effect: erc-list-mode: t erc-menu-mode: t erc-autojoin-mode: t erc-ring-mode: t erc-networks-mode: t erc-pcomplete-mode: t erc-track-mode: t erc-track-minor-mode: t erc-match-mode: t erc-button-mode: t erc-fill-mode: t erc-stamp-mode: t erc-netsplit-mode: t gnus-topic-mode: t gnus-undo-mode: t erc-irccontrols-mode: t erc-noncommands-mode: t erc-move-to-prompt-mode: t erc-readonly-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t global-auto-composition-mode: t auto-composition-mode: t auto-compression-mode: t column-number-mode: t line-number-mode: t transient-mark-mode: t Recent input: RET C-x b * G r TAB RET C-u 2 g p p p C-x b * G r TAB RET C-u 2 g p p p p p p p p p SPC n n n q C-u 2 g p p SPC q SPC n n n n n n n n n n n n n n n q ESC x r e p o r t - e m a c s - b u f TAB RET DEL g RET Recent messages: Generating summary...done Retrieving newsgroup: bildirgec... Fetching headers for bildirgec...done Generating summary...done Retrieving newsgroup: slashdot... Fetching headers for slashdot...done Generating summary...done Retrieving newsgroup: reddit-science... Fetching headers for reddit-science...done Generating summary...done From svenjoac at gmx.de Fri May 2 12:45:04 2008 From: svenjoac at gmx.de (Sven Joachim) Date: Fri, 02 May 2008 21:45:04 +0200 Subject: bug#153: 23.0.60; Minibuffer for M-x dired broken In-Reply-To: (Stefan Monnier's message of "Fri, 02 May 2008 13:20:28 -0400") References: <877ieey3ym.fsf@gmx.de> <87tzhiwn9y.fsf@gmx.de> Message-ID: <87r6ckbidb.fsf@gmx.de> On 2008-05-02 19:20 +0200, Stefan Monnier wrote: >>> Start Emacs somewhere, e.g. in your home directory, and type C-x d >>> /usr. The original part of the filename is not greyed out as it's >>> supposed to be with file-name-shadow-mode enabled, and if you press RET, >>> you get an error message: >>> >>> Reading directory: no such file or directory, /home/sven/usr > > Thanks, should be fixed now, Yes, thank you (closing bug #173). BTW, I just discovered your comments on bug #153. They missed me because a) you did not CC me, and I am not subscribed to the Emacs bug tracker; b) I did not even know that I submitted a bug report (it was just a question sent to emacs-devel, and you seem to have resent it to submit at emacsbugs.donarmstrong.com). I do quite like the latest completion code, but can imagine that other people might find it a bit confusing. Also, if a directory has no non-trivial subdirectories, C-x d TAB completes to . and .., which is probably less useful than immediately listing all possible file name completions. Sven From don at donarmstrong.com Fri May 2 12:55:07 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Fri, 2 May 2008 12:55:07 -0700 Subject: bug#173: marked as done (23.0.60; Minibuffer for M-x dired broken) References: <87r6ckbidb.fsf@gmx.de> <877ieey3ym.fsf@gmx.de> Message-ID: Your message dated Fri, 02 May 2008 21:45:04 +0200 with message-id <87r6ckbidb.fsf at gmx.de> and subject line Re: 23.0.60; Minibuffer for M-x dired broken has caused the Emacs bug report #173, regarding 23.0.60; Minibuffer for M-x dired broken to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact don at donarmstrong.com immediately.) -- 173: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=173 Emacs Bug Tracking System Contact don at donarmstrong.com with problems -------------- next part -------------- An embedded message was scrubbed... From: Sven Joachim Subject: 23.0.60; Minibuffer for M-x dired broken Date: Thu, 01 May 2008 07:43:13 +0200 Size: 8496 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080502/98628aeb/attachment.eml -------------- next part -------------- An embedded message was scrubbed... From: Sven Joachim Subject: Re: 23.0.60; Minibuffer for M-x dired broken Date: Fri, 02 May 2008 21:45:04 +0200 Size: 2612 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080502/98628aeb/attachment-0001.eml From monnier at iro.umontreal.ca Fri May 2 18:25:15 2008 From: monnier at iro.umontreal.ca (Stefan Monnier) Date: Fri, 02 May 2008 21:25:15 -0400 Subject: bug#153: 23.0.60; Minibuffer for M-x dired broken In-Reply-To: <87r6ckbidb.fsf@gmx.de> (Sven Joachim's message of "Fri, 02 May 2008 21:45:04 +0200") References: <877ieey3ym.fsf@gmx.de> <87tzhiwn9y.fsf@gmx.de> <87r6ckbidb.fsf@gmx.de> Message-ID: > I do quite like the latest completion code, Glad to hear it. > but can imagine that other people might find it a bit confusing. Time will tell. > Also, if a directory has no non-trivial subdirectories, C-x d TAB > completes to . and .., which is probably less useful than immediately > listing all possible file name completions. Good point, Stefan From mah at everybody.org Sat May 3 10:41:23 2008 From: mah at everybody.org (Mark A. Hershberger) Date: Sat, 03 May 2008 13:41:23 -0400 Subject: bug#183: 23.0.60; !MEM FULL! and pixbuf errors when viewing SVG without a viewBox Message-ID: <87od7n1e0s.fsf@everybody.org> Please write in English if possible, because the Emacs maintainers usually do not have translators to read other languages for them. Your bug report will be posted to the emacs-pretest-bug at gnu.org mailing list. Please describe exactly what actions triggered the bug and the precise symptoms of the bug: I have the following super-simple SVG file: When I load this in emacs (using ?emacs -q --no-site-file?), I can hit C-c C-c and view the file without a problem. When I remove the viewBox attribute from the svg element, and hit C-c C-c, I get the following on the console: (emacs:30299): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed (emacs:30299): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (emacs:30299): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `pixbuf != NULL' failed (emacs:30299): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion `pixbuf != NULL' failed Hitting C-c C-c again to return to the xml representation of the image results in ?!MEM FULL!? showing up in the lower left-hand corner of the frame. The text does appear, though. In GNU Emacs 23.0.60.1 (i486-pc-linux-gnu, GTK+ Version 2.12.0) of 2008-03-29 on iridium, modified by Debian (emacs-snapshot package, version 1:20080329-1) Windowing system distributor `The X.Org Foundation', version 11.0.10400090 configured using `configure '--build' 'i486-linux-gnu' '--host' 'i486-linux-gnu' '--prefix=/usr' '--sharedstatedir=/var/lib' '--libexecdir=/usr/lib' '--localstatedir=/var' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--with-pop=yes' '--enable-locallisppath=/etc/emacs-snapshot:/etc/emacs:/usr/local/share/emacs/23.0.60/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/23.0.60/site-lisp:/usr/share/emacs/site-lisp:/usr/share/emacs/23.0.60/leim' '--with-x=yes' '--with-x-toolkit=gtk' '--enable-font-backend' 'build_alias=i486-linux-gnu' 'host_alias=i486-linux-gnu' 'CFLAGS=-DDEBIAN -DSITELOAD_PURESIZE_EXTRA=5000 -g -O2'' Important settings: value of $LC_ALL: nil value of $LC_COLLATE: nil value of $LC_CTYPE: nil value of $LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC: nil value of $LC_TIME: nil value of $LANG: en_US.UTF-8 value of $XMODIFIERS: nil locale-coding-system: utf-8-unix default-enable-multibyte-characters: t -- http://hexmode.com/ GPG Fingerprint: 7E15 362D A32C DFAB E4D2 B37A 735E F10A 2DFC BFF5 Ideas create idols; only wonder leads to knowing. -- St. Gregory of Nyssa From sand at blarg.net Sat May 3 10:38:19 2008 From: sand at blarg.net (sand at blarg.net) Date: 3 May 2008 17:38:19 -0000 Subject: bug#184: Resolved underline problem needs to be reflected in etc/PROBLEMS Message-ID: <20080503173819.25361.qmail@priss.frightenedpiglet.com> From drew.adams at oracle.com Sat May 3 14:19:27 2008 From: drew.adams at oracle.com (Drew Adams) Date: Sat, 3 May 2008 14:19:27 -0700 Subject: bug#185: 23.0.60; incremental search in Info is broken Message-ID: <002401c8ad63$5eb273a0$0200a8c0@us.oracle.com> emacs -Q C-h i, choose Elisp manual C-s this-command Repeat C-s. It stops at the "File:" occurrence at the beginning of each node. I've also seen it stop after a link that does not contain the sought text - for instance, searching for "minibuffer" it stops after a link with text "mode-line". In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600) of 2008-04-19 on LENNART-69DE564 Windowing system distributor `Microsoft Corp.', version 5.1.2600 configured using `configure --with-gcc (3.4) --no-opt --cflags -Ic:/g/include -fno-crossjumping' From don at donarmstrong.com Sat May 3 19:15:04 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Sat, 3 May 2008 19:15:04 -0700 Subject: bug#178: marked as done (23.0.60; C-h i puts point at end of dir menu, not start [eom]) References: <87iqxu6d4m.fsf@stupidchicken.com> <009401c8abce$a3f1e1d0$c2b22382@us.oracle.com> Message-ID: Your message dated Sat, 03 May 2008 22:01:45 -0400 with message-id <87iqxu6d4m.fsf at stupidchicken.com> and subject line Re: 23.0.60; C-h i puts point at end of dir menu, not start [eom] has caused the Emacs bug report #178, regarding 23.0.60; C-h i puts point at end of dir menu, not start [eom] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact don at donarmstrong.com immediately.) -- 178: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=178 Emacs Bug Tracking System Contact don at donarmstrong.com with problems -------------- next part -------------- An embedded message was scrubbed... From: "Drew Adams" Subject: 23.0.60; C-h i puts point at end of dir menu, not start [eom] Date: Thu, 1 May 2008 14:02:17 -0700 Size: 5565 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080503/798e2b7d/attachment.eml -------------- next part -------------- An embedded message was scrubbed... From: Chong Yidong Subject: Re: 23.0.60; C-h i puts point at end of dir menu, not start [eom] Date: Sat, 03 May 2008 22:01:45 -0400 Size: 1050 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080503/798e2b7d/attachment-0001.eml From don at donarmstrong.com Sat May 3 19:20:03 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Sat, 3 May 2008 19:20:03 -0700 Subject: bug#171: marked as done (patch for dired-format-columns-of-files) References: <8763tu6ctr.fsf@stupidchicken.com> Message-ID: Your message dated Sat, 03 May 2008 22:08:16 -0400 with message-id <8763tu6ctr.fsf at stupidchicken.com> and subject line Re: patch for dired-format-columns-of-files has caused the Emacs bug report #171, regarding patch for dired-format-columns-of-files to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact don at donarmstrong.com immediately.) -- 171: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=171 Emacs Bug Tracking System Contact don at donarmstrong.com with problems -------------- next part -------------- An embedded message was scrubbed... From: "Toru TSUNEYOSHI" Subject: patch for dired-format-columns-of-files Date: Thu, 1 May 2008 02:50:53 +0900 Size: 5110 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080503/70feb4b1/attachment.eml -------------- next part -------------- An embedded message was scrubbed... From: Chong Yidong Subject: Re: patch for dired-format-columns-of-files Date: Sat, 03 May 2008 22:08:16 -0400 Size: 1181 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080503/70feb4b1/attachment-0001.eml From don at donarmstrong.com Sat May 3 19:35:03 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Sat, 3 May 2008 19:35:03 -0700 Subject: bug#177: marked as done (23.0.60; doc for read-from-minibuffer) References: <87lk2q4xor.fsf@stupidchicken.com> <008f01c8abcd$14683c40$c2b22382@us.oracle.com> Message-ID: Your message dated Sat, 03 May 2008 22:20:36 -0400 with message-id <87lk2q4xor.fsf at stupidchicken.com> and subject line Re: 23.0.60; doc for read-from-minibuffer has caused the Emacs bug report #177, regarding 23.0.60; doc for read-from-minibuffer to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact don at donarmstrong.com immediately.) -- 177: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=177 Emacs Bug Tracking System Contact don at donarmstrong.com with problems -------------- next part -------------- An embedded message was scrubbed... From: "Drew Adams" Subject: 23.0.60; doc for read-from-minibuffer Date: Thu, 1 May 2008 13:51:07 -0700 Size: 5946 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080503/e91c4bd4/attachment-0002.eml -------------- next part -------------- An embedded message was scrubbed... From: Chong Yidong Subject: Re: 23.0.60; doc for read-from-minibuffer Date: Sat, 03 May 2008 22:20:36 -0400 Size: 1342 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080503/e91c4bd4/attachment-0003.eml From eric at siege-engine.com Sat May 3 18:45:06 2008 From: eric at siege-engine.com (Eric M. Ludlam) Date: Sat, 3 May 2008 21:45:06 -0400 Subject: bug#186: 23.0.50; can't debug `message' Message-ID: <200805040145.m441j6cm016447@projectile.siege-engine.com> I was trying to figure out where a stray output message was coming from, so I tried: M-x debug-on-entry RET message RET but sadly, this put Emacs into a state where I couldn't do anything, and I had to kill it because it kept exceeding it's stack depth. In GNU Emacs 23.0.50.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2007-09-10 on projectile Windowing system distributor `The XFree86 Project, Inc', version 11.0.40300000 Important settings: value of $LC_ALL: nil value of $LC_COLLATE: nil value of $LC_CTYPE: nil value of $LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC: nil value of $LC_TIME: nil value of $LANG: en_US.UTF-8 locale-coding-system: utf-8 default-enable-multibyte-characters: t Major mode: Fundamental Minor modes in effect: show-paren-mode: t tooltip-mode: t mouse-wheel-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t unify-8859-on-encoding-mode: t utf-translate-cjk-mode: t auto-compression-mode: t line-number-mode: t Recent input: M-x r e p o r Recent messages: Making completion list... Invalid face reference: quote [10 times] Making completion list... Invalid face reference: quote [10 times] Making completion list... Invalid face reference: quote [10 times] Loading emacsbug... Loading regexp-opt...done Loading emacsbug...done Invalid face reference: quote [10 times] From ofv at wanadoo.es Sat May 3 17:03:50 2008 From: ofv at wanadoo.es (=?UTF-8?Q?=C3=93scar?= Fuentes) Date: Sun, 04 May 2008 02:03:50 +0200 Subject: bug#187: 23.0.60; Font properties does not apply to international characters. Message-ID: <1w4j540p.fsf@telefonica.net> A non-text attachment was scrubbed... Name: fontbug2.png Type: image/png Size: 1184 bytes Desc: not available Url : http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080504/a8c3de91/attachment.png -------------- next part -------------- A non-text attachment was scrubbed... Name: fontbug.png Type: image/png Size: 177 bytes Desc: not available Url : http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080504/a8c3de91/attachment-0001.png -------------- next part -------------- In GNU Emacs 23.0.60.1 (i386-mingw-nt5.0.2195) of 2008-05-04 on K7 Windowing system distributor `Microsoft Corp.', version 5.0.2195 configured using `configure --with-gcc (4.2) --cflags -It:/emacscvs/include --ldflags -Lt:/emacscvs/lib' Important settings: value of $LC_ALL: nil value of $LC_COLLATE: nil value of $LC_CTYPE: nil value of $LC_MESSAGES: en value of $LC_MONETARY: nil value of $LC_NUMERIC: nil value of $LC_TIME: nil value of $LANG: ESN value of $XMODIFIERS: nil locale-coding-system: cp1252 default-enable-multibyte-characters: t Major mode: Lisp Interaction Minor modes in effect: show-paren-mode: t iswitchb-mode: t tooltip-mode: t mouse-wheel-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t blink-cursor-mode: t global-auto-composition-mode: t auto-composition-mode: t auto-encryption-mode: t auto-compression-mode: t column-number-mode: t line-number-mode: t transient-mark-mode: t Recent input: C-x b s s c r r s c r ? ? n ? C-d i i SPC e x i t d e x i t A c c e n t e d SPC c h a r a c t e d r r s C-g ? M-x Recent messages: Loading em-dirs...done Loading em-glob...done Loading em-hist...done Loading em-ls...done Loading em-prompt...done Loading em-script...done Loading em-term...done Loading em-unix...done Quit goto-history-element: Beginning of history; no preceding item Quit -- Oscar From bzg at altern.org Sun May 4 06:04:11 2008 From: bzg at altern.org (Bastien Guerry) Date: Sun, 04 May 2008 15:04:11 +0200 Subject: bug#188: 23.0.60; Custom-save deleting custom file Message-ID: <877ieap6es.fsf@bzg.ath.cx> Please write in English if possible, because the Emacs maintainers usually do not have translators to read other languages for them. Your bug report will be posted to the emacs-pretest-bug at gnu.org mailing list. Please describe exactly what actions triggered the bug and the precise symptoms of the bug: Saving a change with Custom-save deletes the old custom file (in my case ~/.emacs-custom.el). This is quite annoying if you don't have backups. In GNU Emacs 23.0.60.1 (i686-pc-linux-gnu, GTK+ Version 2.12.9) of 2008-05-04 on bzg.ath.cx Windowing system distributor `The X.Org Foundation', version 11.0.10400090 configured using `configure '--enable-font-backend' '--with-x-toolkit=gtk'' Important settings: value of $LC_ALL: nil value of $LC_COLLATE: nil value of $LC_CTYPE: nil value of $LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC: nil value of $LC_TIME: nil value of $LANG: fr_FR.UTF-8 value of $XMODIFIERS: nil locale-coding-system: utf-8-unix default-enable-multibyte-characters: t Major mode: Group Minor modes in effect: gnus-undo-mode: t display-time-mode: t delete-selection-mode: t pc-selection-mode: t shell-dirtrack-mode: t show-paren-mode: t mouse-wheel-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t global-auto-composition-mode: t auto-composition-mode: t auto-encryption-mode: t auto-compression-mode: t line-number-mode: t Recent input: C-e C-a C-e C-a C-e C-a C-e C-a C-e C-z c C-n C-n C-n C-n C-n C-n C-n C-n j e m a . C-u 1 0 0 0 / s c u s t o m M-x r e p o r b u g C u s t M-x c u s C-x C-x o C-x o C-x o C-g C-g q g M-x c u s a - t C-g M-x c u s - f a C-h k C-x C-s C-x 1 C-x k g M-x r e p o r b u C u s t o m - s a v e SPC d e l e t e o o d e l e t i n g SPC o l d SPC d e e l l e t i n g SPC o l d . SPC ~ / C-z c SPC c i u s t o m SPC C-x o C-z c C-x C-f C-x o C-x o s m d l f k s d m f l k s d m f l k s d f C-x o C-x o f i l e C-a C-e C-e C-a C-e C-a C-e C-a C-e C-e C-a C-e C-x o C-e C-x o C-g C-g g M-x Recent messages: nnml: Reading incoming mail (no new mail)...done nndiary: Reading incoming mail from file... nndiary: Reading incoming mail (no new mail)...done Killed inactive buffer: *Help*. Entering debugger... [3 times] Quit [2 times] nnml: Reading incoming mail from file... nnml: Reading incoming mail (no new mail)...done nndiary: Reading incoming mail from file... nndiary: Reading incoming mail (no new mail)...done -- Bastien From dann at ics.uci.edu Sun May 4 10:35:36 2008 From: dann at ics.uci.edu (Dan Nicolaescu) Date: Sun, 04 May 2008 10:35:36 -0700 Subject: bug#189: please make byte compiling during bootstrap take advantage of make -j Message-ID: <200805041735.m44HZbxS018196@sallyv1.ics.uci.edu> Multi-core CPUs are already widespread, and will only become more so. Byte compiling all the elisp files is where most of the time is spent during bootstrap. But currently byte compilation does not take advantage of "make -j", which would speed it up a great deal. Can you please implement this? Thanks From cyd at stupidchicken.com Sun May 4 11:45:52 2008 From: cyd at stupidchicken.com (Chong Yidong) Date: Sun, 04 May 2008 14:45:52 -0400 Subject: bug#168: Emacs-22.1 compilation-error-regexp Message-ID: <87iqxtkivz.fsf@stupidchicken.com> > The compilation-error-regexp works for gcc output but not for > Openwatcom. However, it worked fine for emacs-21. It seems the regexp no > longer accepts parentheses around the line number. > > ----- gcc example is ok ---- > -*- mode: compilation; default-directory: "c:/altm/acp-7-3/build/" -*- > ../src/vi/vi_main.c:53: `xint' undeclared (first use in this function) > ../src/vi/vi_main.c:53: (Each undeclared identifier is reported only once > > ------- Open Watcom Make Version 1.7 -- not ok because of line number ====== > ..\src\ctrl\lister.c(109): Error! E1009: Expecting ';' but found '{' > ..\src\ctrl\lister.c(120): Warning! W201: Unreachable code I don't have Openwatcom installed, so I can't test the fix directly. Could you help me with testing? Please add the following code to your .emacs, then try compiling. Does compilation now work for both gcc and openwatcom? If possible, please test with any other back-end to M-x compile that you have available, to ensure that nothing else broke. Thanks. (require 'compile) (push '(openwatcom "^\\([0-9]*[^0-9\n]\\(?:[^\n ]\\| [^-/\n]\\)*?\\)(\\([0-9]+\\)): ?\ \\(?:\\(Warning! ?W[0-9]+:\\)\\|\\(Error! ?E[0-9]+:\\)\\|\\(.\\)\\)" 1 2 nil (3 . 5)) compilation-error-regexp-alist-alist) (push 'openwatcom compilation-error-regexp-alist) From david.reitter at gmail.com Sun May 4 11:53:12 2008 From: david.reitter at gmail.com (David Reitter) Date: Sun, 4 May 2008 19:53:12 +0100 Subject: bug#166: not a corner case! Message-ID: <53E3A96E-258D-418D-A7BB-9EB081587AC5@gmail.com> this bug is not a corner case. my distribution hides the first frame until everything has been initialized (i.e. the user's .emacs has been read, etc.), in order to avoid ugly jumping frames. any chance somebody who knows what they're doing can fix it? or perhaps point out some possible causes for this...? From don at donarmstrong.com Sun May 4 15:00:04 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Sun, 4 May 2008 15:00:04 -0700 Subject: Processed: close 184 In-Reply-To: <87zlr53fk8.fsf@stupidchicken.com> References: <87zlr53fk8.fsf@stupidchicken.com> Message-ID: Processing commands for control at emacsbugs.donarmstrong.com: > close 184 bug#184: Resolved underline problem needs to be reflected in etc/PROBLEMS 'close' is deprecated; see http://emacsbugs.donarmstrong.com/Developer.html#closing. bug closed, send any further explanations to sand at blarg.net > thanks Stopping processing here. Please contact me if you need assistance. Don Armstrong (administrator, Emacs bugs database) From don at donarmstrong.com Sun May 4 15:30:03 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Sun, 4 May 2008 15:30:03 -0700 Subject: bug#164: marked as done (23.0.60; Broken eshell completion of directory names) References: <87y76p7luo.fsf@stupidchicken.com> <87fxt5z5fp.fsf@localhorst.mine.nu> Message-ID: Your message dated Sun, 04 May 2008 18:20:15 -0400 with message-id <87y76p7luo.fsf at stupidchicken.com> and subject line Re: 23.0.60; Broken eshell completion of directory names has caused the Emacs bug report #164, regarding 23.0.60; Broken eshell completion of directory names to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact don at donarmstrong.com immediately.) -- 164: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=164 Emacs Bug Tracking System Contact don at donarmstrong.com with problems -------------- next part -------------- An embedded message was scrubbed... From: David Hansen Subject: 23.0.60; Broken eshell completion of directory names Date: Tue, 29 Apr 2008 05:49:14 +0200 Size: 9294 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080504/b30780a9/attachment.eml -------------- next part -------------- An embedded message was scrubbed... From: Chong Yidong Subject: Re: 23.0.60; Broken eshell completion of directory names Date: Sun, 04 May 2008 18:20:15 -0400 Size: 1229 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080504/b30780a9/attachment-0001.eml From md5i at cs.cmu.edu Sun May 4 16:55:47 2008 From: md5i at cs.cmu.edu (Michael Welsh Duggan) Date: Sun, 04 May 2008 19:55:47 -0400 Subject: bug#190: 23.0.60; vc inflooping Message-ID: <877ie9lj3w.fsf@maru.md5i.com> Please describe exactly what actions triggered the bug and the precise symptoms of the bug: emacs -Q C-x C-f /tmp/foo RET This is a test file C-x C-s C-x v i yes RET C-x v v Symptoms: find-auto-coding: Variable binding depth exceeds max-specpdl-size max-specpdl-size is a variable defined in `C source code'. Its value is 1040 M-: (setq max-specpdl-size 2000) C-x v v [in buffer foo] Same error M-: (setq max-specpdl-size 10000) C-x v v [in buffer foo] find-auto-coding: Lisp nesting exceeds `max-lisp-eval-depth' max-lisp-eval-depth is a variable defined in `C source code'. Its value is 400 M-: (setq max-lisp-eval-depth 10000) Emacs takes a long, long time. C-g M-x toggle-debug-on-quit C-x v v [wait a couple seconds] C-g Bottom of *Bactrace* buffer: vc-rcs-checkout-model(("/tmp/foo")) vc-rcs-fetch-master-state("/tmp/foo") vc-rcs-checkout-model(("/tmp/foo")) vc-rcs-fetch-master-state("/tmp/foo") vc-rcs-checkout-model(("/tmp/foo")) vc-rcs-fetch-master-state("/tmp/foo") vc-rcs-checkout-model(("/tmp/foo")) apply(vc-rcs-checkout-model ("/tmp/foo")) vc-call-backend(RCS checkout-model ("/tmp/foo")) vc-checkout-model(RCS ("/tmp/foo")) vc-next-action(nil) call-interactively(vc-next-action nil nil) So, there's an infloop happening. In GNU Emacs 23.0.60.6 (i686-pc-linux-gnu, GTK+ Version 2.12.9) of 2008-05-04 on maru Windowing system distributor `The X.Org Foundation', version 11.0.10400090 configured using `configure '--without-toolkit-scroll-bars' '--with-dbus' '--enable-font-backend'' Important settings: value of $LC_ALL: nil value of $LC_COLLATE: nil value of $LC_CTYPE: nil value of $LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC: nil value of $LC_TIME: nil value of $LANG: en_US.utf8 value of $XMODIFIERS: nil locale-coding-system: utf-8-unix default-enable-multibyte-characters: t Major mode: Emacs-Lisp Minor modes in effect: display-time-mode: t shell-dirtrack-mode: t senator-minor-mode: t semantic-idle-summary-mode: t semantic-idle-scheduler-mode: t tooltip-mode: t mouse-wheel-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t global-auto-composition-mode: t auto-composition-mode: t auto-encryption-mode: t auto-compression-mode: t line-number-mode: t Recent input: C-p C-p C-p C-p C-p > C-p C-p C-p C-p C-p C-p C-f C-f M-x d e b u g - o n q M-x C-g C-g C-x C-g q M-x t o g g l e - d e q C-x v v d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d c c c c c d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d c c c c c d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d c c d d d d d d d d d d d d d d d d d d q M-x C-g C-g M-x r e p o r t - e m Recent messages: Entering debugger... Proceeding, will debug on next eval or call. Entering debugger... Proceeding, will debug on next eval or call. Entering debugger... Proceeding, will debug on next eval or call. Entering debugger... Proceeding, will debug on next eval or call. Entering debugger... Back to top level. Don't touch it! It's the History Eraser Button, you fool! [2 times] -- Michael Welsh Duggan (md5i at cs.cmu.edu) From monnier at iro.umontreal.ca Sun May 4 23:41:22 2008 From: monnier at iro.umontreal.ca (Stefan Monnier) Date: Mon, 05 May 2008 02:41:22 -0400 Subject: bug#186: can't debug `message' Message-ID: tag 186 +wontfix Yes, there are many ways to shoot yourself in the foot in Emacs. Not sure what we can do about it, Stefan From don at donarmstrong.com Sun May 4 23:45:04 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Sun, 4 May 2008 23:45:04 -0700 Subject: bug#190: marked as done (23.0.60; vc inflooping) References: <877ie9lj3w.fsf@maru.md5i.com> Message-ID: Your message dated Mon, 05 May 2008 02:38:22 -0400 with message-id and subject line vc inflooping has caused the Emacs bug report #190, regarding 23.0.60; vc inflooping to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact don at donarmstrong.com immediately.) -- 190: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=190 Emacs Bug Tracking System Contact don at donarmstrong.com with problems -------------- next part -------------- An embedded message was scrubbed... From: Michael Welsh Duggan Subject: 23.0.60; vc inflooping Date: Sun, 04 May 2008 19:55:47 -0400 Size: 7885 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080504/86fb37e6/attachment.eml -------------- next part -------------- An embedded message was scrubbed... From: Stefan Monnier Subject: vc inflooping Date: Mon, 05 May 2008 02:38:22 -0400 Size: 1535 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080504/86fb37e6/attachment-0001.eml From don at donarmstrong.com Mon May 5 00:10:08 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Mon, 5 May 2008 00:10:08 -0700 Subject: bug#170: marked as done (23.0.60; `crm-select-current-element' is not defined in crm.el) References: <878wyv9s6h.fsf@patagonia.sebmags.homelinux.org> Message-ID: Your message dated Mon, 05 May 2008 03:05:18 -0400 with message-id and subject line `crm-select-current-element' is not defined in crm.el has caused the Emacs bug report #170, regarding 23.0.60; `crm-select-current-element' is not defined in crm.el to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact don at donarmstrong.com immediately.) -- 170: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=170 Emacs Bug Tracking System Contact don at donarmstrong.com with problems -------------- next part -------------- An embedded message was scrubbed... From: Sebastian Luque Subject: 23.0.60; `crm-select-current-element' is not defined in crm.el Date: Wed, 30 Apr 2008 12:19:18 -0500 Size: 9120 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080505/ddeda917/attachment-0002.eml -------------- next part -------------- An embedded message was scrubbed... From: Stefan Monnier Subject: `crm-select-current-element' is not defined in crm.el Date: Mon, 05 May 2008 03:05:18 -0400 Size: 1575 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080505/ddeda917/attachment-0003.eml From monnier at iro.umontreal.ca Mon May 5 00:00:00 2008 From: monnier at iro.umontreal.ca (Stefan Monnier) Date: Mon, 05 May 2008 03:00:00 -0400 Subject: bug#179: Menu separators are not displayed Message-ID: Does the patch below fix it? Stefan --- subr.el.~1.594.~ 2008-05-02 12:47:05.000000000 -0400 +++ subr.el 2008-05-05 02:58:00.000000000 -0400 @@ -571,10 +571,14 @@ (let* ((key (car binding)) (item (cdr binding)) (oldbind (assq key bindings))) + (if (null key) + ;; nil keys are/were used by easy-menu for "separator lines and + ;; separator titles". Merging them makes no sense. + (push binding bindings) ;; Newer bindings override older. (if oldbind (setq bindings (delq oldbind bindings))) (when item ;nil bindings just hide older ones. - (push binding bindings)))) + (push binding bindings))))) (nconc map bindings))) (put 'keyboard-translate-table 'char-table-extra-slots 0) From monnier at iro.umontreal.ca Sun May 4 23:48:02 2008 From: monnier at iro.umontreal.ca (Stefan Monnier) Date: Mon, 05 May 2008 02:48:02 -0400 Subject: bug#181: Case insensitive file name completion Message-ID: severity 181 wishlist thanks IIUC you'd like completion to be both case-sensitive (if that matches something) and case-insensitive (if there's no case-sensitive match). Stefan From don at donarmstrong.com Mon May 5 00:20:03 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Mon, 5 May 2008 00:20:03 -0700 Subject: bug#78: marked as done (23.0.60; python-mode indents try...except...finally incorrectly) References: <60c603510803231433r1f694dd7w8731b841ab6e9c4a@mail.gmail.com> Message-ID: Your message dated Mon, 05 May 2008 03:11:03 -0400 with message-id and subject line python-mode indents try...except...finally incorrectly has caused the Emacs bug report #78, regarding 23.0.60; python-mode indents try...except...finally incorrectly to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact don at donarmstrong.com immediately.) -- 78: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=78 Emacs Bug Tracking System Contact don at donarmstrong.com with problems -------------- next part -------------- An embedded message was scrubbed... From: "Phil Sung" Subject: 23.0.60; python-mode indents try...except...finally incorrectly Date: Sun, 23 Mar 2008 17:33:25 -0400 Size: 8237 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080505/0cd6259b/attachment.eml -------------- next part -------------- An embedded message was scrubbed... From: Stefan Monnier Subject: python-mode indents try...except...finally incorrectly Date: Mon, 05 May 2008 03:11:03 -0400 Size: 1593 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080505/0cd6259b/attachment-0001.eml From tim.vanholder at gmail.com Mon May 5 04:13:20 2008 From: tim.vanholder at gmail.com (Tim Van Holder) Date: Mon, 05 May 2008 13:13:20 +0200 Subject: bug#191: 23.0.60; vc (CVS backend): vc-directory is broken Message-ID: <87wsm9rokv.fsf@leeloo.anubex.internal> In a CVS HEAD build, C-x v d yields error in process sentinel: Wrong type argument: listp, ".gdbinit" A backtrace shows (with some dir & file names changed, so buffer positions might show discrepancies): Debugger entered--Lisp error: (wrong-type-argument listp ".gdbinit") vc-default-status-printer(CVS ".gdbinit") apply(vc-default-status-printer CVS ".gdbinit") vc-call-backend(CVS status-printer ".gdbinit") vc-generic-status-printer((".gdbinit" edited nil nil nil nil)) #[(G52601 data) "" [G52601 data "\n"] 2](--ewoc--user-pp-- (".gdbinit" edited nil nil nil nil)) apply(#[(G52601 data) "" [G52601 data "\n"] 2] --ewoc--user-pp-- (".gdbinit" edited nil nil nil nil)) (lambda (&rest --cl-rest--) (apply #[... "" [G52601 data "\n"] 2] (quote --ewoc--user-pp--) --cl-rest--))((".gdbinit" edited nil nil nil nil)) ewoc--refresh-node((lambda (&rest --cl-rest--) (apply #[... "" [G52601 data "\n"] 2] (quote --ewoc--user-pp--) --cl-rest--)) [[[[#0 #2 "" #] #1 DL-LIST #] #0 #("VC backend : CVS\nWorking dir: /blah\nModule : ADD CODE TO PRINT THE MODULE\nRepository : ADD CODE TO PRINT THE REPOSITORY\nBranch : ADD CODE TO PRINT THE BRANCH NAME\n\n" 0 13 ... 13 17 ... 17 30 ... 30 48 ... 48 61 ... 61 90 ... 90 103 ... 103 136 ... 136 149 ... 149 183 ...) #] [#0 [#1 [#2 #0 #("VC backend : CVS\nWorking dir: /blah\nModule : ADD CODE TO PRINT THE MODULE\nRepository : ADD CODE TO PRINT THE REPOSITORY\nBranch : ADD CODE TO PRINT THE BRANCH NAME\n\n" 0 13 ... 13 17 ... 17 30 ... 30 48 ... 48 61 ... 61 90 ... 90 103 ... 103 136 ... 136 149 ... 149 183 ...) #] DL-LIST #] "" #] (".gdbinit" edited nil nil nil nil) #] [[[[#0 #2 #("VC backend : CVS\nWorking dir: /blah\nModule : ADD CODE TO PRINT THE MODULE\nRepository : ADD CODE TO PRINT THE REPOSITORY\nBranch : ADD CODE TO PRINT THE BRANCH NAME\n\n" 0 13 ... 13 17 ... 17 30 ... 30 48 ... 48 61 ... 61 90 ... 90 103 ... 103 136 ... 136 149 ... 149 183 ...) #] #1 ... #] #0 "" #] [#0 [#1 [#2 #0 "" #] ... #] #("VC backend : CVS\nWorking dir: /blah\nModule : ADD CODE TO PRINT THE MODULE\nRepository : ADD CODE TO PRINT THE REPOSITORY\nBranch : ADD CODE TO PRINT THE BRANCH NAME\n\n" 0 13 ... 13 17 ... 17 30 ... 30 48 ... 48 61 ... 61 90 ... 90 103 ... 103 136 ... 136 149 ... 149 183 ...) #] DL-LIST #]) ewoc-invalidate([cl-struct-ewoc # (lambda (&rest --cl-rest--) (apply #[... "" [G52601 data "\n"] 2] ... --cl-rest--)) [[[[#1 #3 ... #] #2 "" #] #1 DL-LIST #] [#1 [#2 [#3 #1 DL-LIST #] "" #] ... #] #("VC backend : CVS\nWorking dir: /blah\nModule : ADD CODE TO PRINT THE MODULE\nRepository : ADD CODE TO PRINT THE REPOSITORY\nBranch : ADD CODE TO PRINT THE BRANCH NAME\n\n" 0 13 ... 13 17 ... 17 30 ... 30 48 ... 48 61 ... 61 90 ... 90 103 ... 103 136 ... 136 149 ... 149 183 ...) #] [[[[#1 #3 DL-LIST #] #2 #("VC backend : CVS\nWorking dir: /blah\nModule : ADD CODE TO PRINT THE MODULE\nRepository : ADD CODE TO PRINT THE REPOSITORY\nBranch : ADD CODE TO PRINT THE BRANCH NAME\n\n" 0 13 ... 13 17 ... 17 30 ... 30 48 ... 48 61 ... 61 90 ... 90 103 ... 103 136 ... 136 149 ... 149 183 ...) #] #1 ... #] [#1 [#2 [#3 #1 ... #] #("VC backend : CVS\nWorking dir: /blah\nModule : ADD CODE TO PRINT THE MODULE\nRepository : ADD CODE TO PRINT THE REPOSITORY\nBranch : ADD CODE TO PRINT THE BRANCH NAME\n\n" 0 13 ... 13 17 ... 17 30 ... 30 48 ... 48 61 ... 61 90 ... 90 103 ... 103 136 ... 136 149 ... 149 183 ...) #] DL-LIST #] "" #] [[[[#1 #3 #("VC backend : CVS\nWorking dir: /blah\nModule : ADD CODE TO PRINT THE MODULE\nRepository : ADD CODE TO PRINT THE REPOSITORY\nBranch : ADD CODE TO PRINT THE BRANCH NAME\n\n" 0 13 ... 13 17 ... 17 30 ... 30 48 ... 48 61 ... 61 90 ... 90 103 ... 103 136 ... 136 149 ... 149 183 ...) #] #2 ... #] #1 "" #] [#1 [#2 [#3 #1 "" #] ... #] #("VC backend : CVS\nWorking dir: /blah\nModule : ADD CODE TO PRINT THE MODULE\nRepository : ADD CODE TO PRINT THE REPOSITORY\nBranch : ADD CODE TO PRINT THE BRANCH NAME\n\n" 0 13 ... 13 17 ... 17 30 ... 30 48 ... 48 61 ... 61 90 ... 90 103 ... 103 136 ... 136 149 ... 149 183 ...) #] DL-LIST #] nil (lambda (&rest --cl-rest--) (apply #[... "" [G52601 data "\n"] 2] ... --cl-rest--))] [[[[#0 #2 "" #] #1 DL-LIST #] #0 #("VC backend : CVS\nWorking dir: /blah\nModule : ADD CODE TO PRINT THE MODULE\nRepository : ADD CODE TO PRINT THE REPOSITORY\nBranch : ADD CODE TO PRINT THE BRANCH NAME\n\n" 0 13 ... 13 17 ... 17 30 ... 30 48 ... 48 61 ... 61 90 ... 90 103 ... 103 136 ... 136 149 ... 149 183 ...) #] [#0 [#1 [#2 #0 #("VC backend : CVS\nWorking dir: /blah\nModule : ADD CODE TO PRINT THE MODULE\nRepository : ADD CODE TO PRINT THE REPOSITORY\nBranch : ADD CODE TO PRINT THE BRANCH NAME\n\n" 0 13 ... 13 17 ... 17 30 ... 30 48 ... 48 61 ... 61 90 ... 90 103 ... 103 136 ... 136 149 ... 149 183 ...) #] DL-LIST #] "" #] (".gdbinit" edited nil nil nil nil) #]) vc-dir-update(((".gdbinit" edited) ("foo1" unregistered) ("foo2" unregistered) ("foo3" unregistered) ("foo4" unregistered)) #) #[(G52602 entries &optional more-to-come) "" [G52602 entries more-to-come vc-ewoc remaining mode-line-process vc-dir-update ewoc-collect vc-dir-fileinfo->needs-update vc-dir-refresh-files mapcar vc-dir-fileinfo->name up-to-date nil] 5](--buffer-- ((".gdbinit" edited) ("foo1" unregistered) ("foo2" unregistered) ("foo3" unregistered) ("foo4" unregistered))) apply(#[(G52602 entries &optional more-to-come) "" [G52602 entries more-to-come vc-ewoc remaining mode-line-process vc-dir-update ewoc-collect vc-dir-fileinfo->needs-update vc-dir-refresh-files mapcar vc-dir-fileinfo->name up-to-date nil] 5] --buffer-- ((".gdbinit" edited) ("foo1" unregistered) ("foo2" unregistered) ("foo3" unregistered) ("foo4" unregistered))) (lambda (&rest --cl-rest--) (apply #[... "" [G52602 entries more-to-come vc-ewoc remaining mode-line-process vc-dir-update ewoc-collect vc-dir-fileinfo->needs-update vc-dir-refresh-files mapcar vc-dir-fileinfo->name up-to-date nil] 5] (quote --buffer--) --cl-rest--))(((".gdbinit" edited) ("foo1" unregistered) ("foo2" unregistered) ("foo3" unregistered) ("foo4" unregistered))) vc-cvs-after-dir-status((lambda (&rest --cl-rest--) (apply #[... "" [G52602 entries more-to-come vc-ewoc remaining mode-line-process vc-dir-update ewoc-collect vc-dir-fileinfo->needs-update vc-dir-refresh-files mapcar vc-dir-fileinfo->name up-to-date nil] 5] (quote --buffer--) --cl-rest--))) eval((vc-cvs-after-dir-status (quote (lambda ... ...)))) vc-exec-after((vc-cvs-after-dir-status (quote (lambda ... ...)))) vc-process-sentinel(# "finished\n") From don at donarmstrong.com Mon May 5 12:25:04 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Mon, 5 May 2008 12:25:04 -0700 Subject: bug#185: marked as done (23.0.60; incremental search in Info is broken) References: <87od7kd0sk.fsf@stupidchicken.com> <002401c8ad63$5eb273a0$0200a8c0@us.oracle.com> Message-ID: Your message dated Mon, 05 May 2008 15:10:51 -0400 with message-id <87od7kd0sk.fsf at stupidchicken.com> and subject line Re: 23.0.60; incremental search in Info is broken has caused the Emacs bug report #185, regarding 23.0.60; incremental search in Info is broken to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact don at donarmstrong.com immediately.) -- 185: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=185 Emacs Bug Tracking System Contact don at donarmstrong.com with problems -------------- next part -------------- An embedded message was scrubbed... From: "Drew Adams" Subject: 23.0.60; incremental search in Info is broken Date: Sat, 3 May 2008 14:19:27 -0700 Size: 5765 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080505/98f5481c/attachment.eml -------------- next part -------------- An embedded message was scrubbed... From: Chong Yidong Subject: Re: 23.0.60; incremental search in Info is broken Date: Mon, 05 May 2008 15:10:51 -0400 Size: 1263 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080505/98f5481c/attachment-0001.eml From david.reitter at gmail.com Mon May 5 16:34:30 2008 From: david.reitter at gmail.com (David Reitter) Date: Tue, 6 May 2008 00:34:30 +0100 Subject: bug#166: workaround Message-ID: a workaround is (let ((f (make-frame '((visibility . nil) (left . 1))))) (modify-frame-parameters f '((top . 30) (left . 10) (width . 100))) (make-frame-visible f)) adding just (left . 1) to the frame parameters at creation time seems to get rid of the problem. From cyd at stupidchicken.com Mon May 5 19:58:49 2008 From: cyd at stupidchicken.com (Chong Yidong) Date: Mon, 05 May 2008 22:58:49 -0400 Subject: bug#96: lgrep/rgrep not asking to save buffers Message-ID: <87ve1si1ee.fsf@stupidchicken.com> > I notice that lgrep and rgrep do not offer to save buffers. > This is different from other search and compilation commands. > This means that sometimes the results are incorrect. > > Ideally these would only offer to save files that might actually be > matched by the command -- i.e., filtering buffers based on file > extension and directory. I don't quite understand. Could you be more specific about what behavior you are looking for? From bobmc_net at rogers.com Mon May 5 20:05:45 2008 From: bobmc_net at rogers.com (Bob McIsaac) Date: Mon, 05 May 2008 23:05:45 -0400 Subject: bug#168: Emacs-22.1 compilation-error-regexp In-Reply-To: <87iqxtkivz.fsf@stupidchicken.com> References: <87iqxtkivz.fsf@stupidchicken.com> Message-ID: <481FCB09.2070205@rogers.com> An HTML attachment was scrubbed... URL: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080505/b92d5e1a/attachment.htm From cyd at stupidchicken.com Mon May 5 20:05:10 2008 From: cyd at stupidchicken.com (Chong Yidong) Date: Mon, 05 May 2008 23:05:10 -0400 Subject: bug#101: bad C-j behavior in Emacs-Lisp mode Message-ID: <87ve1sb09l.fsf@stupidchicken.com> Tags: wontfix > In Emacs-Lisp mode, put cursor after (bar m) and hit C-j. > > (if (string= foo "a") > (bar m) ; Comment > > The cursor is put after the semicolon. It should be put before it, > ready for you to type the second "then" clause of the `if'. The behavior is correct, since C-j performs a newline followed by an indent. In Emacs Lisp mode, single-semicolon comments are indented to comment-column, which as a default value of 40. From don at donarmstrong.com Mon May 5 20:20:03 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Mon, 5 May 2008 20:20:03 -0700 Subject: Processed: Tagging wontfix In-Reply-To: <87k5i8p1tu.fsf@stupidchicken.com> References: <87k5i8p1tu.fsf@stupidchicken.com> Message-ID: Processing commands for control at emacsbugs.donarmstrong.com: > tags 186 + wontfix bug#186: 23.0.50; can't debug `message' There were no tags set. Tags added: wontfix > thanks Stopping processing here. Please contact me if you need assistance. Don Armstrong (administrator, Emacs bugs database) From cyd at stupidchicken.com Mon May 5 20:30:30 2008 From: cyd at stupidchicken.com (Chong Yidong) Date: Mon, 05 May 2008 23:30:30 -0400 Subject: bug#188: 23.0.60; Custom-save deleting custom file Message-ID: <87lk2oaz3d.fsf@stupidchicken.com> > Saving a change with Custom-save deletes the old custom file (in my > case ~/.emacs-custom.el). This is quite annoying if you don't have > backups. Could you be more specific? Please supply an exact recipe for reproducing this bug. Thanks. From don at donarmstrong.com Mon May 5 20:40:06 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Mon, 5 May 2008 20:40:06 -0700 Subject: Processed: Fixing In-Reply-To: <87od7kaz6e.fsf@stupidchicken.com> References: <87od7kaz6e.fsf@stupidchicken.com> Message-ID: Processing commands for control at emacsbugs.donarmstrong.com: > close 168 bug#168: Emacs-22.1 compilation-error-regexp 'close' is deprecated; see http://emacsbugs.donarmstrong.com/Developer.html#closing. bug closed, send any further explanations to bobmc at bobmc.net > thanks Stopping processing here. Please contact me if you need assistance. Don Armstrong (administrator, Emacs bugs database) From bruno at clisp.org Mon May 5 18:30:45 2008 From: bruno at clisp.org (Bruno Haible) Date: Tue, 6 May 2008 03:30:45 +0200 Subject: bug#192: regexp does not work as documented Message-ID: <200805060330.45156.bruno@clisp.org> The regular expression (as an Emacs string) "^msgstr\\(\\[[0-9]\\]\\)?.*\n\\(\".*\n\\)*" is supposed to search for a line starting with "msgstr" and an optional digit inside brackets, followed by as many lines starting with a double-quote as possible. The Emacs documentation says: "The matcher processes a `*' construct by matching, immediately, as many repetitions as can be found." This is apparently not the case with the above regexp. ---------------------------------------------------------------------------- To reproduce: $ emacs fr.po or $ emacs -nw fr.po Leave the cursor at the beginning of the file. M-x highlight-regexp Regexp to highlight (enter this with Ctrl-Q Ctrl-J for each of the two newlines): ^msgstr\(\[[0-9]\]\)?.* \(".* \)* Highlight using face: hi-yellow Then move around in the buffer and look which lines are highlighted. In the first match already, only 5 out of 11 lines are highlighted. Then, line 300 (in emacs 22) or line 335 (in emacs 21) are not highlighted either. The attached screenshots were produced with emacs-22.2.1 (on i686-pc-linux-gnu) and with emacs-21.2.1 (on powerpc-apple-darwin7.9.0). ---------------------------------------------------------------------------- In GNU Emacs 22.2.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2008-05-01 on linuix Windowing system distributor `The XFree86 Project, Inc', version 11.0.40300001 configured using `configure '--prefix=/packages/gnu'' Important settings: value of $LC_ALL: nil value of $LC_COLLATE: POSIX value of $LC_CTYPE: nil value of $LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC: nil value of $LC_TIME: nil value of $LANG: de_DE.UTF-8 locale-coding-system: utf-8 default-enable-multibyte-characters: t Major mode: Lisp Interaction Minor modes in effect: tooltip-mode: t tool-bar-mode: t mouse-wheel-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t blink-cursor-mode: t unify-8859-on-encoding-mode: t utf-translate-cjk-mode: t auto-compression-mode: t line-number-mode: t Recent input: Recent messages: ("emacs") Loading cl-indent...done Loading derived...done For information about GNU Emacs and the GNU system, type C-h C-a. Loading emacsbug... Loading regexp-opt...done Loading emacsbug...done PS: Where is the bug tracker? I don't see it at https://savannah.gnu.org/projects/emacs -------------- next part -------------- A non-text attachment was scrubbed... Name: emacs21-1.png Type: image/png Size: 18408 bytes Desc: not available Url : http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080506/119869b2/attachment-0004.png -------------- next part -------------- A non-text attachment was scrubbed... Name: emacs22-2.png Type: image/png Size: 19671 bytes Desc: not available Url : http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080506/119869b2/attachment-0005.png -------------- next part -------------- A non-text attachment was scrubbed... Name: emacs21-2.png Type: image/png Size: 20154 bytes Desc: not available Url : http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080506/119869b2/attachment-0006.png -------------- next part -------------- A non-text attachment was scrubbed... Name: emacs22-1.png Type: image/png Size: 18243 bytes Desc: not available Url : http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080506/119869b2/attachment-0007.png -------------- next part -------------- A non-text attachment was scrubbed... Name: fr.po.gz Type: application/x-gzip Size: 44518 bytes Desc: not available Url : http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080506/119869b2/attachment-0001.bin From don at donarmstrong.com Mon May 5 21:35:05 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Mon, 5 May 2008 21:35:05 -0700 Subject: Processed: closing In-Reply-To: <87tzhcoycj.fsf@stupidchicken.com> References: <87tzhcoycj.fsf@stupidchicken.com> Message-ID: Processing commands for control at emacsbugs.donarmstrong.com: > close 145 bug#145: Char 173 has 0-width? 'close' is deprecated; see http://emacsbugs.donarmstrong.com/Developer.html#closing. bug closed, send any further explanations to Stefan Monnier > thanks Stopping processing here. Please contact me if you need assistance. Don Armstrong (administrator, Emacs bugs database) From cyd at stupidchicken.com Mon May 5 21:20:31 2008 From: cyd at stupidchicken.com (Chong Yidong) Date: Tue, 06 May 2008 00:20:31 -0400 Subject: bug#192: regexp does not work as documented Message-ID: <87k5i8ukq8.fsf@stupidchicken.com> > $ emacs fr.po > M-x highlight-regexp > > Regexp to highlight (enter this with Ctrl-Q Ctrl-J for each of the two > newlines): > > ^msgstr\(\[[0-9]\]\)?.* > \(".* > \)* > > Highlight using face: hi-yellow > > Then move around in the buffer and look which lines are highlighted. > In the first match already, only 5 out of 11 lines are highlighted. I believe this bug arises because highlight-regexp uses font-lock to highlight the regular expression, and the font-lock engine is intentionally limiting the region to search for the multi-line regular expression. OTOH, I don't see what we can do about this problem. Maybe we could add a note to the docstring of highlight-regexp saying that multi-line regular expressions are problematic? Does anyone have a suggestion? BTW, here is a simplified recipe, for those who didn't download the attached file: 1. Copy the following text, between the "---...----" lines, into a buffer ------------------ # Messages fran?ais pour GNU gettext. # Copyright ? 2006 Free Software Foundation, Inc. # Fran?ois Pinard , 1996. # # msgid "" msgstr "" "Project-Id-Version: GNU gettext-tools 0.16.2-pre5\n" "Report-Msgid-Bugs-To: bug-gnu-gettext at gnu.org\n" "POT-Creation-Date: 2007-11-02 03:23+0100\n" "PO-Revision-Date: 2007-10-27 13:35+0200\n" "Last-Translator: Christophe Combelles \n" "Language-Team: French \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n > 1);\n" ------------------ 2. M-: (highlight-regexp "^m.*\n\\(\".*\n\\)+") RET Note that the last two lines remain unhighlighted. From bzg at altern.org Tue May 6 02:21:16 2008 From: bzg at altern.org (Bastien Guerry) Date: Tue, 06 May 2008 11:21:16 +0200 Subject: bug#188: 23.0.60; Custom-save deleting custom file In-Reply-To: <87lk2oaz3d.fsf@stupidchicken.com> (Chong Yidong's message of "Mon, 05 May 2008 23:30:30 -0400") References: <87lk2oaz3d.fsf@stupidchicken.com> Message-ID: <87zlr394ab.fsf@bzg.ath.cx> Chong Yidong writes: >> Saving a change with Custom-save deletes the old custom file (in my >> case ~/.emacs-custom.el). This is quite annoying if you don't have >> backups. > > Could you be more specific? Please supply an exact recipe for > reproducing this bug. Yes, sorry. Emacs version: GNU Emacs 23.0.60.1 (i686-pc-linux-gnu, GTK+ Version 2.12.9) of 2008-05-04 on bzg.ath.cx 1. emacs -Q 2. With an existing ~/.emacs-custom.el file, C-x C-e this: (setq custom-file "~/.emacs-custom.el") (load custom-file) 3. M-x customize-face RET font-lock-comment-face RET 4. [Don't do changes...] 5. C-x C-s Then the custom file is now: ,---- | (custom-set-variables | ;; custom-set-variables was added by Custom. | ;; If you edit it by hand, you could mess it up, so be careful. | ;; Your init file should contain only one such instance. | ;; If there is more than one, they won't work right. | ) | | | (custom-set-faces | ;; custom-set-faces was added by Custom. | ;; If you edit it by hand, you could mess it up, so be careful. | ;; Your init file should contain only one such instance. | ;; If there is more than one, they won't work right. | ) `---- As far as I can check, this is a problem with `custom-save-variables' not writing variables in the custom file if they lack some property. Can't help further for now. Thanks, -- Bastien From bruno at clisp.org Tue May 6 04:35:11 2008 From: bruno at clisp.org (Bruno Haible) Date: Tue, 6 May 2008 13:35:11 +0200 Subject: bug#192: regexp does not work as documented In-Reply-To: <87k5i8ukq8.fsf@stupidchicken.com> References: <87k5i8ukq8.fsf@stupidchicken.com> Message-ID: <200805061335.11379.bruno@clisp.org> Chong Yidong wrote: > BTW, here is a simplified recipe, for those who didn't download the > attached file: > > 1. Copy the following text, between the "---...----" lines, into a > buffer > > ------------------ > # Messages fran?ais pour GNU gettext. > # Copyright ? 2006 Free Software Foundation, Inc. > # Fran?ois Pinard , 1996. > # > # > msgid "" > msgstr "" > "Project-Id-Version: GNU gettext-tools 0.16.2-pre5\n" > "Report-Msgid-Bugs-To: bug-gnu-gettext at gnu.org\n" > "POT-Creation-Date: 2007-11-02 03:23+0100\n" > "PO-Revision-Date: 2007-10-27 13:35+0200\n" > "Last-Translator: Christophe Combelles \n" > "Language-Team: French \n" > "MIME-Version: 1.0\n" > "Content-Type: text/plain; charset=UTF-8\n" > "Content-Transfer-Encoding: 8bit\n" > "Plural-Forms: nplurals=2; plural=(n > 1);\n" > ------------------ > > 2. M-: (highlight-regexp "^m.*\n\\(\".*\n\\)+") RET > > Note that the last two lines remain unhighlighted. Yes. I reproduce with this simpler recipe as well. Thank you. > I believe this bug arises because highlight-regexp uses font-lock to > highlight the regular expression, and the font-lock engine is > intentionally limiting the region to search for the multi-line regular > expression. You are right that there is a limit, but it is set to 200000: highlight-regexp is aliased to hi-lock-face-buffer, which asks for the arguments and calls hi-lock-set-pattern. hi-lock-set-pattern does little more than applying a margin of 100000 and calling re-search-forward. I believe the origin of the bug is deeper, because - the limit of 100000 is way larger than the little snippet you posted, - I originally observed the bug in po-mode (part of GNU gettext), in a function po-find-span-of-entry which essentially only calls re-search-backward and re-search-forward. > OTOH, I don't see what we can do about this problem. Maybe we could add > a note to the docstring of highlight-regexp saying that multi-line > regular expressions are problematic? Can someone help me find a workaround, then? If not, I would have to give up maintaining po-mode as part of GNU gettext. Said function is central in Emacs po-mode (everything else relies on it), and if multi-line regular expressions don't work, I don't know how this function could be rewritten. Bruno From rudalics at gmx.at Tue May 6 05:12:45 2008 From: rudalics at gmx.at (martin rudalics) Date: Tue, 06 May 2008 14:12:45 +0200 Subject: bug#192: regexp does not work as documented In-Reply-To: <200805061335.11379.bruno@clisp.org> References: <87k5i8ukq8.fsf@stupidchicken.com> <200805061335.11379.bruno@clisp.org> Message-ID: <48204B3D.6000500@gmx.at> > Can someone help me find a workaround, then? If not, I would have to give up > maintaining po-mode as part of GNU gettext. Said function is central in > Emacs po-mode (everything else relies on it), and if multi-line regular > expressions don't work, I don't know how this function could be rewritten. Don't worry, Stefan will find the solution. First of all you will probably have to (setq font-lock-multiline t) in the respective buffer. This will _not_ always DTRT after a buffer modification, as, for example, in AAAA CCCC BBBB where AAAA stands for some old text previously matched by your regexp, CCCC for some new text inserted (or old text removed), and BBBB for some text which, after the change, is now matched by the regexp (or not matched any more): In this case BBBB will be wrongly highlighted now. Alan uses the notorious `font-lock-extend-jit-lock-region-after-change' function to handle this, but it's not immediately clear how to apply this here. If everything else fails you will have to refontify till `window-end' (I prefer using a timer for such refontifications). From koppel at ece.lsu.edu Tue May 6 08:00:12 2008 From: koppel at ece.lsu.edu (David Koppelman) Date: Tue, 06 May 2008 10:00:12 -0500 Subject: bug#192: regexp does not work as documented In-Reply-To: <87k5i8ukq8.fsf@stupidchicken.com> (Chong Yidong's message of "Tue, 06 May 2008 00:20:31 -0400") References: <87k5i8ukq8.fsf@stupidchicken.com> Message-ID: Later in the week I'll look into it and provide either a fix or document the limitation. Chong Yidong writes: > OTOH, I don't see what we can do about this problem. Maybe we could add > a note to the docstring of highlight-regexp saying that multi-line > regular expressions are problematic? Does anyone have a suggestion? Chong Yidong writes: >> $ emacs fr.po >> M-x highlight-regexp >> >> Regexp to highlight (enter this with Ctrl-Q Ctrl-J for each of the two >> newlines): >> >> ^msgstr\(\[[0-9]\]\)?.* >> \(".* >> \)* >> >> Highlight using face: hi-yellow >> >> Then move around in the buffer and look which lines are highlighted. >> In the first match already, only 5 out of 11 lines are highlighted. > > I believe this bug arises because highlight-regexp uses font-lock to > highlight the regular expression, and the font-lock engine is > intentionally limiting the region to search for the multi-line regular > expression. > > OTOH, I don't see what we can do about this problem. Maybe we could add > a note to the docstring of highlight-regexp saying that multi-line > regular expressions are problematic? Does anyone have a suggestion? > > > BTW, here is a simplified recipe, for those who didn't download the > attached file: > > 1. Copy the following text, between the "---...----" lines, into a > buffer > > ------------------ > # Messages fran?ais pour GNU gettext. > # Copyright ? 2006 Free Software Foundation, Inc. > # Fran?ois Pinard , 1996. > # > # > msgid "" > msgstr "" > "Project-Id-Version: GNU gettext-tools 0.16.2-pre5\n" > "Report-Msgid-Bugs-To: bug-gnu-gettext at gnu.org\n" > "POT-Creation-Date: 2007-11-02 03:23+0100\n" > "PO-Revision-Date: 2007-10-27 13:35+0200\n" > "Last-Translator: Christophe Combelles \n" > "Language-Team: French \n" > "MIME-Version: 1.0\n" > "Content-Type: text/plain; charset=UTF-8\n" > "Content-Transfer-Encoding: 8bit\n" > "Plural-Forms: nplurals=2; plural=(n > 1);\n" > ------------------ > > 2. M-: (highlight-regexp "^m.*\n\\(\".*\n\\)+") RET > > Note that the last two lines remain unhighlighted. From monnier at iro.umontreal.ca Tue May 6 08:35:01 2008 From: monnier at iro.umontreal.ca (Stefan Monnier) Date: Tue, 06 May 2008 11:35:01 -0400 Subject: bug#192: regexp does not work as documented In-Reply-To: <200805061335.11379.bruno@clisp.org> (Bruno Haible's message of "Tue, 6 May 2008 13:35:11 +0200") References: <87k5i8ukq8.fsf@stupidchicken.com> <200805061335.11379.bruno@clisp.org> Message-ID: > You are right that there is a limit, but it is set to 200000: > highlight-regexp is aliased to hi-lock-face-buffer, which asks for the > arguments and calls hi-lock-set-pattern. hi-lock-set-pattern does little > more than applying a margin of 100000 and calling re-search-forward. Actually, font-lock-fontified is most likely set to t, so hi-lock-set-pattern doesn't call re-sarch-forward at all and only calls font-lock-fontify-buffer instead. > - I originally observed the bug in po-mode (part of GNU gettext), in > a function po-find-span-of-entry which essentially only calls > re-search-backward and re-search-forward. Please try and reproduce the problem there and send us a recipe. Stefan From bruno at clisp.org Tue May 6 14:29:05 2008 From: bruno at clisp.org (Bruno Haible) Date: Tue, 6 May 2008 23:29:05 +0200 Subject: bug#192: regexp does not work as documented In-Reply-To: References: <87k5i8ukq8.fsf@stupidchicken.com> <200805061335.11379.bruno@clisp.org> Message-ID: <200805062329.05484.bruno@clisp.org> Stefan Monnier wrote: > Actually, font-lock-fontified is most likely set to t, so > hi-lock-set-pattern doesn't call re-sarch-forward at all and only calls > font-lock-fontify-buffer instead. You're right: If I do a M-x evaluate-expression (setq font-lock-fontify-buffer nil) before M-x highlight-regexp the result is correct. So the problem is indeed with the font-locking. Bruno From bruno at clisp.org Tue May 6 14:35:59 2008 From: bruno at clisp.org (Bruno Haible) Date: Tue, 6 May 2008 23:35:59 +0200 Subject: bug#192: regexp does not work as documented In-Reply-To: References: <87k5i8ukq8.fsf@stupidchicken.com> Message-ID: <200805062335.59206.bruno@clisp.org> David Koppelman wrote: > Later in the week I'll look into it and provide either a fix > or document the limitation. Thank you! Chong Yidong wrote: > > OTOH, I don't see what we can do about this problem. Maybe we could add > > a note to the docstring of highlight-regexp saying that multi-line > > regular expressions are problematic? Does anyone have a suggestion? As an end user, for testing the effect of a regexp on a buffer interactively, I would prefer to have a "volatile" coloring (i.e. one that disappears at the next buffer modification) but is correct, rather than a documented-to-be-wrong coloring that updates itself correctly during buffer modifications. Less functionality but implemented correctly. OTOH, third-party packages may prefer the current behaviour if their regexps match only portions of a line. Bruno From rhansen at bbn.com Tue May 6 14:49:13 2008 From: rhansen at bbn.com (Richard Hansen) Date: Tue, 06 May 2008 17:49:13 -0400 Subject: bug#193: Fill for // (C++) style comments in C (C99) Message-ID: <4820D259.2060805@bbn.com> It appears that filling C++-style comments inside C99 code via c-fill-paragraph is still broken. This bug was previously reported[1] in November 2006 and was extensively discussed, but it looks like no fix was ever committed. [1] http://lists.gnu.org/archive/html/emacs-devel/2006-11/msg00868.html -Richard From monnier at iro.umontreal.ca Tue May 6 18:04:19 2008 From: monnier at iro.umontreal.ca (Stefan Monnier) Date: Tue, 06 May 2008 21:04:19 -0400 Subject: bug#192: regexp does not work as documented In-Reply-To: <200805062335.59206.bruno@clisp.org> (Bruno Haible's message of "Tue, 6 May 2008 23:35:59 +0200") References: <87k5i8ukq8.fsf@stupidchicken.com> <200805062335.59206.bruno@clisp.org> Message-ID: > As an end user, for testing the effect of a regexp on a buffer interactively, > I would prefer to have a "volatile" coloring (i.e. one that disappears at the > next buffer modification) but is correct, rather than a documented-to-be-wrong > coloring that updates itself correctly during buffer modifications. Less > functionality but implemented correctly. Actually, we can get the combination of the two. hilight-changes (c|sh)ould use its own loop with re-search-forward, even when font-lock is enabled. This way the highlighting would be initially correct, and in some cases it would also be correctly preserved/discovered later on. This would only be used for regexp that can span multiple lines, so highlight-changes (c|sh)ould analyse the regexp to see if there's a possibility for it to match multiple lines. Stefan From md5i at cs.cmu.edu Tue May 6 20:41:16 2008 From: md5i at cs.cmu.edu (Michael Welsh Duggan) Date: Tue, 06 May 2008 23:41:16 -0400 Subject: bug#124: 23.0.60; Incorrect fontification for man in utf8 environment Message-ID: <87y76mixwj.fsf@maru.md5i.com> A non-text attachment was scrubbed... Name: man.out Type: application/octet-stream Size: 31402 bytes Desc: not available Url : http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080506/0d33a98b/attachment-0001.obj From thorne at timbral.net Tue May 6 21:59:01 2008 From: thorne at timbral.net (Evans Winner) Date: Tue, 6 May 2008 22:59:01 -0600 (MDT) Subject: bug#194: 23.0.60; Building from cvs on Hurd Message-ID: <20080507045901.039E41B505@mail.timbral.net> I am trying to compile Emacs from today/yesterday cvs on a freshly installed Debian/GNU/Hurd/Mach (K16) system. (That platform is supported, isn't it?). I have tried a couple of different times with different ./configure options, but always get the compile error in sysdep.c. I have included what looks like the relevant bit inline below. I'm sorry that I have absolutely no idea how to debug non-trivial C code. I hope this might be useful. Please ask for any other desired information. ===================== The bit the error message seems to refer to (with a few lines of context) is: #ifndef DOS_NT struct emacs_tty s; EMACS_GET_TTY (out, &s); #if defined (HAVE_TERMIO) || defined (HAVE_TERMIOS) s.main.c_oflag |= OPOST; /* Enable output postprocessing */ s.main.c_oflag &= ~ONLCR; /* Disable map of NL to CR-NL on output */ #ifdef NLDLY s.main.c_oflag &= ~(NLDLY|CRDLY|TABDLY|BSDLY|VTDLY|FFDLY); /* No output delays */ ====================== [uname -a: GNU hurd 0.3 GNU-Mach 1.3.99/Hurd-0.3 i386-AT386 GNU] ====================== Output of make bootstrap: gcc -c -Demacs -DHAVE_CONFIG_H -I. -I/home/thorne/src/emacs/src -g -O2 -Wno-pointer-sign sysdep.c sysdep.c: In function 'wait_for_termination': sysdep.c:491: warning: 'sigsetmask' is deprecated (declared at /usr/include/signal.h:184) sysdep.c:494: warning: 'sigsetmask' is deprecated (declared at /usr/include/signal.h:184) sysdep.c: In function 'child_setup_tty': sysdep.c:605: error: 'FFDLY' undeclared (first use in this function) sysdep.c:605: error: (Each undeclared identifier is reported only once sysdep.c:605: error: for each function it appears in.) sysdep.c: In function 'request_sigio': sysdep.c:997: warning: 'sigblock' is deprecated (declared at /usr/include/signal.h:181) sysdep.c:997: warning: 'sigsetmask' is deprecated (declared at /usr/include/signal.h:184) sysdep.c:999: warning: 'sigblock' is deprecated (declared at /usr/include/signal.h:181) sysdep.c:999: warning: 'sigsetmask' is deprecated (declared at /usr/include/signal.h:184) sysdep.c: In function 'unrequest_sigio': sysdep.c:1016: warning: 'sigblock' is deprecated (declared at /usr/include/signal.h:181) sysdep.c:1018: warning: 'sigblock' is deprecated (declared at /usr/include/signal.h:181) make[2]: *** [sysdep.o] Error 1 make[2]: Leaving directory `/home/thorne/src/emacs/src' make[1]: *** [bootstrap-build] Error 2 make[1]: Leaving directory `/home/thorne/src/emacs' make: *** [bootstrap] Error 2 From espen.wiborg at telio.no Wed May 7 02:42:10 2008 From: espen.wiborg at telio.no (Espen Wiborg) Date: Wed, 07 May 2008 11:42:10 +0200 Subject: bug#162: 23.0.60; Infinite loop in encode-coding-string (utf-7-imap) In-Reply-To: (Emacs bug Tracking System's message of "Mon, 28 Apr 2008 09:45:03 -0700") References: <87od7ujlr2.fsf@telio.no> Message-ID: <87ej8elabx.fsf_-_@telio.no> A non-text attachment was scrubbed... Name: 162.patch Type: text/x-diff Size: 570 bytes Desc: not available Url : http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080507/43cfbd2e/attachment.patch From don at donarmstrong.com Wed May 7 07:30:03 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Wed, 7 May 2008 07:30:03 -0700 Subject: Processed: toto In-Reply-To: References: Message-ID: Processing commands for control at emacsbugs.donarmstrong.com: > tag 162 +patch bug#162: 23.0.60; Infinite loop in encode-coding-string (utf-7-imap) There were no tags set. Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Don Armstrong (administrator, Emacs bugs database) From nathaniel.cunningham at gmail.com Wed May 7 08:17:46 2008 From: nathaniel.cunningham at gmail.com (Nathaniel Cunningham) Date: Wed, 7 May 2008 10:17:46 -0500 Subject: bug#195: menu bar misbehavior during (ispell-buffer) Message-ID: <20ecf6c70805070817l48d51df8s21bc0e4ef611269f@mail.gmail.com> When (ispell-buffer) is underway in one frame, and the displayed buffer in another frame has different/additional menu bar items, selecting that second frame doesn't update the menu bar. However, clicking on the menu bar *does* trigger a change to the menu bar categories, which means you may click on the wrong item! (i.e. the menu bar item under the mouse pointer may not be the same with or without mouse-1) In GNU Emacs 22.2.50.2 (i386-apple-darwin9.2.2, Carbon Version 1.6.0) of 2008-05-05 on plume.sr.unh.edu Windowing system distributor `Apple Inc.', version 10.4.11 configured using `configure '--without-x' '--prefix=/usr/local'' Important settings: value of $LC_ALL: nil value of $LC_COLLATE: nil value of $LC_CTYPE: nil value of $LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC: nil value of $LC_TIME: nil value of $LANG: nil locale-coding-system: iso-8859-1 default-enable-multibyte-characters: t Major mode: Emacs-Lisp Minor modes in effect: tooltip-mode: t tool-bar-mode: t mouse-wheel-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t blink-cursor-mode: t unify-8859-on-encoding-mode: t utf-translate-cjk-mode: t auto-compression-mode: t line-number-mode: t Recent input: C-x C-f D e s k i s p e C-x 5 2 C-_ C-_ C-x C-f ~ / D o c u [ r p r o g r a m a s p e t e s t t e s t q < send-emacs-bug-report> Recent messages: For information about GNU Emacs and the GNU system, type C-h C-a. Undo! undo-more: No further undo information testspell.txt has auto save data; consider M-x recover-this-file Loading ispell...done Loading regexp-opt...done Starting new Ispell process [default] ... Spell checking testspell.txt using aspell with default dictionary... Ispell process killed Loading emacsbug...done -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080507/148f7afc/attachment.htm From mail2kyle at gmail.com Wed May 7 10:59:34 2008 From: mail2kyle at gmail.com (Kyle M. Lee) Date: Thu, 08 May 2008 01:59:34 +0800 Subject: bug#196: 23.0.60; emacs hangs on WinXP with --disable-font-backend, and backtrace Message-ID: <4821EE06.9040409@gmail.com> E:\cvs_home\emacs23\emacs\src>gdb .\emacs.exe GNU gdb 6.8 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later 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 "i686-pc-mingw32"... SIGINT is used by the debugger. Are you sure you want to change it? (y or n) [answered Y; input not from termina l] Environment variable "DISPLAY" not defined. Environment variable "TERM" not defined. Breakpoint 1 at 0x11b3fe5: file w32fns.c, line 9490. Breakpoint 2 at 0x10be7de: file sysdep.c, line 1317. (gdb) r Starting program: E:\cvs_home\emacs23\emacs\src/.\emacs.exe [New thread 5048.0x1270] [New thread 5048.0x13bc] [New thread 5048.0x3e4] Program exited normally. (gdb) r --disable-font-backend Starting program: E:\cvs_home\emacs23\emacs\src/.\emacs.exe --disable-font-backe nd [New thread 1032.0xb0c] [New thread 1032.0x17a8] [New thread 1032.0x1668] Program exited normally. (gdb) xbacktrace Cannot access memory at address 0x82f6d4 (gdb) r --disable-font-backend Starting program: E:\cvs_home\emacs23\emacs\src/.\emacs.exe --disable-font-backe nd [New thread 5804.0xf84] [New thread 5804.0x14e8] [New thread 5804.0x1254] [New thread 5804.0xf00] [New thread 5804.0x1a4] [Switching to thread 5804.0x1a4] Quit (expect signal SIGINT when the program is resumed) (gdb) b No default breakpoint address now. (gdb) No default breakpoint address now. (gdb) No default breakpoint address now. (gdb) xbacktrace (gdb) back #0 0x7c810659 in KERNEL32!CreateThread () from C:\WINDOWS\system32\kernel32.dll #1 0x0400ff81 in ?? () #2 0x75ff0000 in ?? () #3 0x029e6818 in ?? () #4 0x006a0000 in ?? () #5 0xff1475ff in ?? () #6 0x50571075 in ?? () #7 0xf74a830f in ?? () #8 0xc9330002 in ?? () #9 0x14e88f8a in ?? () #10 0xe18377d1 in ?? () #11 0x8d14ff3f in ?? () #12 0x77d118e8 in ?? () from C:\WINDOWS\system32\user32.dll #13 0xfffefae9 in ?? () #14 0x909090ff in ?? () #15 0xff8b9090 in ?? () #16 0xe8ec8b55 in ?? () #17 0xffffd214 in ?? () #18 0x39084d8b in ?? () #19 0x20740841 in ?? () #20 0x6456098b in ?? () #21 0x000018a1 in ?? () #22 0x51006a00 in ?? () #23 0x7fe8f08b in ?? () #24 0x2bffffd2 in ?? () #25 0xf75e2046 in ?? () #26 0x40c01bd8 in ?? () #27 0x0004c25d in ?? () #28 0xeb40c033 in ?? () #29 0x909090f7 in ?? () #30 0x106a9090 in ?? () #31 0xd1b4d068 in ?? () #32 0xd141e877 in ?? () #33 0xa164ffff in ?? () #34 0x00000018 in ?? () #35 0x06f4b08b in ?? () #36 0xb88b0000 in ?? () #37 0x000006fc in ?? () #38 0x4589c033 in ?? () #39 0x0113b9e4 in scan_for_column (endpos=Cannot access memory at address 0x10c2 65 ) at indent.c:623 Backtrace stopped: previous frame inner to this frame (corrupt stack?) (gdb) In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600) of 2008-05-08 on RAZ0R Windowing system distributor `Microsoft Corp.', version 5.1.2600 configured using `configure --with-gcc (3.4) --no-opt --cflags -I./inc -pipe' Important settings: value of $LC_ALL: nil value of $LC_COLLATE: nil value of $LC_CTYPE: nil value of $LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC: nil value of $LC_TIME: nil value of $LANG: CHS value of $XMODIFIERS: nil locale-coding-system: cp936 default-enable-multibyte-characters: t Major mode: Fundamental Minor modes in effect: which-function-mode: t yas/minor-mode: t desktop-save-mode: t recentf-mode: t show-paren-mode: t auto-image-file-mode: t tabbar-mwheel-mode: t tabbar-mode: t tooltip-mode: t mouse-wheel-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t blink-cursor-mode: t global-auto-composition-mode: t auto-composition-mode: t auto-encryption-mode: t auto-compression-mode: t column-number-mode: t line-number-mode: t transient-mark-mode: t Recent input: Recent messages: Setting up cedet-contrib...done Loading d:/home/.emacs.d/site-lisp/cedet/common/cedet.el (source)...done Loading d:/home/.emacs.d/.emacs_custom.el (source)... Loading semantic-idle...done Loading which-func...done Loading d:/home/.emacs.d/.emacs_custom.el (source)...done Loading outline...done Loading vc-cvs...done [17 times] Desktop: 33 buffers restored. For information about GNU Emacs and the GNU system, type C-h C-a. From user42 at zip.com.au Wed May 7 16:37:54 2008 From: user42 at zip.com.au (Kevin Ryde) Date: Thu, 08 May 2008 09:37:54 +1000 Subject: bug#197: next-error wrong position in target file Message-ID: <87iqxp7kj1.fsf@blah.blah> An embedded and charset-unspecified text was scrubbed... Name: foo.txt Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080508/0580f6eb/attachment.txt From cyd at stupidchicken.com Wed May 7 19:17:24 2008 From: cyd at stupidchicken.com (Chong Yidong) Date: Wed, 07 May 2008 22:17:24 -0400 Subject: bug#188: 23.0.60; Custom-save deleting custom file In-Reply-To: <87zlr394ab.fsf@bzg.ath.cx> (Bastien Guerry's message of "Tue, 06 May 2008 11:21:16 +0200") References: <87lk2oaz3d.fsf@stupidchicken.com> <87zlr394ab.fsf@bzg.ath.cx> Message-ID: <87myn1y1xn.fsf@stupidchicken.com> Bastien Guerry writes: > 1. emacs -Q > 2. With an existing ~/.emacs-custom.el file, C-x C-e this: > > (setq custom-file "~/.emacs-custom.el") > (load custom-file) > > 3. M-x customize-face RET font-lock-comment-face RET > 4. [Don't do changes...] > 5. C-x C-s > > Then the custom file is now: > > ,---- > | (custom-set-variables > | ;; custom-set-variables was added by Custom. > | ;; If you edit it by hand, you could mess it up, so be careful. > | ;; Your init file should contain only one such instance. > | ;; If there is more than one, they won't work right. > | ) > | > | > | (custom-set-faces > | ;; custom-set-faces was added by Custom. > | ;; If you edit it by hand, you could mess it up, so be careful. > | ;; Your init file should contain only one such instance. > | ;; If there is more than one, they won't work right. > | ) > `---- > > As far as I can check, this is a problem with `custom-save-variables' > not writing variables in the custom file if they lack some property. I don't see any problem. If the custom-file was originally empty, that above result is what I see. But if the custom-file originally contains customizations (which is not explained in your recipe, but which I tried), those customizations are not lost. Where's the problem? From lennart.borgman at gmail.com Thu May 8 01:16:59 2008 From: lennart.borgman at gmail.com (Lennart Borgman (gmail)) Date: Thu, 08 May 2008 10:16:59 +0200 Subject: bug#198: 23.0.60; Different heights for customize faces Message-ID: <4822B6FB.9030102@gmail.com> The heights for custom-variable-tag-face and custom-face-tag differs. In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600) of 2008-05-07 From don at donarmstrong.com Thu May 8 04:45:04 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Thu, 8 May 2008 04:45:04 -0700 Subject: Processed: (no subject) In-Reply-To: <4822E67B.90007@gnu.org> References: <4822E67B.90007@gnu.org> Message-ID: Processing commands for control at emacsbugs.donarmstrong.com: > tags 132 moreinfo bug#132: emacs crashes on There were no tags set. Tags added: moreinfo > End of message, stopping processing here. Please contact me if you need assistance. Don Armstrong (administrator, Emacs bugs database) From don at donarmstrong.com Thu May 8 04:50:04 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Thu, 8 May 2008 04:50:04 -0700 Subject: bug#136: marked as done (23.0.60; bad link underlining in Info) References: <4822E766.1020601@gnu.org> <4802FBC5.9050207@gmail.com> Message-ID: Your message dated Thu, 08 May 2008 12:43:34 +0100 with message-id <4822E766.1020601 at gnu.org> and subject line Re: 23.0.60; bad link underlining in Info has caused the Emacs bug report #134, regarding 23.0.60; bad link underlining in Info to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact don at donarmstrong.com immediately.) -- 134: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=134 Emacs Bug Tracking System Contact don at donarmstrong.com with problems -------------- next part -------------- An embedded message was scrubbed... From: "Lennart Borgman (gmail)" Subject: Re: 23.0.60; bad link underlining in Info Date: Mon, 14 Apr 2008 08:37:57 +0200 Size: 2360 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080508/86547279/attachment-0002.eml -------------- next part -------------- An embedded message was scrubbed... From: Jason Rumney Subject: Re: 23.0.60; bad link underlining in Info Date: Thu, 08 May 2008 12:43:34 +0100 Size: 1963 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080508/86547279/attachment-0003.eml From jasonr at gnu.org Thu May 8 04:34:42 2008 From: jasonr at gnu.org (Jason Rumney) Date: Thu, 08 May 2008 12:34:42 +0100 Subject: bug#167: 23.0.60; new frames ignore set-default-font In-Reply-To: <50e027900804290601k38703f72hbf93d193a116ff78@mail.gmail.com> References: <50e027900804290601k38703f72hbf93d193a116ff78@mail.gmail.com> Message-ID: <4822E552.6010508@gnu.org> Jim Hunziker wrote: > I am using the Xft font backend and Emacs from CVS. I am using the > Andale Mono-13 font from msttcorefonts. > > When using the setting (set-default-font "Andale Mono-13") in my > .emacs file, new frames created with M-x 5 2 don't use the default > font. (The initial frame does use the font.) > I think this is by design. set-default-font is an alias for set-frame-font, and it only sets the default font for the current frame. To set the font for future frames, you need to set the font frame-parameter in default-frame-alist. From don at donarmstrong.com Thu May 8 04:45:03 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Thu, 8 May 2008 04:45:03 -0700 Subject: Processed: (no subject) In-Reply-To: <4822E591.9060203@gnu.org> References: <4822E591.9060203@gnu.org> Message-ID: Processing commands for control at emacsbugs.donarmstrong.com: > tag 167 wontfix bug#167: 23.0.60; new frames ignore set-default-font There were no tags set. Tags added: wontfix > End of message, stopping processing here. Please contact me if you need assistance. Don Armstrong (administrator, Emacs bugs database) From don at donarmstrong.com Thu May 8 04:50:04 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Thu, 8 May 2008 04:50:04 -0700 Subject: bug#134: marked as done (23.0.60; bad link underlining in Info) References: <4822E766.1020601@gnu.org> <000a01c89dc5$b8e5df90$0200a8c0@us.oracle.com> Message-ID: Your message dated Thu, 08 May 2008 12:43:34 +0100 with message-id <4822E766.1020601 at gnu.org> and subject line Re: 23.0.60; bad link underlining in Info has caused the Emacs bug report #134, regarding 23.0.60; bad link underlining in Info to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact don at donarmstrong.com immediately.) -- 134: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=134 Emacs Bug Tracking System Contact don at donarmstrong.com with problems -------------- next part -------------- An embedded message was scrubbed... From: "Drew Adams" Subject: 23.0.60; bad link underlining in Info Date: Sun, 13 Apr 2008 17:23:11 -0700 Size: 30708 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080508/f07b27fa/attachment-0002.eml -------------- next part -------------- An embedded message was scrubbed... From: Jason Rumney Subject: Re: 23.0.60; bad link underlining in Info Date: Thu, 08 May 2008 12:43:34 +0100 Size: 1963 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080508/f07b27fa/attachment-0003.eml From jasonr at gnu.org Thu May 8 04:50:23 2008 From: jasonr at gnu.org (Jason Rumney) Date: Thu, 08 May 2008 12:50:23 +0100 Subject: bug#196: 23.0.60; emacs hangs on WinXP with --disable-font-backend, and backtrace In-Reply-To: <4821EE06.9040409@gmail.com> References: <4821EE06.9040409@gmail.com> Message-ID: <4822E8FF.1090706@gnu.org> Is the bug reproducable without --disable-font-backend? The old font code is due to be removed soon, so there is no point in spending too much time tracking down and fixing bugs in it now. From don at donarmstrong.com Thu May 8 04:55:05 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Thu, 8 May 2008 04:55:05 -0700 Subject: Processed: --disable-font-backend will be removed soon In-Reply-To: <4822E7F0.5020607@gnu.org> References: <4822E7F0.5020607@gnu.org> Message-ID: Processing commands for control at emacsbugs.donarmstrong.com: > tags 187 wontfix bug#187: 23.0.60; Font properties does not apply to international characters. There were no tags set. Tags added: wontfix > End of message, stopping processing here. Please contact me if you need assistance. Don Armstrong (administrator, Emacs bugs database) From tim.vanholder at gmail.com Thu May 8 06:14:00 2008 From: tim.vanholder at gmail.com (Tim Van Holder) Date: Thu, 08 May 2008 15:14:00 +0200 Subject: bug#199: 23.0.60; Frame sizing problem with toolbar containing no toolbar buttons Message-ID: <87hcd97xbb.fsf@leeloo.anubex.internal> CVS emacs of this morning, with GTK toolkit (rebuilt, not bootstrapped). Buffers with no associated toolbar buttons now show an empty toolbar (which is probably the actual bug). But an empty toolbar isn't as high as one with buttons, resulting in the rest of the frame getting shifted up, leaving a smallish empty area at the bottom of the frame (below the minibuffer). So either the toolbar needs to be hidden entirely, or the screen painting code needs to take this height difference into account. To reproduce: run report-emacs-bug, enter a subject, and switch between the message and the *Bug Help* buffer. From svenjoac at gmx.de Thu May 8 06:52:07 2008 From: svenjoac at gmx.de (Sven Joachim) Date: Thu, 08 May 2008 15:52:07 +0200 Subject: bug#200: 23.0.60; recode-region leaves the region active Message-ID: <871w4cvr7c.fsf@gmx.de> In transient-mark-mode, recode-region does not deactivate the mark when it's finished. Moreover, pressing C-x u afterwards ("undo in region") will delete the region, multiple presses of C-x u do not recover from this (only when the region is deactivated). In GNU Emacs 23.0.60.2 (i686-pc-linux-gnu, GTK+ Version 2.12.9) of 2008-05-08 on debian Windowing system distributor `The X.Org Foundation', version 11.0.10300000 Important settings: value of $LC_ALL: nil value of $LC_COLLATE: C value of $LC_CTYPE: nil value of $LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC: nil value of $LC_TIME: nil value of $LANG: de_DE.UTF-8 value of $XMODIFIERS: nil locale-coding-system: utf-8-unix default-enable-multibyte-characters: t Major mode: Fundamental Minor modes in effect: tooltip-mode: t tool-bar-mode: t mouse-wheel-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t blink-cursor-mode: t global-auto-composition-mode: t auto-composition-mode: t auto-encryption-mode: t auto-compression-mode: t line-number-mode: t transient-mark-mode: t Recent input: C-x 1 C-SPC C-v C-v C-l M-x r e c o d e - r e g m u i s o l 1 C-x u C-x u C-l C-x u C-x u C-SPC M-x m u i s o l 1 C-x u C-x u C-x u C-x u C-x u C-x u M-x r e p o r t - e m < return> Recent messages: undo-more: No further undo information for region call-interactively: Beginning of buffer [2 times] Mark set Redo! Undo! Mark set [2 times] Undo in region! [3 times] undo-more: No further undo information for region Redo! Undo! From jasonr at gnu.org Thu May 8 08:00:11 2008 From: jasonr at gnu.org (Jason Rumney) Date: Thu, 08 May 2008 16:00:11 +0100 Subject: bug#169: 23.0.60; Umlaut chars with 'face property set to 'bold aren't displayed in bold with --disable-font-backend In-Reply-To: <87d4o7d7cv.fsf@baldur.tsdh.de> References: <87d4o7d7cv.fsf@baldur.tsdh.de> Message-ID: <4823157B.30200@gnu.org> Tassilo Horn wrote: > I use a very recent CVS checkout compiled with --disable-font-backend. > > (insert (propertize "test???????test" 'font-lock-face 'bold)) > > The umlauts between the "test"s won't be displayed in bold, although the > misc-fixed font contains bold versions of all those chars. Can you reproduce this without compiling with --disable-font-backend, or in Emacs 22? From jasonr at gnu.org Thu May 8 08:10:16 2008 From: jasonr at gnu.org (Jason Rumney) Date: Thu, 08 May 2008 16:10:16 +0100 Subject: bug#119: modify-frame-parameters in Emacs 23 for fonts Message-ID: <482317D8.5080003@gnu.org> I've marked this as fixed, since the bug reported will be fixed when font-backend is merged. I will not close it at this time though, as valid points about documentation were raised. From don at donarmstrong.com Thu May 8 08:15:05 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Thu, 8 May 2008 08:15:05 -0700 Subject: Processed: (no subject) In-Reply-To: <48231783.4000507@gnu.org> References: <48231783.4000507@gnu.org> Message-ID: Processing commands for control at emacsbugs.donarmstrong.com: > tags 36 moreinfo bug#36: 23.0.60; Segmentation fault when deleting Emacs frame There were no tags set. Tags added: moreinfo > tags 63 moreinfo bug#63: 23.0.60; Emacs consumes all CPU while idle There were no tags set. Tags added: moreinfo > tags 119 fixed bug#119: modify-frame-parameters in Emacs 23 for fonts There were no tags set. Tags added: fixed > severity 121 wishlist bug#121: 22.2.50; Display of "zero width no-break space" (U+FEFF) Severity set to `wishlist' from `normal' > severity 181 wishlist bug#181: 23.0.60; OSX: Case insensitive file name completion Severity set to `wishlist' from `normal' > tags 188 moreinfo bug#188: 23.0.60; Custom-save deleting custom file There were no tags set. Tags added: moreinfo > End of message, stopping processing here. Please contact me if you need assistance. Don Armstrong (administrator, Emacs bugs database) From mail2kyle at gmail.com Thu May 8 08:34:35 2008 From: mail2kyle at gmail.com (Kyle M. Lee) Date: Thu, 08 May 2008 23:34:35 +0800 Subject: bug#196: 23.0.60; emacs hangs on WinXP with --disable-font-backend, and backtrace In-Reply-To: <4822E8FF.1090706@gnu.org> References: <4821EE06.9040409@gmail.com> <4822E8FF.1090706@gnu.org> Message-ID: <48231D8B.3030305@gmail.com> Jason Rumney ??: > Is the bug reproducable without --disable-font-backend? No. > > The old font code is due to be removed soon, so there is no point in > spending too much time tracking down and fixing bugs in it now. > I agree this point. But the new font backend is really slow now. I think my computer is powerful enough to run an editor (or OS ? :). From don at donarmstrong.com Thu May 8 10:10:05 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Thu, 8 May 2008 10:10:05 -0700 Subject: Processed: (no subject) In-Reply-To: <48233245.2070908@gnu.org> References: <48233245.2070908@gnu.org> Message-ID: Processing commands for control at emacsbugs.donarmstrong.com: > severity 203 wishlist bug#203: Maximize frame does not work at startup Severity set to `wishlist' from `normal' > End of message, stopping processing here. Please contact me if you need assistance. Don Armstrong (administrator, Emacs bugs database) From don at donarmstrong.com Thu May 8 10:15:03 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Thu, 8 May 2008 10:15:03 -0700 Subject: Processed: Re: 23.0.60; emacs hangs on WinXP with --disable-font-backend, and backtrace In-Reply-To: <482333DA.90504@gnu.org> References: <482333DA.90504@gnu.org> Message-ID: Processing commands for control at emacsbugs.donarmstrong.com: > tags 196 wontfix bug#196: 23.0.60; emacs hangs on WinXP with --disable-font-backend, and backtrace There were no tags set. Tags added: wontfix > End of message, stopping processing here. Please contact me if you need assistance. Don Armstrong (administrator, Emacs bugs database) From harven at free.fr Thu May 8 09:49:20 2008 From: harven at free.fr (harven) Date: Thu, 8 May 2008 09:49:20 -0700 (PDT) Subject: bug#204: documentation bug Message-ID: <50496f77-5c30-400d-ab9b-3ec3ffa484e7@m44g2000hsc.googlegroups.com> In Gnu Emacs Manual version 22.1, there is an entry "television" in the index. It refers to section Appending Kills. I can't see anything relevant to "television" in this section, so may be the entry should be removed. From don at donarmstrong.com Thu May 8 11:20:04 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Thu, 8 May 2008 11:20:04 -0700 Subject: bug#204: marked as done (documentation bug) References: <87d4nwvfbw.fsf@stupidchicken.com> <50496f77-5c30-400d-ab9b-3ec3ffa484e7@m44g2000hsc.googlegroups.com> Message-ID: Your message dated Thu, 08 May 2008 14:08:35 -0400 with message-id <87d4nwvfbw.fsf at stupidchicken.com> and subject line Re: bug#204: documentation bug has caused the Emacs bug report #204, regarding documentation bug to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact don at donarmstrong.com immediately.) -- 204: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=204 Emacs Bug Tracking System Contact don at donarmstrong.com with problems -------------- next part -------------- An embedded message was scrubbed... From: harven Subject: documentation bug Date: Thu, 8 May 2008 09:49:20 -0700 (PDT) Size: 3698 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080508/6a29893d/attachment.eml -------------- next part -------------- An embedded message was scrubbed... From: Chong Yidong Subject: Re: bug#204: documentation bug Date: Thu, 08 May 2008 14:08:35 -0400 Size: 1609 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080508/6a29893d/attachment-0001.eml From reinersteib+gmane at imap.cc Thu May 8 14:14:08 2008 From: reinersteib+gmane at imap.cc (Reiner Steib) Date: Thu, 08 May 2008 23:14:08 +0200 Subject: bug#205: 23.0.60; smerge-command-prefix custom type Message-ID: Hi, customizing `smerge-command-prefix' ends up like this: ,----[ M-x customize-variable RET smerge-command-prefix RET ] | Smerge Command Prefix: [Hide Value] [Value Menu] String: ^C^ | [State]: STANDARD. | Prefix for `smerge-mode' commands. | -UUU:**--F1 *Customize Option: Smerge Command Prefix* (Custom)---- | Available choices: | | 0 = String | 1 = String | 2 = String | 3 = String `---- All choices look the same. I'd suggest to install this patch... --8<---------------cut here---------------start------------->8--- --- smerge-mode.el 12 Apr 2008 11:36:45 +0200 1.66 +++ smerge-mode.el 08 May 2008 23:05:59 +0200 @@ -160,7 +160,10 @@ (defcustom smerge-command-prefix "\C-c^" "Prefix for `smerge-mode' commands." :group 'smerge - :type '(choice (string "\e") (string "\C-c^") (string "") string)) + :type '(choice (const :tag "ESC" "\e") + (const :tag "C-c ^" "\C-c^" ) + (const :tag "none" "") + string)) (easy-mmode-defmap smerge-mode-map `((,smerge-command-prefix . ,smerge-basic-map)) --8<---------------cut here---------------end--------------->8--- ... so that we get: ,----[ M-x customize-variable RET smerge-command-prefix RET ] | Smerge Command Prefix: [Hide Value] [Value Menu] C-c ^ | [State]: STANDARD. | Prefix for `smerge-mode' commands. | -UUU:**--F1 *Customize Option: Smerge Command Prefix* (Custom)---- | Available choices: | | 0 = ESC | 1 = C-c ^ | 2 = none | 3 = String `---- Bye, Reiner. -- ,,, (o o) ---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/ From jihyun.jo at gmail.com Thu May 8 09:41:07 2008 From: jihyun.jo at gmail.com (Jihyun Cho) Date: Fri, 9 May 2008 01:41:07 +0900 Subject: bug#37: hangul.el - new korean-hangul module In-Reply-To: References: <6bc6bb380803020605h2b6ff241h3085564fa7b3c8dc@mail.gmail.com> <85bq5s3v0x.fsf@lola.goethe.zz> <6bc6bb380804030826k4a82e242hfd6a1fbc6951ac7f@mail.gmail.com> <6bc6bb380804190329k44a332bcua279da080cb8e6ee@mail.gmail.com> <6bc6bb380804240942h1b755fe2t71a8eab1abb4e508@mail.gmail.com> Message-ID: <9d644d9b0805080941n273e7396oa7c7f8333f30fb80@mail.gmail.com> Hi. I have made a improved patch. The patch file is big. Because it contains hanja and symbol table. Therefore, it can input not only hangul but also hanja and symbol. I've posted the patch file : http://pds9.egloos.com/pds/200805/09/75/emacs-korean-hangul-patch.diff From offby1 at blarg.net Thu May 8 20:51:48 2008 From: offby1 at blarg.net (Eric Hanchrow) Date: Thu, 08 May 2008 20:51:48 -0700 Subject: bug#206: 23.0.60; crash in make-frame-on-display Message-ID: <87ej8cjfsb.fsf@offby1.atm01.sea.blarg.net> Please describe exactly what actions triggered the bug and the precise symptoms of the bug: Unfortunately, I don't know what I did exactly. Here's what I remember: * I started emacs with "-Q -nw", but couldn't reproduce the problem so I loaded my rather large and complex init file. * I did M-x make-frame-on-display RET :0 RET a few times; from the new X frame, I also did C-x 5 2 a few times. I'm pretty sure that I changed the font in one of those frames. Here's the backtrace: #0 abort () at emacs.c:430 No locals. #1 0x081cdb2b in font_merge_old_spec (name=137780505, family=137807457, registry=137780505, spec=138025180) at font.c:1582 len = p0 = p1 = #2 0x081ce7a7 in font_find_for_lface (f=0x928e0c8, lface=0x87b9d4c, spec=137780505, c=-1) at font.c:2684 frame = 153673932 entities = val = 137780505 i = result = #3 0x081ce9c4 in font_load_for_face (f=0x928e0c8, face=0x87b9d00) at font.c:2812 entity = font_object = 137780505 #4 0x080d0c90 in realize_face (cache=0x92c5fe8, attrs=0xbf9271f4, former_face_id=) at xfaces.c:7755 face = (struct face *) 0x87b9d00 #5 0x080d13be in realize_named_face (f=0x928e0c8, symbol=137812417, id=1) at xfaces.c:7597 c = (struct face_cache *) 0x92c5fe8 lface = attrs = {137780841, 137807457, 137807457, 736, 137807457, 137807457, 137780505, 137780553, 140756859, 154180611, 137780505, 137780505, 137780505, 137780505, 137780505, 137780505, 56, 154148795} symbol_attrs = {137780841, 137807457, 137807457, 137807457, 137807457, 137807457, 137807457, 137780553, 140756859, 137807457, 137807457, 137807457, 137807457, 137807457, 137807457, 137807457, 137807457, 137807457} #6 0x080d1568 in realize_basic_faces (f=0x928e0c8) at xfaces.c:7392 success_p = 1 #7 0x080d3a44 in recompute_basic_faces (f=0x928e0c8) at xfaces.c:961 No locals. #8 0x0807ed1d in init_iterator (it=0xbf927354, w=0x92d28c0, charpos=1, bytepos=1, row=0x0, base_face_id=DEFAULT_FACE_ID) at xdisp.c:2561 No locals. #9 0x080854fd in resize_mini_window (w=0x92d28c0, exact_p=1) at xdisp.c:8534 total_height = 40 max_height = unit = 13 old_current_buffer = (struct buffer *) 0x91786a0 it = { window = 153954500, w = 0x92d28c0, f = 0x928e0c8, method = GET_FROM_BUFFER, stop_charpos = 0, end_charpos = 0, s = 0x0, string_nchars = 0, region_beg_charpos = 0, region_end_charpos = 0, redisplay_end_trigger_charpos = 0, multibyte_p = 0, header_line_p = 0, string_from_display_prop_p = 0, ellipsis_p = 0, dp = 0x0, dpvec = 0x0, dpend = 0x0, dpvec_char_len = 0, dpvec_face_id = 0, saved_face_id = 0, ctl_chars = {0 }, start = { pos = { charpos = 0, bytepos = 0 }, overlay_string_index = 0, string_pos = { charpos = 0, bytepos = 0 }, dpvec_index = 0 }, current = { pos = { charpos = 0, bytepos = 0 }, overlay_string_index = -1, string_pos = { charpos = -1, bytepos = -1 }, dpvec_index = -1 }, n_overlay_strings = 0, overlay_strings = {0 }, string_overlays = {0 }, string = 137780505, from_overlay = 0, stack = {{ string = 0, string_nchars = 0, end_charpos = 0, stop_charpos = 0, face_id = 0, u = { image = { object = 0, slice = { x = 0, y = 0, width = 0, height = 0 }, image_id = 0 }, comp = { object = 0, c = 0, len = 0, cmp_id = 0, cmp_len = 0 }, stretch = { object = 0 } }, position = { charpos = 0, bytepos = 0 }, current = { pos = { charpos = 0, bytepos = 0 }, overlay_string_index = 0, string_pos = { charpos = 0, bytepos = 0 }, dpvec_index = 0 }, from_overlay = 0, area = LEFT_MARGIN_AREA, method = GET_FROM_BUFFER, multibyte_p = 0, string_from_display_prop_p = 0, display_ellipsis_p = 0, space_width = 0, font_height = 0, voffset = 0 }, { string = 0, string_nchars = 0, end_charpos = 0, stop_charpos = 0, face_id = 0, u = { image = { object = 0, slice = { x = 0, y = 0, width = 0, height = 0 }, image_id = 0 }, comp = { object = 0, c = 0, len = 0, cmp_id = 0, cmp_len = 0 }, stretch = { object = 0 } }, position = { charpos = 0, bytepos = 0 }, current = { pos = { charpos = 0, bytepos = 0 }, overlay_string_index = 0, string_pos = { charpos = 0, bytepos = 0 }, dpvec_index = 0 }, from_overlay = 0, area = LEFT_MARGIN_AREA, method = GET_FROM_BUFFER, multibyte_p = 0, string_from_display_prop_p = 0, display_ellipsis_p = 0, space_width = 0, font_height = 0, voffset = 0 }, { string = 0, string_nchars = 0, end_charpos = 0, stop_charpos = 0, face_id = 0, u = { image = { object = 0, slice = { x = 0, y = 0, width = 0, height = 0 }, image_id = 0 }, comp = { object = 0, c = 0, len = 0, cmp_id = 0, cmp_len = 0 }, stretch = { object = 0 } }, position = { charpos = 0, bytepos = 0 }, current = { pos = { charpos = 0, bytepos = 0 }, overlay_string_index = 0, string_pos = { charpos = 0, bytepos = 0 }, dpvec_index = 0 }, from_overlay = 0, area = LEFT_MARGIN_AREA, method = GET_FROM_BUFFER, multibyte_p = 0, string_from_display_prop_p = 0, display_ellipsis_p = 0, space_width = 0, font_height = 0, voffset = 0 }, { string = 0, string_nchars = 0, end_charpos = 0, stop_charpos = 0, face_id = 0, u = { image = { object = 0, slice = { x = 0, y = 0, width = 0, height = 0 }, image_id = 0 }, comp = { object = 0, c = 0, len = 0, cmp_id = 0, cmp_len = 0 }, stretch = { object = 0 } }, position = { charpos = 0, bytepos = 0 }, current = { pos = { charpos = 0, bytepos = 0 }, overlay_string_index = 0, string_pos = { charpos = 0, bytepos = 0 }, dpvec_index = 0 }, from_overlay = 0, area = LEFT_MARGIN_AREA, method = GET_FROM_BUFFER, multibyte_p = 0, string_from_display_prop_p = 0, display_ellipsis_p = 0, space_width = 0, font_height = 0, voffset = 0 }}, sp = 0, selective = 0, what = IT_CHARACTER, face_id = 0, selective_display_ellipsis_p = 0, ctl_arrow_p = 0, truncate_lines_p = 0, face_box_p = 0, start_of_box_run_p = 0, end_of_box_run_p = 0, overlay_strings_at_end_processed_p = 0, ignore_overlay_strings_at_pos_p = 0, glyph_not_available_p = 0, starts_in_middle_of_char_p = 0, face_before_selective_p = 0, constrain_row_ascent_descent_p = 0, base_face_id = 0, c = 0, len = 0, cmp_id = 0, cmp_len = 0, char_to_display = 0, image_id = 0, slice = { x = 0, y = 0, width = 0, height = 0 }, space_width = 0, voffset = 0, font_height = 0, object = 0, position = { charpos = 0, bytepos = 0 }, tab_width = 0, truncation_pixel_width = 0, continuation_pixel_width = 0, first_visible_x = 0, last_visible_x = 0, last_visible_y = 0, extra_line_spacing = 0, max_extra_line_spacing = 0, override_ascent = 0, override_descent = 0, override_boff = 0, glyph_row = 0x0, area = LEFT_MARGIN_AREA, nglyphs = 0, pixel_width = 0, ascent = 0, descent = 0, max_ascent = 0, max_descent = 0, phys_ascent = 0, phys_descent = 0, max_phys_ascent = 0, max_phys_descent = 0, current_x = 0, continuation_lines_width = 0, current_y = 0, first_vpos = 0, vpos = 0, hpos = 0, left_user_fringe_bitmap = 0, right_user_fringe_bitmap = 0, left_user_fringe_face_id = 0, right_user_fringe_face_id = 0 } height = f = (struct frame *) 0x928e0c8 window_height_changed_p = 0 #10 0x08062f12 in do_switch_frame (frame=137910404, track=1, for_deletion=0) at frame.c:870 No locals. #11 0x08063791 in Fselect_frame (frame=137910404) at frame.c:912 No locals. #12 0x0817f9fd in unbind_to (count=288, value=137780505) at eval.c:3387 quitf = 137780505 #13 0x08097568 in run_window_configuration_change_hook (f=0x928e0c8) at window.c:3351 frame = 153673932 global_wcch = 137780505 #14 0x0805d63a in change_frame_size_1 (f=0x928e0c8, newheight=40, newwidth=80, pretend=1, delay=0, safe=0) at dispnew.c:6395 new_frame_total_cols = #15 0x080eca9c in Fx_create_frame (parms=142152773) at xfns.c:3590 f = (struct frame *) 0x928e0c8 frame = 153673932 tem = name = 137780529 minibuffer_only = 0 width = 137807457 height = 137807457 display = dpyinfo = (struct x_display_info *) 0x880d240 parent = 137780505 kb = (struct kboard *) 0x9275910 #16 0x08181c9f in Ffuncall (nargs=2, args=0xbf927914) at eval.c:3032 fun = original_fun = funcar = numargs = 1 val = backtrace = { next = 0xbf927a04, function = 0xbf927914, args = 0xbf927918, nargs = 1, evalargs = 0 '\0', debug_on_exit = 0 '\0' } internal_args = (Lisp_Object *) 0xbf927918 i = #17 0x081abbcc in Fbyte_code (bytestr=136473883, vector=136473900, maxdepth=) at bytecode.c:679 op = 137807457 vectorp = (Lisp_Object *) 0x8226d30 stack = { pc = 0x82f5b43 "\310\031\032\033\311\216\312\n!\210\313\n\b\"\210\314\n!\210\315\n!\210\316\n!\210\v\2042", top = 0xbf927918, bottom = 0xbf927910, byte_string = 136473883, byte_string_start = 0x82f5b37 "\304\b!\020\305\b\236\306\307\bB!\310\031\032\033\311\216\312\n!\210\313\n\b\"\210\314\n!\210\315\n!\210\316\n!\210\v\2042", constants = 136473900, next = 0xbf927a8c } top = (Lisp_Object *) 0xbf927914 result = #18 0x081815d4 in funcall_lambda (fun=136473836, nargs=1, arg_vector=0xbf927a44) at eval.c:3219 val = syms_left = next = i = 1 optional = 1 rest = 0 #19 0x08181a1b in Ffuncall (nargs=2, args=0xbf927a40) at eval.c:3089 fun = 136473836 original_fun = 142955593 funcar = numargs = 1 val = backtrace = { next = 0xbf927b44, function = 0xbf927a40, args = 0xbf927a44, nargs = 1, evalargs = 0 '\0', debug_on_exit = 0 '\0' } internal_args = (Lisp_Object *) 0xbf927a44 i = #20 0x081abbcc in Fbyte_code (bytestr=136740691, vector=136740708, maxdepth=) at bytecode.c:679 op = 137807457 vectorp = (Lisp_Object *) 0x8267f68 stack = { pc = 0x82c98ec "\026\027\321\016\027!\210\016\031\311\036\032\211\036\033\203\232", top = 0xbf927a44, bottom = 0xbf927a40, byte_string = 136740691, byte_string_start = 0x82c988e "\306\b\236\203,", constants = 136740708, next = 0xbf927bbc } top = (Lisp_Object *) 0xbf927a40 result = #21 0x081815d4 in funcall_lambda (fun=136740644, nargs=1, arg_vector=0xbf927b84) at eval.c:3219 val = syms_left = next = i = 1 optional = 1 rest = 0 #22 0x08181a1b in Ffuncall (nargs=2, args=0xbf927b80) at eval.c:3089 fun = 136740644 original_fun = 143642449 funcar = numargs = 1 val = backtrace = { next = 0xbf927cdc, function = 0xbf927b80, args = 0xbf927b84, nargs = 1, evalargs = 0 '\0', debug_on_exit = 0 '\0' } internal_args = (Lisp_Object *) 0xbf927b84 i = #23 0x081abbcc in Fbyte_code (bytestr=136739435, vector=136739452, maxdepth=) at bytecode.c:679 op = 137807457 vectorp = (Lisp_Object *) 0x8267a80 stack = { pc = 0x82c9ba2 "\207", top = 0xbf927b84, bottom = 0xbf927b80, byte_string = 136739435, byte_string_start = 0x82c9b7f "\304\305\b\"\204\v", constants = 136739452, next = 0xbf927ddc } top = (Lisp_Object *) 0xbf927b80 result = #24 0x081815d4 in funcall_lambda (fun=136739380, nargs=1, arg_vector=0xbf927c40) at eval.c:3219 val = syms_left = next = i = 1 optional = 1 rest = 0 #25 0x081817e0 in apply_lambda (fun=136739380, args=148042821, eval_flag=1) at eval.c:3143 args_left = 137780505 arg_vector = (Lisp_Object *) 0x836c661 i = 1 tem = 155291251 #26 0x08180e77 in Feval (form=148042837) at eval.c:2423 fun = 137807457 val = original_fun = 147597857 original_args = 148042821 funcar = 137807457 backtrace = { next = 0xbf927d54, function = 0xbf927cf4, args = 0xbf927c40, nargs = 1, evalargs = 0 '\0', debug_on_exit = 0 '\0' } #27 0x08181c9f in Ffuncall (nargs=2, args=0xbf927d90) at eval.c:3032 fun = original_fun = funcar = numargs = 1 val = backtrace = { next = 0xbf927e94, function = 0xbf927d90, args = 0xbf927d94, nargs = 1, evalargs = 0 '\0', debug_on_exit = 0 '\0' } internal_args = (Lisp_Object *) 0xbf927d94 i = #28 0x081abbcc in Fbyte_code (bytestr=136592187, vector=136592204, maxdepth=) at bytecode.c:679 op = 137807457 vectorp = (Lisp_Object *) 0x8243b50 stack = { pc = 0x82df52e "\202C", top = 0xbf927d94, bottom = 0xbf927d90, byte_string = 136592187, byte_string_start = 0x82df4fc "\bS\t8\306\032\211\033\2035", constants = 136592204, next = 0x0 } top = (Lisp_Object *) 0xbf927d90 result = #29 0x081815d4 in funcall_lambda (fun=136592148, nargs=1, arg_vector=0xbf927f24) at eval.c:3219 val = syms_left = next = i = 1 optional = 0 rest = 0 #30 0x08181a1b in Ffuncall (nargs=2, args=0xbf927f20) at eval.c:3089 fun = 136592148 original_fun = 142967801 funcar = numargs = 1 val = backtrace = { next = 0xbf9280a4, function = 0xbf927f20, args = 0xbf927f24, nargs = 1, evalargs = 0 '\0', debug_on_exit = 0 '\0' } internal_args = (Lisp_Object *) 0xbf927f24 i = #31 0x0817eda1 in Fcall_interactively (function=142967801, record_flag=137780505, keys=137818892) at callint.c:859 val = args = (Lisp_Object *) 0xbf927f20 visargs = (Lisp_Object *) 0xbf927f00 specs = 137780505 filter_specs = teml = up_event = 137780505 enable = 137780505 next_event = 3 prefix_arg = 137780505 string = tem = (unsigned char *) 0x81e86ca "" varies = (int *) 0xbf927ee0 i = 1 j = 1 foo = prompt1 = '\0' arg_from_tty = 0 key_count = 3 record_then_fail = 0 save_this_command = 142967801 save_last_command = 137815785 save_this_original_command = 142967801 save_real_this_command = 142967801 #32 0x08181c74 in Ffuncall (nargs=4, args=0xbf9280e0) at eval.c:3038 fun = original_fun = funcar = numargs = 3 val = backtrace = { next = 0x0, function = 0xbf9280e0, args = 0xbf9280e4, nargs = 3, evalargs = 0 '\0', debug_on_exit = 0 '\0' } internal_args = (Lisp_Object *) 0xbf9280e4 i = #33 0x08181dc9 in call3 (fn=137943225, arg1=142967801, arg2=137780505, arg3=137780505) at eval.c:2862 ret_ungc_val = 1 #34 0x0812861e in command_loop_1 () at keyboard.c:1912 cmd = lose = nonundocount = 0 keybuf = {192, 216, 216, 0 , -1080917644, -1080917808, 0, -65536, 137780505, 143183977, -16121856, 0, 138291128, 138291112, -1080917608} i = prev_modiff = 21 prev_buffer = (struct buffer *) 0x91786a0 already_adjusted = 0 #35 0x081804f0 in internal_condition_case (bfun=0x81282c0 , handlers=137823649, hfun=0x8123240 ) at eval.c:1501 val = c = { tag = 137780505, val = 137780505, next = 0xbf9282c0, gcpro = 0x0, jmp = {{ __jmpbuf = {0, 138291128, 138291112, -1080917368, 822296705, 604595182}, __mask_was_saved = 0, __saved_mask = { __val = {3075967772, 3214016514, 3086770777, 134542761, 3078711868, 3086823412, 3214049504, 3071288540, 3214049556, 3086749785, 146994816, 3214049492, 3077275636, 146994816, 3086808508, 3214049504, 3214049760, 3214049856, 3214050144, 4294967295, 3214049992, 135465443, 3214050144, 3214049856, 128, 0, 0, 0, 0, 0, 0, 0} } }}, backlist = 0x0, handlerlist = 0x0, lisp_eval_depth = 0, pdlcount = 2, poll_suppress_count = 1, interrupt_input_blocked = 0, byte_stack = 0x0 } h = { handler = 137823649, var = 137780505, chosen_clause = 0, tag = 0xbf9281ac, next = 0x0 } #36 0x08122653 in command_loop_2 () at keyboard.c:1369 val = 1 #37 0x081805ca in internal_catch (tag=137819625, func=0x8122630 , arg=137780505) at eval.c:1237 c = { tag = 137819625, val = 137780505, next = 0x0, gcpro = 0x0, jmp = {{ __jmpbuf = {0, 138291128, 138291112, -1080917112, 822435969, 604732398}, __mask_was_saved = 0, __saved_mask = { __val = {0, 0, 0, 0, 0, 0, 0, 3076361617, 0, 0, 0, 0, 0, 0, 0, 145793768, 3077153525, 0, 3077280144, 0, 138006618, 138006616, 138009856, 3214050168, 135732837, 138009857, 138006618, 137780505, 137806352, 0, 0, 137780529} } }}, backlist = 0x0, handlerlist = 0x0, lisp_eval_depth = 0, pdlcount = 2, poll_suppress_count = 1, interrupt_input_blocked = 0, byte_stack = 0x0 } #38 0x081230a7 in command_loop () at keyboard.c:1348 No locals. #39 0x0812341b in recursive_edit_1 () at keyboard.c:957 val = #40 0x08123551 in Frecursive_edit () at keyboard.c:1019 buffer = 137780505 #41 0x08118142 in main (argc=3, argv=0xbf928794) at emacs.c:1784 dummy = 0 stack_bottom_variable = 8 '\b' do_initial_setlocale = 1 skip_args = 1 rlim = { rlim_cur = 8388608, rlim_max = 18446744073709551615 } no_loadup = 0 junk = 0x0 Lisp Backtrace: "x-create-frame" (0xbf927918) "x-create-frame-with-faces" (0xbf927a44) "make-frame" (0xbf927b84) "make-frame-on-display" (0xbf927c40) "eval" (0xbf927d94) "repeat-complex-command" (0xbf927f24) "call-interactively" (0xbf9280e4) "x-create-frame" (0xbf927918) "x-create-frame-with-faces" (0xbf927a44) "make-frame" (0xbf927b84) "make-frame-on-display" (0xbf927c40) "eval" (0xbf927d94) "repeat-complex-command" (0xbf927f24) "call-interactively" (0xbf9280e4) In GNU Emacs 23.0.60.1 (i686-pc-linux-gnu, GTK+ Version 2.12.9) of 2008-05-08 on debian configured using `configure '--enable-maintainer-mode' '--with-xpm=no' '--with-jpeg=no' '--with-gif=no' '--with-tiff=no' '--with-xft' '--with-x-toolkit=gtk'' Important settings: value of $LC_ALL: nil value of $LC_COLLATE: nil value of $LC_CTYPE: nil value of $LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC: nil value of $LC_TIME: nil value of $LANG: nil value of $XMODIFIERS: nil locale-coding-system: utf-8-unix default-enable-multibyte-characters: t Major mode: Text Minor modes in effect: erc-ring-mode: t erc-pcomplete-mode: t erc-netsplit-mode: t erc-button-mode: t erc-fill-mode: t erc-stamp-mode: t erc-autojoin-mode: t erc-track-mode: t erc-track-minor-mode: t erc-match-mode: t erc-log-mode: t erc-services-mode: t erc-irccontrols-mode: t erc-noncommands-mode: t erc-readonly-mode: t desktop-save-mode: t recentf-mode: t display-time-mode: t global-auto-revert-mode: t shell-dirtrack-mode: t iswitchb-mode: t mouse-wheel-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t global-auto-composition-mode: t auto-composition-mode: t auto-encryption-mode: t auto-compression-mode: t line-number-mode: t transient-mark-mode: t Recent input: a s SPC i n SPC M o n t r e a l SPC - - SPC w h i c h , SPC a l a s , SPC w a s SPC y e a r s SPC a g o SPC - - SPC I SPC h a d SPC a SPC d e l i g h t f u l SPC m e a l SPC a t SPC e i t h e r SPC a SPC P o l i s h SPC o r SPC R u s s i a n SPC p l a c e . RET l o v e SPC t o SPC g o SPC b a c k , SPC b u t SPC i t ' s SPC p r e t t y SPC f a r SPC : ) _ DEL DEL | RET C-c C-@ C-c C-@ y o u ' d SPC t h i n k SPC i t SPC w o u l d , SPC b u t SPC . . . RET C-c C-@ n u DEL DEL C-x b e m RET n u t s , SPC t h e SPC " e m a c s SPC - Q SPC - n w " SPC i s SPC w o r k i n g SPC f i n e . RET C-h i d m g d b RET i l o g RET , , C-x C-f / u s r / l o c TAB s r TAB e m TAB v TAB s r TAB RET s ESC < n n RET C-v C-v ESC < ESC x r e p o r t TAB b TAB RET Recent messages: uncompressing gdb.info-3.gz...done uncompressing gdb.info-4.gz...done uncompressing gdb.info-4.gz...done uncompressing gdb.info-4.gz...done uncompressing gdb.info-2.gz...done Found `ADP (Angel Debugger Protocol) logging' in Index. (9 total; use `,' for next) Found `log output in GDB/MI' in Index. (9 total; use `,' for next) uncompressing gdb.info-1.gz...done Found `logging file name' in Index. (9 total; use `,' for next) Mark set [2 times] -- It has been suggested that this article or section be merged into Fried dough. (Discuss) -- Seen on Wikipedia From don at donarmstrong.com Fri May 9 01:25:05 2008 From: don at donarmstrong.com (Emacs bug Tracking System) Date: Fri, 9 May 2008 01:25:05 -0700 Subject: bug#191: marked as done (23.0.60; vc (CVS backend): vc-directory is broken) References: <87wsm9rokv.fsf@leeloo.anubex.internal> Message-ID: Your message dated Fri, 9 May 2008 10:15:32 +0200 with message-id and subject line Fixed by recent VC changes has caused the Emacs bug report #191, regarding 23.0.60; vc (CVS backend): vc-directory is broken to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact don at donarmstrong.com immediately.) -- 191: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=191 Emacs Bug Tracking System Contact don at donarmstrong.com with problems -------------- next part -------------- An embedded message was scrubbed... From: Tim Van Holder Subject: 23.0.60; vc (CVS backend): vc-directory is broken Date: Mon, 05 May 2008 13:13:20 +0200 Size: 13174 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080509/e73dd112/attachment.eml -------------- next part -------------- An embedded message was scrubbed... From: "Tim Van Holder" Subject: Fixed by recent VC changes Date: Fri, 9 May 2008 10:15:32 +0200 Size: 2109 Url: http://lists.donarmstrong.com/pipermail/emacsbugs/attachments/20080509/e73dd112/attachment-0001.eml From lekktu at gmail.com Fri May 9 06:52:45 2008 From: lekktu at gmail.com (Juanma Barranquero) Date: Fri, 9 May 2008 15:52:45 +0200 Subject: bug#207: Next release In-Reply-To: References: <18457.37369.262079.668907@kahikatea.snap.net.nz> <4822B82A.6030003@gnu.org> <86zlr1qjq3.fsf@lola.quinscape.zz> Message-ID: > What for? Just to help catching errors. I'm a functional programming fan, I like inmutable objects. > char-tables have inheritance, so I don't see what more we need for > display-tables. (let ((global (make-display-table)) (local (make-display-table))) (set-char-table-parent local global) (aset global ?0 [?< ?0 ?>]) (aset local ?1 [?< ?1 ?>]) (setq standard-display-table global) (setq buffer-display-table local) (insert "01")) => 0<1> That is, local's parent is global, but once local is set as buffer-local display table, global's contents is irrelevant when viewing the buffer. That limits the usefulness of display tables. Or am I missing something? Juanma From drew.adams at oracle.com Fri May 9 08:44:29 2008 From: drew.adams at oracle.com (Drew Adams) Date: Fri, 9 May 2008 08:44:29 -0700 Subject: bug#208: 23.0.60; `l' in Info skips last visited node Message-ID: <000301c8b1eb$91f6f150$0200a8c0@us.oracle.com> emacs -Q C-h i, choose Elisp manual. g Customization Types m d TAB RET, to go to node Defining New Types SPC SPC to get to node Loading l This takes you back to node Customization, not to the last visited node, which is Defining New Types, or even to the node visited just before that, which is Customization Types. Node Customization is the grandparent of the last visited node, and it was never even visited. This behavior contradicts what a user expects, which is a strict chronological navigation, unrelated to the hierarchical manual organization. It also contradicts what the doc of `l' says it is supposed to do: "Go back in the history to the last node visited." Likewise, the Info tutorial says this about `l': "`l' command (`l' for "last") will do that, one node-step at a time. As you move from node to node, Info records the nodes where you have been in a special history list. The `l' command revisits nodes in the history list; each successive `l' command moves one step back through the history." `l' is not in fact moving one step through the history list. In fact, it is even moving to nodes that are not on the history list (never visited). The doc is not wrong about what `l' should do; it is the actual behavior that is wrong. `l' should act like the `Back' button of a Web browser; it should totally ignore book structure and stick to the navigation history. In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600) of 2008-05-04 on LENNART-69DE564 Windowing system distributor `Microsoft Corp.', version 5.1.2600 configured using `configure --with-gcc (3.4) --no-opt --cflags -Ic:/g/include -fno-crossjumping' From eric.hanchrow at gmail.com Fri May 9 11:27:16 2008 From: eric.hanchrow at gmail.com (Eric Hanchrow) Date: Fri, 9 May 2008 11:27:16 -0700 Subject: bug#209: 23.0.60; clicking on mode-line coding system indicator "M" causes crash Message-ID: <36366a980805091127m49c60a33s2338e70f2251eff8@mail.gmail.com> Please write in English if possible, because the Emacs maintainers usually do not have translators to read other languages for them. Your bug report will be posted to the emacs-pretest-bug at gnu.org mailing list. Please describe exactly what actions triggered the bug and the precise symptoms of the bug: I visited my ~/.abbrev_defs file, and noted that the coding system indicator in the mode line was "M". I didn't know what that meant, so I clicked on it. Kaboom. Breakpoint 1, abort () at emacs.c:430 430 kill (getpid (), SIGABRT); #0 abort () at emacs.c:430 No locals. #1 0x081cdb2b in font_merge_old_spec (name=137780505, family=137807457, registry=137780505, spec=138025180) at font.c:1582 len = p0 = p1 = #2 0x081ce7a7 in font_find_for_lface (f=0x9335a40, lface=0x9076434, spec=137780505, c=-1) at font.c:2684 frame = 154360388 entities = val = 137780505 i = result = #3 0x081ce9c4 in font_load_for_face (f=0x9335a40, face=0x90763e8) at font.c:2812 entity = font_object = 137780505 #4 0x080d0c90 in realize_face (cache=0x933ccc0, attrs=0xbfe33314, former_face_id=) at xfaces.c:7755 face = (struct face *) 0x90763e8 #5 0x080d13be in realize_named_face (f=0x9335a40, symbol=137812417, id=1) at xfaces.c:7597 c = (struct face_cache *) 0x933ccc0 lface = attrs = {137780841, 137807457, 137807457, 968, 137807457, 137807457, 137780505, 137780505, 151551979, 137944099, 137780505, 137780505, 137780505, 138342461, 137780505, 137780505, 56, 152426651} symbol_attrs = {137780841, 137807457, 137807457, 137807457, 137807457, 137807457, 137807457, 137807457, 151551979, 137944099, 137807457, 137807457, 137807457, 138342461, 137807457, 137807457, 137807457, 137807457} #6 0x080d1568 in realize_basic_faces (f=0x9335a40) at xfaces.c:7392 success_p = 1 #7 0x080d27e5 in Fdisplay_supports_face_attributes_p (attributes=147618653, display=154360388) at xfaces.c:6637 frame = 154360388 def_face = (struct face *) 0xbfe339b8 attrs = {137807457, 137807457, 137807457, 137807457, 137807457, 137807145, 137807457 } #8 0x08181c8d in Ffuncall (nargs=3, args=0xbfe33580) at eval.c:3035 fun = original_fun = funcar = numargs = 2 val = backtrace = { next = 0xbfe33684, function = 0xbfe33580, args = 0xbfe33584, nargs = 2, evalargs = 0 '\0', debug_on_exit = 0 '\0' } internal_args = (Lisp_Object *) 0xbfe33584 i = #9 0x081abbcc in Fbyte_code (bytestr=136468939, vector=136468956, maxdepth=) at bytecode.c:679 op = 137807457 vectorp = (Lisp_Object *) 0x82259e0 stack = { pc = 0x82f6635 "\202\302", top = 0xbfe33588, bottom = 0xbfe33580, byte_string = 136468939, byte_string_start = 0x82f657b "\b\031\306\211\032\033\306\034\307\035\t\307=\203\022", constants = 136468956, next = 0xbfe336fc } top = (Lisp_Object *) 0xbfe33580 result = #10 0x081815d4 in funcall_lambda (fun=136468892, nargs=2, arg_vector=0xbfe336c4) at eval.c:3219 val = syms_left = next = i = 2 optional = 0 rest = 0 #11 0x08181a1b in Ffuncall (nargs=3, args=0xbfe336c0) at eval.c:3089 fun = 136468892 original_fun = 143219409 funcar = numargs = 2 val = backtrace = { next = 0xbfe337b4, function = 0xbfe336c0, args = 0xbfe336c4, nargs = 2, evalargs = 0 '\0', debug_on_exit = 0 '\0' } internal_args = (Lisp_Object *) 0xbfe336c4 i = #12 0x081abbcc in Fbyte_code (bytestr=136469195, vector=136469212, maxdepth=) at bytecode.c:679 op = 137807457 vectorp = (Lisp_Object *) 0x8225ae0 stack = { pc = 0x82f6524 "\203L", top = 0xbfe336c8, bottom = 0xbfe336c0, byte_string = 136469195, byte_string_start = 0x82f64e0 "\b\204\a", constants = 136469212, next = 0xbfe3383c } top = (Lisp_Object *) 0xbfe336c0 result = #13 0x081815d4 in funcall_lambda (fun=136469140, nargs=2, arg_vector=0xbfe337f4) at eval.c:3219 val = syms_left = next = i = 2 optional = 1 rest = 0 #14 0x08181a1b in Ffuncall (nargs=3, args=0xbfe337f0) at eval.c:3089 fun = 136469140 original_fun = 143063505 funcar = numargs = 2 val = backtrace = { next = 0xbfe338f4, function = 0xbfe337f0, args = 0xbfe337f4, nargs = 2, evalargs = 0 '\0', debug_on_exit = 0 '\0' } internal_args = (Lisp_Object *) 0xbfe337f4 i = #15 0x081abbcc in Fbyte_code (bytestr=136469875, vector=136469892, maxdepth=) at bytecode.c:679 op = 137807457 vectorp = (Lisp_Object *) 0x8225d88 stack = { pc = 0x82f635a "\211\032\205h", top = 0xbfe337f8, bottom = 0xbfe337f0, byte_string = 136469875, byte_string_start = 0x82f6356 "\306\b\t\"\211\032\205h", constants = 136469892, next = 0xbfe3397c } top = (Lisp_Object *) 0xbfe337f0 result = #16 0x081815d4 in funcall_lambda (fun=136469820, nargs=3, arg_vector=0xbfe33934) at eval.c:3219 val = syms_left = next = i = 3 optional = 0 rest = 0 #17 0x08181a1b in Ffuncall (nargs=4, args=0xbfe33930) at eval.c:3089 fun = 136469820 original_fun = 143121009 funcar = numargs = 3 val = backtrace = { next = 0xbfe33a34, function = 0xbfe33930, args = 0xbfe33934, nargs = 3, evalargs = 0 '\0', debug_on_exit = 0 '\0' } internal_args = (Lisp_Object *) 0xbfe33934 i = #18 0x081abbcc in Fbyte_code (bytestr=136469723, vector=136469740, maxdepth=) at bytecode.c:679 op = 137807457 vectorp = (Lisp_Object *) 0x8225cf0 stack = { pc = 0x82f63e7 "\210\314\n\315N!\211\033\316\034\211\035\203K", top = 0xbfe3393c, bottom = 0xbfe33930, byte_string = 136469723, byte_string_start = 0x82f63c1 "\306\b\t\"\210\b\307N\206\f", constants = 136469740, next = 0xbfe33aac } top = (Lisp_Object *) 0xbfe33930 result = #19 0x081815d4 in funcall_lambda (fun=136469676, nargs=2, arg_vector=0xbfe33a74) at eval.c:3219 val = syms_left = next = i = 2 optional = 0 rest = 0 #20 0x08181a1b in Ffuncall (nargs=3, args=0xbfe33a70) at eval.c:3089 fun = 136469676 original_fun = 143063673 funcar = numargs = 2 val = backtrace = { next = 0xbfe33b2c, function = 0xbfe33a70, args = 0xbfe33a74, nargs = 2, evalargs = 0 '\0', debug_on_exit = 0 '\0' } internal_args = (Lisp_Object *) 0xbfe33a74 i = #21 0x081abbcc in Fbyte_code (bytestr=136474579, vector=136474604, maxdepth=) at bytecode.c:679 op = 137807457 vectorp = (Lisp_Object *) 0x8226ff0 stack = { pc = 0x82f5a0b "\210\303\t!\304>\203\022", top = 0xbfe33a78, bottom = 0xbfe33a70, byte_string = 136474579, byte_string_start = 0x82f5a07 "\302\b\t\"\210\303\t!\304>\203\022", constants = 136474604, next = 0xbfe33ccc } top = (Lisp_Object *) 0xbfe33a70 result = #22 0x0818114c in Feval (form=136474565) at eval.c:2369 numargs = argvals = {136474579, 136474604, 24, -16121856, 137390919, -1075627200, 0, -1075627096} args_left = 137780505 i = 3 fun = val = original_fun = 137943033 original_args = 136474573 funcar = backtrace = { next = 0xbfe33d84, function = 0xbfe33b44, args = 0xbfe33b0c, nargs = 3, evalargs = 1 '\001', debug_on_exit = 0 '\0' } #23 0x0818370f in internal_lisp_condition_case (var=137780505, bodyform=136474565, handlers=136474677) at eval.c:1446 val = c = { tag = 137780505, val = 137780505, next = 0xbfe34048, gcpro = 0x0, jmp = {{ __jmpbuf = {137780505, -1075626896, 181, -1075626920, -763969407, 611111918}, __mask_was_saved = 0, __saved_mask = { __val = {0, 3219340264, 135796205, 368, 154119061, 24, 3219340412, 136455100, 23, 3219340264, 135832527, 154122149, 137780505, 0, 2, 3219340404, 1, 3219340376, 135797901, 137807529, 154119061, 3219340336, 3219340568, 4294967295, 3219340552, 3077361652, 3219340568, 3219340336, 3219340508, 137931864, 3219340336, 2} } }}, backlist = 0xbfe33d84, handlerlist = 0xbfe34110, lisp_eval_depth = 10, pdlcount = 25, poll_suppress_count = 1, interrupt_input_blocked = 0, byte_stack = 0xbfe33ccc } h = { handler = 136474677, var = 137780505, chosen_clause = -16121856, tag = 0xbfe33b78, next = 0xbfe34110 } #24 0x081ac520 in Fbyte_code (bytestr=136474187, vector=136474204, maxdepth=) at bytecode.c:869 handlers = body = 137807457 op = 137807457 vectorp = (Lisp_Object *) 0x8226e60 stack = { pc = 0x82f5add "\210\016\036A\211\026\036\204\265", top = 0xbfe33c70, bottom = 0xbfe33c70, byte_string = 136474187, byte_string_start = 0x82f5a1f "\b\204Q", constants = 136474204, next = 0xbfe33f7c } top = (Lisp_Object *) 0xbfe33c70 result = #25 0x081815d4 in funcall_lambda (fun=136474148, nargs=1, arg_vector=0xbfe33dc4) at eval.c:3219 val = syms_left = next = i = 1 optional = 0 rest = 0 #26 0x08181a1b in Ffuncall (nargs=2, args=0xbfe33dc0) at eval.c:3089 fun = 136474148 original_fun = 137981089 funcar = numargs = 1 val = backtrace = { next = 0xbfe33ef4, function = 0xbfe33dc0, args = 0xbfe33dc4, nargs = 1, evalargs = 0 '\0', debug_on_exit = 0 '\0' } internal_args = (Lisp_Object *) 0xbfe33dc4 i = #27 0x08182eb9 in call1 (fn=137981089, arg1=154360388) at eval.c:2817 ret_ungc_val = 1 #28 0x080e9633 in Fx_show_tip (string=152261491, frame=152254836, parms=139457421, timeout=80, dx=40, dy=160) at xfns.c:5184 f = (struct frame *) 0x9133970 w = root_x = root_y = old_buffer = pos = { charpos = 0, bytepos = 0 } i = width = height = old_windows_or_buffers_changed = 0 #29 0x08181bff in Ffuncall (nargs=7, args=0xbfe33f30) at eval.c:3051 fun = original_fun = funcar = numargs = 6 val = backtrace = { next = 0xbfe33ffc, function = 0xbfe33f30, args = 0xbfe33f34, nargs = 6, evalargs = 0 '\0', debug_on_exit = 0 '\0' } internal_args = (Lisp_Object *) 0xbfe33f34 i = #30 0x081abbcc in Fbyte_code (bytestr=136956123, vector=136956148, maxdepth=) at bytecode.c:679 op = 137807457 vectorp = (Lisp_Object *) 0x829c8f8 stack = { pc = 0x82abe69 "+\207", top = 0xbfe33f48, bottom = 0xbfe33f30, byte_string = 136956123, byte_string_start = 0x82abe2f "\306\b!\307\310\311\"\307\310\312\"\031\032\033\n;\203\037", constants = 136956148, next = 0xbfe3417c } top = (Lisp_Object *) 0xbfe33f30 result = #31 0x0818114c in Feval (form=136956109) at eval.c:2369 numargs = argvals = {136956123, 136956148, 56, 2, -1213609122, 137780480, -1075626656, -16121856} args_left = 137780505 i = 3 fun = val = original_fun = 137943033 original_args = 136956117 funcar = backtrace = { next = 0xbfe34234, function = 0xbfe34014, args = 0xbfe33fdc, nargs = 3, evalargs = 1 '\001', debug_on_exit = 0 '\0' } #32 0x0818370f in internal_lisp_condition_case (var=137823649, bodyform=136956109, handlers=136956253) at eval.c:1446 val = c = { tag = 137780505, val = 137780505, next = 0xbfe34728, gcpro = 0x0, jmp = {{ __jmpbuf = {137780505, -1075625664, 8, -1075625688, -763338623, 611111918}, __mask_was_saved = 0, __saved_mask = { __val = {140684184, 3081176608, 0, 0, 0, 0, 0, 268435456, 0, 3219341780, 3219341732, 3076447633, 0, 141065856, 16777216, 0, 147041856, 144143128, 146791832, 0, 147041856, 32, 2492, 1, 16, 0, 144143144, 0, 0, 0, 0, 0} } }}, backlist = 0xbfe34234, handlerlist = 0xbfe347f0, lisp_eval_depth = 7, pdlcount = 12, poll_suppress_count = 1, interrupt_input_blocked = 0, byte_stack = 0xbfe3417c } h = { handler = 136956253, var = 137823649, chosen_clause = 0, tag = 0xbfe34048, next = 0xbfe347f0 } #33 0x081ac520 in Fbyte_code (bytestr=136956059, vector=136956076, maxdepth=) at bytecode.c:869 handlers = body = 137807457 op = 137807457 vectorp = (Lisp_Object *) 0x829c8b0 stack = { pc = 0x82abe78 "\207", top = 0xbfe34140, bottom = 0xbfe34140, byte_string = 136956059, byte_string_start = 0x82abe6c "\b\203\b", constants = 136956076, next = 0xbfe342ac } top = (Lisp_Object *) 0xbfe34140 result = #34 0x081815d4 in funcall_lambda (fun=136956004, nargs=2, arg_vector=0xbfe34274) at eval.c:3219 val = syms_left = next = i = 2 optional = 1 rest = 0 #35 0x08181a1b in Ffuncall (nargs=3, args=0xbfe34270) at eval.c:3089 fun = 136956004 original_fun = 148316729 funcar = numargs = 2 val = backtrace = { next = 0xbfe34364, function = 0xbfe34270, args = 0xbfe34274, nargs = 2, evalargs = 0 '\0', debug_on_exit = 0 '\0' } internal_args = (Lisp_Object *) 0xbfe34274 i = #36 0x081abbcc in Fbyte_code (bytestr=136957627, vector=136957644, maxdepth=) at bytecode.c:679 op = 137807457 vectorp = (Lisp_Object *) 0x829ced0 stack = { pc = 0x82abbfc "\210\303\207", top = 0xbfe34278, bottom = 0xbfe34270, byte_string = 136957627, byte_string_start = 0x82abbf3 "\b;\205\v", constants = 136957644, next = 0xbfe3447c } top = (Lisp_Object *) 0xbfe34270 result = #37 0x081815d4 in funcall_lambda (fun=136957588, nargs=1, arg_vector=0xbfe34448) at eval.c:3219 val = syms_left = next = i = 1 optional = 0 rest = 0 #38 0x08181a1b in Ffuncall (nargs=2, args=0xbfe34444) at eval.c:3089 fun = 136957588 original_fun = 148316177 funcar = numargs = 1 val = backtrace = { next = 0xbfe34404, function = 0xbfe34444, args = 0xbfe34448, nargs = 1, evalargs = 0 '\0', debug_on_exit = 0 '\0' } internal_args = (Lisp_Object *) 0xbfe34448 i = #39 0x08183031 in run_hook_with_args (nargs=2, args=0xbfe34444, cond=until_success) at eval.c:2691 sym = 148316153 val = 137807457 ret = 137780505 globals = #40 0x08181d35 in Ffuncall (nargs=3, args=0xbfe34440) at eval.c:3013 fun = original_fun = 137920721 funcar = numargs = 2 val = backtrace = { next = 0xbfe34534, function = 0xbfe34440, args = 0xbfe34444, nargs = 2, evalargs = 0 '\0', debug_on_exit = 0 '\0' } internal_args = (Lisp_Object *) 0xbfe34444 i = #41 0x081abbcc in Fbyte_code (bytestr=136955819, vector=136955836, maxdepth=) at bytecode.c:679 op = 137807457 vectorp = (Lisp_Object *) 0x829c7c0 stack = { pc = 0x8306b47 "\207", top = 0xbfe34448, bottom = 0xbfe34440, byte_string = 136955819, byte_string_start = 0x8306b43 "\301\302\b\"\207", constants = 136955836, next = 0xbfe3465c } top = (Lisp_Object *) 0xbfe34440 result = #42 0x081815d4 in funcall_lambda (fun=136955780, nargs=1, arg_vector=0xbfe34628) at eval.c:3219 val = syms_left = next = i = 1 optional = 0 rest = 0 #43 0x08181a1b in Ffuncall (nargs=2, args=0xbfe34624) at eval.c:3089 fun = 136955780 original_fun = 148316681 funcar = numargs = 1 val = backtrace = { next = 0xbfe345e4, function = 0xbfe34624, args = 0xbfe34628, nargs = 1, evalargs = 0 '\0', debug_on_exit = 0 '\0' } internal_args = (Lisp_Object *) 0xbfe34628 i = #44 0x081833b9 in Fapply (nargs=2, args=0xbfe34624) at eval.c:2465 i = numargs = spread_arg = 139461144 funcall_args = fun = 148316681 #45 0x08181d35 in Ffuncall (nargs=3, args=0xbfe34620) at eval.c:3013 fun = original_fun = 137920649 funcar = numargs = 2 val = backtrace = { next = 0xbfe346dc, function = 0xbfe34620, args = 0xbfe34624, nargs = 2, evalargs = 0 '\0', debug_on_exit = 0 '\0' } internal_args = (Lisp_Object *) 0xbfe34624 i = #46 0x081abbcc in Fbyte_code (bytestr=136811963, vector=136811988, maxdepth=) at bytecode.c:679 op = 137807457 vectorp = (Lisp_Object *) 0x82795d8 stack = { pc = 0x82bf80e "\207", top = 0xbfe34628, bottom = 0xbfe34620, byte_string = 136811963, byte_string_start = 0x82bf806 "\301\b\302H\b\303H\"\207", constants = 136811988, next = 0xbfe3486c } top = (Lisp_Object *) 0xbfe34620 result = #47 0x0818114c in Feval (form=136811949) at eval.c:2369 numargs = argvals = {136811963, 136811988, 32, 137780505, 137099679, -1075624208, 31, -1075624104} args_left = 137780505 i = 3 fun = val = original_fun = 137943033 original_args = 136811957 funcar = backtrace = { next = 0xbfe34924, function = 0xbfe346f4, args = 0xbfe346bc, nargs = 3, evalargs = 1 '\001', debug_on_exit = 0 '\0' } #48 0x0818370f in internal_lisp_condition_case (var=137780505, bodyform=136811949, handlers=136812021) at eval.c:1446 val = c = { tag = 137780505, val = 137780505, next = 0xbfe3520c, gcpro = 0x0, jmp = {{ __jmpbuf = {137780505, -1075623904, 106, -1075623928, -762437503, 611111918}, __mask_was_saved = 0, __saved_mask = { __val = {1, 3219343256, 135796205, 128, 139460901, 32, 3219343396, 136811308, 8, 140479648, 4, 1, 0, 0, 136811308, 148203553, 1, 3219343368, 135797275, 137916936, 137918432, 3219343320, 135732837, 137918433, 137916938, 137780553, 149516048, 0, 28, 148203552, 137918432, 1} } }}, backlist = 0xbfe34924, handlerlist = 0xbfe352d4, lisp_eval_depth = 1, pdlcount = 8, poll_suppress_count = 1, interrupt_input_blocked = 0, byte_stack = 0xbfe3486c } h = { handler = 136812021, var = 137780505, chosen_clause = -16121856, tag = 0xbfe34728, next = 0xbfe352d4 } #49 0x081ac520 in Fbyte_code (bytestr=136811819, vector=136811836, maxdepth=) at bytecode.c:869 handlers = body = 137807457 op = 137807457 vectorp = (Lisp_Object *) 0x8279540 stack = { pc = 0x82bf87e "\210\016\026\205x", top = 0xbfe34820, bottom = 0xbfe34820, byte_string = 136811819, byte_string_start = 0x82bf810 "\b\021\n\020\v\022\306\034\307\v!\203|", constants = 136811836, next = 0x0 } top = (Lisp_Object *) 0xbfe34820 result = #50 0x081815d4 in funcall_lambda (fun=136811780, nargs=1, arg_vector=0xbfe34964) at eval.c:3219 val = syms_left = next = i = 1 optional = 0 rest = 0 #51 0x08181a1b in Ffuncall (nargs=2, args=0xbfe34960) at eval.c:3089 fun = 136811780 original_fun = 137813449 funcar = numargs = 1 val = backtrace = { next = 0x0, function = 0xbfe34960, args = 0xbfe34964, nargs = 1, evalargs = 0 '\0', debug_on_exit = 0 '\0' } internal_args = (Lisp_Object *) 0xbfe34964 i = #52 0x08182eb9 in call1 (fn=137813449, arg1=154246444) at eval.c:2817 ret_ungc_val = 1 #53 0x08120748 in timer_check (do_it_now=1) at keyboard.c:4658 old_deactivate_mark = 137780505 timer = idle_timer = now = { tv_sec = 1210357426, tv_usec = 608191 } timers = 153791901 idle_timers = 137780505 chosen_timer = 154246444 #54 0x08120949 in readable_events (flags=1) at keyboard.c:3648 No locals. #55 0x081209b7 in get_input_pending (addr=0x8351c58, flags=1) at keyboard.c:6952 No locals. #56 0x08120aa0 in detect_input_pending_run_timers (do_display=1) at keyboard.c:10632 old_timers_run = 147 #57 0x081b294a in wait_reading_process_output (time_limit=67, microsecs=0, read_kbd=-1, do_display=1, wait_for_cell=137780505, wait_proc=0x0, just_wait_proc=0) at process.c:4682 old_timers_run = 147 old_buffer = (struct buffer *) 0x8e96f10 old_window = 154194212 leave = timeout_reduced_for_timers = 1 channel = nfds = 0 Available = { fds_bits = {0 } } Connecting = { fds_bits = {0 } } check_connect = 0 check_delay = 1 no_avail = 0 xerrno = 11 proc = 36 timeout = { tv_sec = 0, tv_usec = 0 } end_time = { tv_sec = 1210357493, tv_usec = 355021 } wait_channel = -1 got_some_input = 0 #58 0x08057e86 in sit_for (timeout=536, reading=1, do_display=1) at dispnew.c:6614 sec = 67 usec = 0 #59 0x081252d6 in read_char (commandflag=1, nmaps=4, maps=0xbfe35040, prev_event=137780505, used_mouse_menu=0xbfe350d0, end_time=0x0) at keyboard.c:2932 tem0 = delay_level = 67 buffer_size = c = 137780505 local_getcjmp = {{ __jmpbuf = {140479680, 0, 4, -1075621896, -761560959, 814426094}, __mask_was_saved = 0, __saved_mask = { __val = {149516052, 3219345416, 135769428, 137809841, 8, 149516052, 3219345292, 0, 0, 4278845440, 1, 137780505, 3219345288, 3219345256, 135802929, 1, 3219345288, 137780553, 0, 1, 137813641, 153830536, 1, 3219345288, 1, 3219345304, 135803327, 137780505, 137780505, 4278845440, 142916721, 149516052} } }} save_jump = {{ __jmpbuf = {0, 0, 0, 0, 0, 0}, __mask_was_saved = 0, __saved_mask = { __val = {0 } } }} key_already_recorded = 0 tem = save = previous_echo_area_message = 137780505 also_record = 137780505 reread = 0 polling_stopped_here = orig_kboard = (struct kboard *) 0x8c4b7a0 #60 0x081264df in read_key_sequence (keybuf=0xbfe35174, bufsize=30, prompt=137780505, dont_downcase_last=0, can_return_switch_frame=1, fix_current_buffer=1) at keyboard.c:9441 interrupted_kboard = (KBOARD *) 0x8c4b7a0 key = 0 used_mouse_menu = 0 echo_local_start = 0 last_real_key_start = 0 keys_local_start = 0 local_first_binding = 0 from_string = 137780505 count = 2 t = 0 echo_start = 0 keys_start = 0 nmaps = 4 nmaps_allocated = 4 defs = (Lisp_Object * volatile) 0xbfe35020 submaps = (Lisp_Object * volatile) 0xbfe35040 orig_local_map = 137780505 orig_keymap = 137780505 localized_local_map = 0 first_binding = 0 first_unbound = 31 mock_input = 0 fkey = { parent = 143397661, map = 143397661, start = 0, end = 0 } keytran = { parent = 137773949, map = 137773949, start = 0, end = 0 } indec = { parent = 143397733, map = 143397733, start = 0, end = 0 } shift_translated = 0 delayed_switch_frame = 137780505 original_uppercase = 137780505 original_uppercase_position = -1 starting_buffer = (struct buffer *) 0x8e96f10 fake_prefixed_keys = 137780505 #61 0x08128467 in command_loop_1 () at keyboard.c:1653 cmd = lose = nonundocount = 0 keybuf = {192, 48, 135410158, 153686565, 137780553, -1075621450, 137780505, 0, 137780505, -1075621384, 135410421, 153686565, -1075621450, 1, 1006, -1223592592, -1224689016, 134543445, 0, -1075621420, -1075621584, 0, -1075642368, 137780505, 143119153, -16121856, 0, 138291120, 138291104, -16121856} i = prev_modiff = 288 prev_buffer = (struct buffer *) 0x91f5778 already_adjusted = 0 #62 0x081804f0 in internal_condition_case (bfun=0x81282c0 , handlers=137823649, hfun=0x8123240 ) at eval.c:1501 val = c = { tag = 137780505, val = 137780505, next = 0xbfe35320, gcpro = 0x0, jmp = {{ __jmpbuf = {0, 138291120, 138291104, -1075621144, -761003903, 604595182}, __mask_was_saved = 0, __saved_mask = { __val = {3076053788, 3219324930, 3086815833, 134542761, 3078797884, 3086868468, 3219345728, 3071374556, 3219345780, 3086794841, 147018424, 3219345716, 3077361652, 147018424, 3086853564, 3219345728, 3219345984, 3219346080, 3219346368, 4294967295, 3219346216, 135465443, 3219346368, 3076037532, 3078797960, 0, 4294967295, 3086868468, 134523132, 3086870120, 3219346160, 3086812201} } }}, backlist = 0x0, handlerlist = 0x0, lisp_eval_depth = 0, pdlcount = 2, poll_suppress_count = 1, interrupt_input_blocked = 0, byte_stack = 0x0 } h = { handler = 137823649, var = 137780505, chosen_clause = 137780553, tag = 0xbfe3520c, next = 0x0 } #63 0x08122653 in command_loop_2 () at keyboard.c:1369 val = 1 #64 0x081805ca in internal_catch (tag=137819625, func=0x8122630 , arg=137780505) at eval.c:1237 c = { tag = 137819625, val = 137780505, next = 0x0, gcpro = 0x0, jmp = {{ __jmpbuf = {0, 138291120, 138291104, -1075620888, -760864639, 604732398}, __mask_was_saved = 0, __saved_mask = { __val = {0, 0, 0, 0, 0, 0, 0, 3076447633, 0, 0, 0, 0, 0, 0, 0, 145164288, 3077239541, 0, 3077366160, 0, 138006618, 138006616, 138009856, 3219346392, 135732837, 138009857, 138006618, 137780505, 137806352, 0, 0, 137780529} } }}, backlist = 0x0, handlerlist = 0x0, lisp_eval_depth = 0, pdlcount = 2, poll_suppress_count = 1, interrupt_input_blocked = 0, byte_stack = 0x0 } #65 0x081230a7 in command_loop () at keyboard.c:1348 No locals. #66 0x0812341b in recursive_edit_1 () at keyboard.c:957 val = #67 0x08123551 in Frecursive_edit () at keyboard.c:1019 buffer = 137780505 #68 0x08118142 in main (argc=1, argv=0xbfe357f4) at emacs.c:1784 dummy = 0 stack_bottom_variable = 8 '\b' do_initial_setlocale = 1 skip_args = 0 rlim = { rlim_cur = 8388608, rlim_max = 18446744073709551615 } no_loadup = 0 junk = 0x0 Lisp Backtrace: "display-supports-face-attributes-p" (0xbfe33584) "face-spec-set-match-display" (0xbfe336c4) "face-spec-choose" (0xbfe337f4) "face-spec-set-2" (0xbfe33934) "face-spec-recalc" (0xbfe33a74) "byte-code" (0xbfe33b0c) "face-set-after-frame-default" (0xbfe33dc4) "x-show-tip" (0xbfe33f34) "byte-code" (0xbfe33fdc) "tooltip-show" (0xbfe34274) "tooltip-help-tips" (0xbfe34448) "run-hook-with-args-until-success" (0xbfe34444) "tooltip-timeout" (0xbfe34628) "apply" (0xbfe34624) "byte-code" (0xbfe346bc) "timer-event-handler" (0xbfe34964) The program being debugged has been started already. Start it from the beginning? (y or n) Starting program: /usr/local/src/emacs-via-git/src/emacs [Thread debugging using libthread_db enabled] [New Thread 0xb705f720 (LWP 25204)] If Emacs crashed, and you have the Emacs process in the gdb debugger, please include the output from the following gdb commands: `bt full' and `xbacktrace'. If you would like to further debug the crash, please read the file /usr/local/src/emacs-via-git/etc/DEBUG for instructions. In GNU Emacs 23.0.60.1 (i686-pc-linux-gnu, GTK+ Version 2.12.9) of 2008-05-09 on enver-laptop Windowing system distributor `The X.Org Foundation', version 11.0.10400090 configured using `configure '--enable-maintainer-mode' '--with-xpm=no' '--with-jpeg=no' '--with-gif=no' '--with-tiff=no' '--with-xft' '--with-x-toolkit=gtk'' Important settings: value of $LC_ALL: nil value of $LC_COLLATE: nil value of $LC_CTYPE: nil value of $LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC: nil value of $LC_TIME: nil value of $LANG: nil value of $XMODIFIERS: nil locale-coding-system: nil default-enable-multibyte-characters: t Major mode: Dired by name Minor modes in effect: erc-autojoin-mode: t erc-match-mode: t erc-log-mode: t erc-services-mode: t erc-networks-mode: t desktop-save-mode: t recentf-mode: t display-time-mode: t global-auto-revert-mode: t shell-dirtrack-mode: t iswitchb-mode: t tooltip-mode: t mouse-wheel-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t blink-cursor-mode: t global-auto-composition-mode: t auto-composition-mode: t auto-encryption-mode: t auto-compression-mode: t line-number-mode: t transient-mark-mode: t Recent input: y M-x r e p o r t - e m Recent messages: setting up indent stuff Indentation variables are now local. Indentation setup for shell type sh Note: file is write protected Setting up indent for shell type sh setting up indent stuff Indentation variables are now local. Indentation setup for shell type sh Desktop: 21 buffers restored. For information about GNU Emacs and the GNU system, type C-h C-a.