Re: Big desktop undo buffer crashes Emacs
Bill Wohler [EMAIL PROTECTED] writes: Every morning for the past weeks, I've had a message in my minibuffer that roughly goes, Desktop undo buffer is 3+ MB, discard? (yes or no). I've been saying yes. This morning, feeling snarky, I said no and Emacs crashed. I said no to that question twice this morning, and Emacs did not crash. What is this Desktop undo buffer by the way? And why does Emacs keep asking me this question? I'd still like to know the answer to these questions. Thanks. -- Bill Wohler [EMAIL PROTECTED] http://www.newt.com/wohler/ GnuPG ID:610BD9AD Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian! If you're passed on the right, you're in the wrong lane. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Big desktop undo buffer crashes Emacs
Bill Wohler [EMAIL PROTECTED] writes: What is this Desktop undo buffer by the way? And why does Emacs keep asking me this question? I'd still like to know the answer to these questions. Thanks. `undo-outer-limit' might provide some explanation. admin/FOR-RELEASE has an item about `undo-ask-before-discard' too. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
debugger entered when debug-on-error = nil
emacs -Q M-: (setq 4 5) The debugger is entered, even though `debug-on-error' is nil (by default): Debugger entered--Lisp error: (wrong-type-argument symbolp 4) (setq 4 5) eval((setq 4 5)) eval-expression((setq 4 5) nil) call-interactively(eval-expression) In GNU Emacs 22.0.50.1 (i386-mingw-nt5.1.2600) of 2006-03-20 on W2ONE X server distributor `Microsoft Corp.', version 5.1.2600 configured using `configure --with-gcc (3.4) --cflags -Id:/g/include' 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: ENU locale-coding-system: cp1252 default-enable-multibyte-characters: t Major mode: Debugger Minor modes in effect: encoded-kbd-mode: t tooltip-mode: t auto-compression-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 line-number-mode: t Recent input: down-mouse-1 mouse-1 M-: ( s e t q SPC 4 SPC 5 ) return help-echo help-echo help-echo help-echo help-echo help-echo help-echo menu-bar help-menu report-emacs-bug Recent messages: (C:\Emacs-22-2006-03-20\bin\emacs.exe -q --no-site-file --debug-init C:\drews-lisp-20) Loading encoded-kb...done For information about the GNU Project and its goals, type C-h C-p. Loading dired... Loading regexp-opt...done Loading dired...done Loading debug...done Entering debugger... Loading help-mode...done Loading emacsbug...done ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Big desktop undo buffer crashes Emacs
Bill Wohler wrote: Bill Wohler [EMAIL PROTECTED] writes: Every morning for the past weeks, I've had a message in my minibuffer that roughly goes, Desktop undo buffer is 3+ MB, discard? (yes or no). I've been saying yes. This morning, feeling snarky, I said no and Emacs crashed. I said no to that question twice this morning, and Emacs did not crash. Emacs only crashes if the size of the undo info is big enough to cause memory overflow. So the fact that if you answer no, Emacs sometimes crashes and sometimes not is to be expected. Also, if you leave Emacs running while the question is being asked and leave your computer without answering the question for a relatively long time, memory leakage will occur. What is this Desktop undo buffer by the way? I do not use desktop. But my impression is that desktop should disable undo somewhere. Somebody who uses and knows desktop should take a look at that. And why does Emacs keep asking me this question? For debugging purposes. I do not know desktop well enough, but this seems to be a bug in desktop (failing to disable undo). Once Emacs-22 is released, the undo info will be discarded automatically, to prevent crashes and memory leakage. Sincerely, Luc. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: debugger entered when debug-on-error = nil
Drew Adams [EMAIL PROTECTED] writes: emacs -Q M-: (setq 4 5) The debugger is entered, even though `debug-on-error' is nil (by default): AFAIK, it's a feature: ,[ C-h f eval-expression RET ] | eval-expression is an interactive compiled Lisp function in `simple.el'. | It is bound to M-:, M-ESC :. | (eval-expression eval-expression-arg optional | eval-expression-insert-value) | | [...] | | If `eval-expression-debug-on-error' is non-nil, which is the default, | this command arranges for all errors to enter the debugger. | | [back] ` « for _all_ errors ». Regards, -- | Michaël `Micha' Cadilhac | Un certain Blaise Pascal | | Epita/LRDE Promo 2007 | etc... etc... | | http://www.lrde.org/~cadilh_m | -- Prévert (Les paris stupides) | `-- - JID: [EMAIL PROTECTED] --' - --' ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: should c-indentation-style be marked as safe?
So what should we do here: mark c-indentation-style as safe or delete the local variable from etags.c ? For now, I'd say delete it (or comment it out somehow). For the longer term, I think we should make it work to bind that variable, but maybe we cannot do that now. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: add info about safe-local-variable to describe-variable
Good idea--please do install it. Please also update the fill-column example in man/custom.texi. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Big desktop undo buffer crashes Emacs
Every morning for the past weeks, I've had a message in my minibuffer that roughly goes, Desktop undo buffer is 3+ MB, discard? (yes or no). I've been saying yes. This morning, feeling snarky, I said no and Emacs crashed. Could you please provide the precise text of the message? The message includes a buffer name; what is the buffer name? ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: empty input for fakemail.c
I fixed this. And the one in movemail. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
RE: debugger entered when debug-on-error = nil
M-: (setq 4 5) The debugger is entered, even though `debug-on-error' is nil (by default): | M-: runs the command eval-expression | | [...] | | If `eval-expression-debug-on-error' is non-nil, which is the default, | this command arranges for all errors to enter the debugger. 1. Oh, that's a new one on me: `eval-expression-debug-on-error'. Is it supposed to overrule `debug-on-error' this way (apparently so)? And its default value is non-nil - is that the appropriate default value? 2. The doc string you quote says that `eval-expression-debug-on-error' non-nil means that *all* errors enter the debugger. If so, and if the default value is non-nil, then *all* errors enter the debugger. If that were the case, then what would be the point of `debug-on-error'? 3. Is `eval-expression-debug-on-error' perhaps designed (in spite of what the doc string says) to apply only to errors during execution of `eval-expression'? That's what the Emacs-Lisp manual says: If this variable has a non-`nil' value, then `debug-on-error' is set to `t' when evaluating with the command `eval-expression'. 4. In buffer *scratch*, type (setq 4 5) and then use `C-x C-e' (`eval-last-sexp'). The debugger is entered, just as for `M-:'. So perhaps `eval-expression-debug-on-error' is *not* just for command `eval-expression', in spite of both its doc string and its Emacs Lisp-manual entry? So just what is its scope? The Emacs manual says this, which I'm guessing is more correct (where these commands refers to *all* of the Lisp evaluation commands): `eval-expression-debug-on-error' controls whether evaluation errors invoke the debugger when *these commands* are used; its default is `t'. 5. According to the convention that emacs-devel is frequently touting, the option name should end in -flag: `eval-expression-debug-on-error-flag'. (Likewise, `debug-on-error', BTW.) 6. The behavior and doc should be reconsidered and clarified. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
bookmark-alist doc string is incorrect
emacs -Q I already have some bookmarks, created in an earlier version of Emacs - I don't know if that affects this question or not. I doubt it, since the doc string for Emacs 20 is identical (i.e. also incorrect in the same way, wrt my bookmark-alist). C-h v bookmark-alist Mine looks like this: ((Linux ~ ((filename . /whatever.com:/home/whomever/) (front-context-string . .Xdefaults\n drw) (rear-context-string . 99 Nov 18 23:54 ) (position . 220))) (Linux: Emacs lisp/ ((filename . /whatever.com:/usr/share/emacs/21.3/lisp/) (front-context-string . COPYING\n -rw-r-) (rear-context-string . 92 Mar 18 2003 ) (position . 233))) (Windows - Emacs 22 Lisp ((filename . c:/Emacs-22-2006-03-20/lisp) (front-context-string . .arch-inventory\n) (rear-context-string . 22 Jun 11 2004 ) (position . 222))) ...) The doc string for bookmark-alist says this: each BOOKMARK is of the form (NAME (filename . FILE) (front-context-string . FRONT-STR) (rear-context-string . REAR-STR) (position . POS) (info-node . POS) (annotation . ANNOTATION)) That seems incorrect, given my alist, above. It should say this, I suspect (note additional parens): (NAME ((filename . FILE) (front-context-string . FRONT-STR) (rear-context-string . REAR-STR) (position . POS) (info-node . POS) (annotation . ANNOTATION))) In GNU Emacs 22.0.50.1 (i386-mingw-nt5.1.2600) of 2006-03-20 on W2ONE X server distributor `Microsoft Corp.', version 5.1.2600 configured using `configure --with-gcc (3.4) --cflags -Id:/g/include' 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: ENU locale-coding-system: cp1252 default-enable-multibyte-characters: t Major mode: Dired by name Minor modes in effect: encoded-kbd-mode: t tooltip-mode: t auto-compression-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 line-number-mode: t Recent input: help-echo help-echo help-echo help-echo help-echo help-echo help-echo help-echo help-echo menu-bar help-menu report-emacs-bug Recent messages: (C:\Emacs-22-2006-03-20\bin\emacs.exe -q --no-site-file --debug-init C:\drews-lisp-20) Loading encoded-kb...done For information about the GNU Project and its goals, type C-h C-p. Loading dired... Loading regexp-opt...done Loading dired...done Loading emacsbug...done ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
RE: bookmark-alist doc string is incorrect
This comment in bookmark.el is perhaps pertinent. ;;; File format stuff ;; The OLD format of the bookmark-alist was: ;; ;; ((bookmark-name (filename ;;string-in-front ;;string-behind ;;point)) ;;...) ;; ;; The NEW format of the bookmark-alist is: ;; ;; ((bookmark-name ((filename . FILENAME) ;;(front-context-string . string-in-front) ;;(rear-context-string . string-behind) ;;(position . POINT) ;;(annotation . annotation) ;;(whatever . VALUE) ;;... ;;)) ;;...) ;; ;; ;; I switched to using an internal as well as external alist because I ;; felt that would be a more flexible framework in which to add ;; features. It means that the order in which values appear doesn't ;; matter, and it means that arbitrary values can be added without ;; risk of interfering with existing ones. ;; ;; BOOKMARK-NAME is the string the user gives the bookmark and ;; accesses it by from then on. ;; ;; FILENAME is the location of the file in which the bookmark is set. ;; ;; STRING-IN-FRONT is a string of `bookmark-search-size' chars of ;; context in front of the point at which the bookmark is set. ;; ;; STRING-BEHIND is the same thing, but after the point. ;; ;; The context strings exist so that modifications to a file don't ;; necessarily cause a bookmark's position to be invalidated. ;; bookmark-jump will search for STRING-BEHIND and STRING-IN-FRONT in ;; case the file has changed since the bookmark was set. It will ;; attempt to place the user before the changes, if there were any. ;; ANNOTATION is the annotation for the bookmark; it may not exist ;; (for backward compatibility), be nil (no annotation), or be a ;; string. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
doc for catch throw should not mention tag
The doc strings and the Emacs Lisp-manual doc for `catch' and `throw' currently refer to the catch target as the tag. Because of possible confusion with tags files, and to let searching the manual for \btag find only occurrences that involve tag files, the doc for `catch' and `throw' should call the target something like target or label instead of tag. In GNU Emacs 22.0.50.1 (i386-mingw-nt5.1.2600) of 2006-03-20 on W2ONE X server distributor `Microsoft Corp.', version 5.1.2600 configured using `configure --with-gcc (3.4) --cflags -Id:/g/include' 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: ENU locale-coding-system: cp1252 default-enable-multibyte-characters: t Major mode: Info Minor modes in effect: encoded-kbd-mode: t tooltip-mode: t auto-compression-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 line-number-mode: t Recent input: down-mouse-1 mouse-1 C-h i help-echo help-echo help-echo help-echo down-mouse-2 mouse-2 help-echo help-echo help-echo help-echo s t a g return s \ b t a g return s return help-echo help-echo help-echo help-echo help-echo help-echo help-echo help-echo help-echo help-echo menu-bar help-menu report-emacs-bug Recent messages: For information about the GNU Project and its goals, type C-h C-p. Loading dired... Loading regexp-opt...done Loading dired...done Loading info... Loading easymenu...done Loading info...done Composing main Info directory...done Searching subfile elisp-2... Loading emacsbug...done ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: doc for catch throw should not mention tag
Drew Adams wrote: The doc strings and the Emacs Lisp-manual doc for `catch' and `throw' currently refer to the catch target as the tag. Because of possible confusion with tags files, and to let searching the manual for \btag find only occurrences that involve tag files, the doc for `catch' and `throw' should call the target something like target or label instead of tag. tag is just standard Lisp terminology for this. That is why, for instance, the Common Lisp function `tagbody' is not called `labelbody' or `targetbody'. Sincerely, Luc. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
RE: doc for catch throw should not mention tag
The doc strings and the Emacs Lisp-manual doc for `catch' and `throw' currently refer to the catch target as the tag. Because of possible confusion with tags files, and to let searching the manual for \btag find only occurrences that involve tag files, the doc for `catch' and `throw' should call the target something like target or label instead of tag. tag is just standard Lisp terminology for this. That is why, for instance, the Common Lisp function `tagbody' is not called `labelbody' or `targetbody'. Yes, I know that. But I don't think Common Lisp has tags tables. The Emacs Tags facility is well known. Anyway, here are some more comments. Take them for what you will... --- It turns out that there is anyway almost no mention of tags tables (or files) in the Emacs-Lisp manual. So my suggestion about that manual is perhaps irrelevant. In the Emacs manual, however, tag refers mainly to tags tables (the Tags facility) - that is what users will think a tag is. So I still think it's a bad idea to use tag for just about anything in the Lisp manual. For example: 1. It's too bad we also have keyword :tag. That keyword should perhaps have been called :label (that's what it is), but it's too late for that now. This is the most frequent occurrence of tag in the Emacs-Lisp manual, BTW. 2. Manual node Bindat Spec could avoid using tag in `union FORM (TAG SPEC)...'. Here, the word means nothing - the TAG is similar to the FORM. Some better term should be found. Back to the Emacs manual - 1. It looks like Tumme has now introduced yet another meaning for tag - see node Tumme. At least this meaning is a bit similar to the tags-table notion. However, this similarity can be an even worse source of confusion, especially since Tumme speaks of tagged files. It would be better to pick a better term for this - the Tumme doc itself suggests alternatives: Tag is just another word for keyword, label or category. I'd suggest using category or perhaps property. 2. Node Init Syntax refers to a `-*-coding: CODING-SYSTEM-*-' tag on the first line. This should be called a declaration, not a tag. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: doc for catch throw should not mention tag
Of course you can find tons of different meanings for the word tag, because it is such a common word. CVS has tags also. I am pretty sure that if I wanted to take the trouble, I could easily point out tons of different uses for label or target too. There is absolutely no problem as long as it is clear from the context which type of tag is meant. In practice, after reading through tons of docs, I never encountered any ambiguity whatsoever. In situations where ambiguity could arise one could easily specify catch tag or CVS tag or whatever. But this will very seldom happen in practice. Sincerely, Luc. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Big desktop undo buffer crashes Emacs
What is this Desktop undo buffer by the way? I do not use desktop. But my impression is that desktop should disable undo somewhere. Somebody who uses and knows desktop should take a look at that. It is really fishy that Desktop does so much consing. We need to figure out why. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: tool-bar-setup overwrites local tool-bar-map
To see what should have happened: emacs22 -Q M-x tool-bar-mode Note how Preferences and Help icons are present. M-x info Note how Preferences and Help icons are absent. In what sense is that what should have happened? I do not follow. Shouldn't the Preferences and Help icons always be present? No, I may not ;-). It breaks the idiom from the tool-bar-add-item documentation, namely: (defvar foo-tool-bar-map (let ((tool-bar-map (make-sparse-keymap))) (tool-bar-add-item ...) ... tool-bar-map)) It also did some mean and nasty things to the MH-E toolbar. The following patch (to tool-bar-setup) seems to be working a little better. What are you asking us to do? ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
