Re: Function w32_abort not defined
Usually I don't configure Emacs with --without-x, so I don't see a similar message. I see it a lot. It would be good to somehow suppress this message (by using some GDB option?). I tried very hard to find a way to do that, but failed. I'm open to suggestions. Maybe another approach is better: what's w32_abort? Couldn't we rename it to some more generic name and then define (and use) it for all versions? Stefan ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Function w32_abort not defined
Cc: Juri Linkov [EMAIL PROTECTED], emacs-pretest-bug@gnu.org From: Stefan Monnier [EMAIL PROTECTED] Date: Fri, 02 Jan 1970 03:25:26 -0500 what's w32_abort? See w32fns.c: it pops up the Emacs Abort dialog. The MS-Windows build redirects all calls to `abort' to this function. Couldn't we rename it to some more generic name and then define (and use) it for all versions? Fine with me. But then we should do something similar with x_error_quitter, I think. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Fwd: size of the slider bar
The length of the slider bar, the blue bar that slides inside the scroll bar track (I'm not sure about the terminology) changes randomly as you scroll up and down the text. I'm sure you know that the ratio of the length of this bar to the total length of the scroll bar must represent the ratio between the number of lines in the window to the number of lines in the file. That would take too long, for large files; he would not like this either, but he has not realized this would be the price of what he wants. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Function w32_abort not defined
It would be good to somehow suppress this message (by using some GDB option?). I tried very hard to find a way to do that, but failed. I'm open to suggestions. I wouldn't spend much time on it myself. Ordinary users don't get these messages, since they don't run Emacs under GDB. We could add this command to .gdbinit to reassure anyone who might get worried: output If you see messages immediately following about functions not being defined,\n don't worry about them. Nothing is wrong.\n ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: describe-char
AFAICT it's the exact same situation as in all other cases, except that you use (buffer-string). All other cases call `help-setup-xref' with the same function name and its arguments just before calling `(with-output-to-temp-buffer (help-buffer) ...)' and replacing old contents of the help buffer with the new contents. But this is not possible when the new contents should be stored in the help xref stack. Isn't that what I wrote? Instead of using (help-insert-string (buffer-string)) I'd use (describe-char pos buf), which admittedly forces you to add a `buf' optional argument. This is not reliable way to restore the old output of `describe-char' since the original buffer might be killed or the character at the old position might be deleted, The same holds for most/all other uses of help-setup-xref. Stefan ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
