void: footnote-english-lower-regexp
Bootstrapping CVS of today brought the following error message: Symbol's value as variable is void: footnote-english-lower-regexp make[2]: *** [bootstrap-emacs] Fehler 255 make[2]: Leaving directory `/foo/bar/... /emacs/src' make[1]: *** [bootstrap-build] Fehler 2 make[1]: Leaving directory `/foo/bar/... /emacs' make: *** [bootstrap] Fehler 2 Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
slow with html-file
Pretest Emacs is very slow--near to freeze--after opening the attached html-file. Opening takes 10 seconds and more. Thanks Andreas Roehler In GNU Emacs 22.0.95.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2007-03-12 on kiste X server distributor `The X.Org Foundation', version 11.0.60802000 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: de_DE.UTF-8 locale-coding-system: utf-8 default-enable-multibyte-characters: t Major mode: SGML Minor modes in effect: xslt-process-mode: t semantic-idle-scheduler-mode: t shell-dirtrack-mode: t csv-field-index-mode: t savehist-mode: t recentf-mode: t iswitchb-mode: t auto-insert-mode: t auto-image-file-mode: t 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 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 transient-mark-mode: t abbrev-mode: t Recent input: a b tab s tab return down-mouse-1 mouse-1 C-x 1 down down down up up backspace backspace backspace backspace backspace backspace backspace backspace backspace backspace backspace backspace M- next next next next next next next next next next next next next next next next next mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 next M- M-x r e p o r t - e m c backspace a tab b u g return Recent messages: Unclosed tag BODY Unclosed tag META Unclosed tag HTML Error during redisplay: (quit) Quit Making completion list... Loading emacsbug...done autoren.tgz Description: GNU Unix tar archive ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacs-22.0.95 successful installs
Richard Stallman schrieb: Do you want this kind of testing status sent to emacs-pretest-bug? You may as well report successes only to me. Don't you risk to receive a lot of redundant reports that way, as other users can't see if their system is mentioned already? Beside: As far as it concerns me, I like to read about successful installations in this list, for what reason whatever. __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
auto-insert help-buffer
emacs -q M-x auto-insert Prompt for keyword C-h opens a help-buffer with descriptions, but without the corresponding keywords visible. This buffer vanishes, when clicked by mouse. = scroll-bar-toolkit-scroll: Wrong type argument: window-live-p, #window 7 Clicking the scroll-bar once also produced a segmentation fault. (error-message was in German: Speicherzugriffsfehler) So far __ Andreas Roehler Suse 10.0 In GNU Emacs 22.0.93.4 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2007-02-18 on kiste X server distributor `The X.Org Foundation', version 11.0.60802000 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: de_DE.UTF-8 locale-coding-system: utf-8 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: - i n s e r t return a s d M-x up return return up M-x up return C-x C-w e i l . e l return y M-x up return return C-h help-echo mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 mouse-1 M-x r e p o r t - e m a c s - b u g return backspace backspace backspace backspace backspace backspace backspace C-g M-x C-g up up up up up M-x up return return C-h help-echo down-mouse-1 drag-mouse-1 C-g M-x r e p o r t - e m tab return Recent messages: Loading help-mode...done scroll-bar-toolkit-scroll: Wrong type argument: window-live-p, #window 7 call-interactively: Command attempted to use minibuffer while in minibuffer Quit [2 times] mouse-drag-region: Wrong type argument: window-live-p, #window 9 mouse-minibuffer-check: Wrong type argument: window-live-p, #window 9 Quit Loading emacsbug... Loading regexp-opt...done Loading emacsbug...done ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: info-lookup slow
Eli Zaretskii schrieb: Date: Sun, 11 Feb 2007 16:40:21 +0100 From: Andreas Roehler [EMAIL PROTECTED] CC: emacs-pretest-bug@gnu.org, Stefan Monnier [EMAIL PROTECTED], Richard Stallman [EMAIL PROTECTED] Ok now with CVS-Emacs, back to ten seconds, thanks. However, looking up symbol `defun' for example after prompt took still 38 seconds. As this command isn't called often, I can live with - just to mention it. Thanks for following up. I think the change below should fix this remaining problem as well: 2007-02-17 Eli Zaretskii [EMAIL PROTECTED] * info-look.el (info-lookup): Bind Info-fontify-maximum-menu-size to nil to speed up lookup of the symbol in index nodes. Index: lisp/info-look.el === RCS file: /cvsroot/emacs/emacs/lisp/info-look.el,v retrieving revision 1.55 diff -u -r1.55 info-look.el --- lisp/info-look.el 10 Feb 2007 11:12:42 - 1.55 +++ lisp/info-look.el 17 Feb 2007 11:59:07 - @@ -353,8 +353,11 @@ suffix (nth 3 (car doc-spec))) (when (condition-case error-data (progn - (Info-goto-node node) - (setq doc-found t)) + ;; Don't need Index menu fontifications here, and + ;; they slow down the lookup. + (let (Info-fontify-maximum-menu-size) + (Info-goto-node node) + (setq doc-found t))) (error (message Cannot access Info node %s node) (sit-for 1) It's fine now. Just a few seconds. Thanks. __ Andreas Roehler GNU Emacs 22.0.93.4 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2007-02-18 on kiste ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: info-lookup slow
Eli Zaretskii schrieb: Date: Mon, 05 Feb 2007 11:15:25 +0100 From: Andreas Roehler [EMAIL PROTECTED] Whereas `emacs-22.0.92' took approximately 10 seconds with info-lookup to until the prompt Describe symbol was shown, 22.0.93.1 takes up to one minute. Thank you for your report. Does the patch below fix it? (Yet another unnecessary change that created a new bug, sigh...) Index: lisp/info-look.el === RCS file: /cvsroot/emacs/emacs/lisp/info-look.el,v retrieving revision 1.54 diff -u -r1.54 info-look.el --- lisp/info-look.el 21 Jan 2007 03:53:11 - 1.54 +++ lisp/info-look.el 10 Feb 2007 11:03:42 - @@ -441,6 +441,7 @@ (let ((doc-spec (info-lookup-doc-spec topic mode)) (regexp (concat ^\\( (info-lookup-regexp topic mode) \\)\\([ \t].*\\)?$)) + Info-fontify-maximum-menu-size node trans entry item prefix result doc-found (buffer (get-buffer-create temp-info-look))) (with-current-buffer buffer Ok now with CVS-Emacs, back to ten seconds, thanks. However, looking up symbol `defun' for example after prompt took still 38 seconds. As this command isn't called often, I can live with - just to mention it. Andreas Roehler ; In GNU Emacs 22.0.93.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2007-02-11 X server distributor `The X.Org Foundation', version 11.0.60802000 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: de_DE.UTF-8 locale-coding-system: utf-8 default-enable-multibyte-characters: t Major mode: Lisp Interaction Minor modes in effect: show-paren-mode: t 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 transient-mark-mode: t Recent input: down-mouse-1 mouse-1 M-x r e p o r t - e m tab return Recent messages: Loading /usr/local/share/emacs/22.0.93/leim/leim-list.el (source)...done Loading /home/speck/emacs/leim/leim-list.el (source)...done Loading /usr/local/share/emacs/site-lisp/egg/leim-list.el (source)...done Loading /usr/share/emacs/site-lisp/anthy/leim-list.elc...done Loading /usr/share/emacs/site-lisp/egg/leim-list.el (source)...done Loading paren...done For information about the GNU Project and its goals, type C-h C-p. [2 times] Loading emacsbug... Loading regexp-opt...done Loading emacsbug...done ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
info-lookup slow
emacs -q Whereas `emacs-22.0.92' took approximately 10 seconds with info-lookup to until the prompt Describe symbol was shown, 22.0.93.1 takes up to one minute. __ Andreas Roehler ;; X server distributor `The X.Org Foundation', version 11.0.60802000 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: de_DE.UTF-8 locale-coding-system: utf-8 default-enable-multibyte-characters: t Major mode: Lisp Interaction Minor modes in effect: show-paren-mode: t 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 transient-mark-mode: t Recent input: down-mouse-1 mouse-1 M-x i n f o - l o o k u p - s y m b o l return C-g M-x v e r s i o n return M-x r e p o r t - e m tab return Recent messages: Loading easymenu...done Loading info-look...done Processing Info node `(emacs)Command Index'...done Processing Info node `(emacs)Variable Index'...done Processing Info node `(elisp)Index'...done Quit GNU Emacs 22.0.93.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2007-01-30 Loading emacsbug... Loading regexp-opt...done Loading emacsbug...done ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
defun-at-point, (thing-at-point 'defun)
With cursor inside a functions definition, what should `defun-at-point' resp. (thing-at-point 'defun) return: - the function name - the complete functions corpus What about introducing `functionname-at-point'? Thanks __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: list-at-point
What do you do if scan-lists reports an error? Condition case re-introduced... It now reads as follows: (defun bounds-of-thatpt (thing optional arg) Determine the start and end buffer locations for the THING at point. THING is a symbol which specifies the kind of syntactic entity you want. Possibilities include `symbol', `list', `sexp', `defun', `filename', `url', `word', `sentence', `whitespace', `line', `page' and others. (condition-case nil (save-excursion (let ((orig (point)) (beg (progn (funcall ;; First, move to beg. (or (get thing 'beginning-op) (lambda () (forward-char 1) (forward-thing thing -1 (point))) (end (progn (funcall ;; Then move to end. (or (get thing 'end-op) (lambda () (forward-thing thing 1 (point ;; if orig not between beg and end, failure, nil (when (and(= beg orig) (= orig end) ( beg end)) (cons beg end (error nil))) Please have a look at the newly published thingatpt-util.el at gnu.emacs.sources Thanks __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
symbol-at-point
As already mentioned, I'm considering thing-at-point help functions, provide interactive specs, some bugfixing. I'll stay as close as possible at routines from thingatpt.el. Just one different behaviour until now: list-at-point will return the list too if called inside a string enclosed by that list - instead of nil now. With symbol-at-point however, I intend to drop the (if thing (intern thing)) form when called. Because I conceive this as not regular. All the thing-at-point forms just return the object at point, doing nothing else. To intern an object may have a lot of results not considered then. Altogether the user may not be notice it. Any objections, other ideas? __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Info - Changing the Location of Point
Seems as Emacs info node 8.2 Changing the Location of Point doesn't contain a link to move-commands as forward-list etc. Would consider it helpful. Thanks __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: backward-up-list
Stefan Monnier schrieb: (while (in-string-p) (backward-char 1)) That's the way a snail would do it, (goto-char (or (nth 8 (syntax-ppss)) (point))) would be faster and solve the same problem with comments at the same time. Stefan Thanks. However, I'm not convinced here. in-string-p is very clear and short written. (defun in-string-p () (let ((orig (point))) (save-excursion (beginning-of-defun) (nth 3 (parse-partial-sexp (point) orig) With syntax-ppss there are a lot of lines, hardly to follow. Altogether it ends up with the same core-function or at least calls it: (setq ppss (parse-partial-sexp pt-min pos nil nil ppss)) So I doubt it being faster. Cheers a nonbelieving snail ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: list-at-point
Checked your patch with a bound of (thing-at-point 'list)- function Watched execution with edebug. (foo at the beginning of the buffer, cursor at pipe) (defun foo () (message %s baz)) __|__ - Result: (23 44) wrong, must be: (23 43) (defun foo () (message %s baz)) __|_ edebug-signal: Format specifier doesn't match argument type ;;; The last error reveals a problem in `backward-up-list' IMO. Workaround: (while (in-string-p) (backward-char 1)) list-ops now in use: (put 'list 'end-op (lambda () (forward-list 1))) (put 'list 'beginning-op (lambda () (while (in-string-p) (backward-char 1)) (while (and (not (bobp)) (not (eq (char-syntax (char-after)) ?\())) (backward-up-list A solution is still needed, if point is not inside a list, just near. IMO it should not neither go inside nor across them. Cheers __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: backward-up-list
Stefan Monnier schrieb: Don't understand behaviour of `backward-up-list' in `emacs-lisp-mode' if inside a string. backward-up-list doesn't know you start from inside a string and instead assumes you start from outside of any string or comment. So when it bumps into the opening it thinks this is a closing and treats the text before that as being inside a string. Try it with: (foor an open ( inside a string blabla try it from HERE for fun.) Bug? Misfeature. Not letal. (while (in-string-p) (backward-char 1)) ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: list-at-point
martin rudalics schrieb: (put 'list 'end-op (lambda () (forward-list 1))) (setq thatpt-listconstruktor '\() (put 'list 'beginning-op (lambda () (unless (looking-at (format %s thatpt-listconstruktor )) (backward-up-list (unless (looking-at ()) seems simpler. But to check whether a character starts a list you should check its syntax as (eq (char-syntax (char-after)) ?\()) OK. Tried to make `thatpt-listconstruktor' a customizable variable, to let the user decide, what should be conceived as beginning and end of a list. Enabling strings and regexps here, it was intended to read databases with, extract arbitrary code etc. Meanwhile I think its better to create a separate data-at-point for this. The idea of thing-at-point is to get the thing if point is before or in it, or point is after it and not before a thing of the same kind. What do you get with point after (foo bar)? What do you do if point is not in the range beg..end? AFAIS old thing-at-point function returned just thatpt, if anything, nothing different. Drew Adams wrote `form-nearest-point', `form-nearest-point-with-bounds' and a lot of things around it with thatpt+.el. IMO the problem of old bounds-of-thatpt-function is: it starts to go forward, not backward, thus multiplying difficulties, as regexps don't work well from the end. There is shortcoming in the documentation too. The docstring of `thing-at-point' says: , | Possibilities include `symbol', `list', `sexp', `defun', `filename', `url', | `word', `sentence', `whitespace', `line', `page' and others. ` and others is misleading, as the user may get the impression, it's up to him to call thatpt with arbitrary regular names to get working. In fact it only works, if either the guesses as `(intern-soft (format forward-%s thing)))' are successful or the `beginning-op' and `end-op' is set before. The user should be averted so far. Question: What should thatpt return if it finds nothing appropriate? I prefer just `nil' at the moment. Maybe let the user decide? Introduce a customised return behaviour? What do you do if scan-lists reports an error? Will see. I'm going to look at the program a little bit further and do some checks. BTW. Here is s tool for it. With some adaptation it might be useful for others too. (defun thing-at-point-test-ar () (interactive) (let ((oldbuf (current-buffer)) (atp-list (list 'word-at-point-ar 'bounds-of-word-at-point-ar 'sentence-at-point-ar 'bounds-of-sentence-at-point-ar 'sexp-at-point-ar 'bounds-of-sexp-at-point-ar 'symbol-at-point-ar 'bounds-of-symbol-at-point-ar 'url-at-point-ar 'bounds-of-url-at-point-ar 'filename-at-point 'bounds-of-filename-at-point ))) (save-excursion (set-buffer (get-buffer-create thatpt-test)) (erase-buffer)) (dolist (elt atp-list) (let ((item (funcall elt))) (save-excursion (switch-to-buffer thatpt-test) (when (listp item) (setq item (concat (format %s (car item)) (format %s (cadr item) (insert (concat (format %s: elt) item \n))) (switch-to-buffer oldbuf) __ Regards Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: list-at-point
martin rudalics schrieb: Seems as function `list-at-point' from thingatpt.el fails. Currently `list-at-point' does `up-list' followed by `backward-sexp' followed by another `up-list' which doesn't make sense. Please look at the attached - largely untested - patch which also tries to handle the problem that `sexp-at-point' fails at eob. Thanks a lot caring for this. Probably its worthwhile to discuss possible changes a little bit. Hope it will not--and should not--delay upcoming release. What about to shorten `bounds-of-thing-at-point' as shown below? It works in the list-context, checked also with word, symbol, url: everything fine. ;; Lists ;; (put 'list 'end-op (lambda () (up-list 1))) (put 'list 'end-op (lambda () (forward-list 1))) (setq thatpt-listconstruktor '\() ;; (put 'list 'beginning-op 'backward-sexp) (put 'list 'beginning-op (lambda () (unless (looking-at (format %s thatpt-listconstruktor )) (backward-up-list (defun bounds-of-thing-at-point-ar (thing) Determine the start and end buffer locations for the THING at point. THING is a symbol which specifies the kind of syntactic entity you want. Possibilities include `symbol', `list', `sexp', `defun', `filename', `url', `word', `sentence', `whitespace', `line', `page' and others. (let ((beg (progn (funcall (or (get thing 'beginning-op) (lambda () (forward-thing thing -1 (point))) (end (progn (funcall (or (get thing 'end-op) (lambda () (forward-thing thing 1 (point (cons beg end))) (defun bounds-of-list-at-point-ar (optional arg) (interactive p) (let ((bounds (bounds-of-thing-at-point-ar 'list))) (when arg (message %s bounds)) bounds)) (defun list-at-point-ar (optional arg) (interactive p) (let* ((bounds (bounds-of-thing-at-point-ar 'list)) (list (buffer-substring-no-properties (car bounds) (cdr bounds (when arg (message %s list) list))) (defun copy-list-at-point-ar (optional arg) (interactive p) (let* ((bounds (bounds-of-thing-at-point-ar 'list)) (list (buffer-substring-no-properties (car bounds) (cdr bounds (when arg (message %s list) (kill-new list (defun kill-list-at-point-ar (optional arg) (interactive p) (let* ((bounds (bounds-of-thing-at-point-ar 'list)) (start (car bounds)) (end (cdr bounds))) (kill-region start end))) BTW: Published a bunch of other thing-at-point utility-functions at gnu-emacs-sources. Regards __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
list-at-point
Seems as function `list-at-point' from thingatpt.el fails. To check this, I set a defun foo at the beginning of a buffer and called check-list functions an them as given. The result was always nil, but should return the list. (defun foo () (interactive *) (message %s baz)) (defun check-list-at-point-1 () (interactive) (goto-char 3) (message %s (list-at-point))) (defun check-list-at-point-2 () (interactive) (goto-char 3) (message %s (form-at-point 'list 'listp))) AFAIS the error is in `bounds-of-thing-at-point' which grasps the right positions during its curse, but fails to store and deliver them. For the moment I wrote some simplified, independent list-handlers, which I forward herewith for discussion. ;;; (defun separate-list-ar (arg) (interactive p) (unless (looking-at \\s\() (backward-up-list)) (let* ((opoint (point))) (when (re-search-backward [^ \t]+ (line-beginning-position) t 1) (goto-char opoint) (newline-and-indent)) (push-mark) (forward-list arg) (setq opoint (point)) (when (or (looking-at \\s\)) (re-search-forward [^ \t]+ (line-end-position) t 1)) (goto-char opoint) (save-excursion (newline-and-indent) (defun separate-and-comment-ar (arg) Separate list and save a commented copy of it (interactive p) (separate-list-ar arg) (comment-uncomment-line-or-region arg)) (defun mark-list-ar (arg) (interactive p) (unless (looking-at \\s\() (backward-up-list)) (push-mark) (forward-list arg)) (defun copy-list-ar (arg) (interactive p) (let ((start (progn (unless (looking-at \\s\() (backward-up-list)) (push-mark) (point))) (end (progn (forward-list arg) ;;(forward-char 1) (point (copy-region-as-kill start end) )) (defun transpose-list-ar () (interactive *) (when (looking-at [ \n\t\f]) (backward-char 1)) (copy-list-ar 1) (backward-sexp 2) (let ((start (point))) (copy-list-ar 1) (forward-sexp) (delete-region start (point))) (insert (concat (cadr kill-ring)\n(car kill-ring (defun kill-list-ar (arg) (interactive p) (let ((start (progn (unless (looking-at \\s\() (backward-up-list)) (push-mark) (point))) (end (progn (forward-list arg) (point (kill-region start end) )) (defun comment-uncomment-line-or-region (optional arg) Comments or uncomments a line according to state before. With key pressed, continues with next line. With arg copies and reinserts last line. (interactive *P) (comment-normalize-vars) (let* ((arg (if arg (prefix-numeric-value arg) 0)) (start (if (and mark-active transient-mark-mode) (region-beginning) (line-beginning-position))) (end (if (and mark-active transient-mark-mode) (region-end) (line-end-position))) (line-to-comment-or-uncomment (buffer-substring-no-properties (or start (line-beginning-position)) (or end (line-end-position) (cond ((eq 1 arg) ;; comment and reinsert (comment-or-uncomment-region start end) (indent-according-to-mode) (end-of-line) (newline) (insert line-to-comment-or-uncomment) (indent-according-to-mode)) (( 1 arg) ;; comment as many lines are given (while (= 1 (prefix-numeric-value arg)) (comment-or-uncomment-region (line-beginning-position) (line-end-position)) (indent-according-to-mode) (end-of-line) (forward-line 1) ;; (indent-according-to-mode) (setq arg (1- arg ((and start end) (comment-or-uncomment-region start end) (indent-according-to-mode) (if (eobp) (progn (newline) (indent-according-to-mode)) (progn (forward-line 1) (indent-according-to-mode (t ;; just one line (progn (comment-or-uncomment-region (line-beginning-position) (line-end-position)) (indent-according-to-mode) (if (eobp) (progn (newline) (indent-according-to-mode)) (progn (forward-line 1) (indent-according-to-mode Any comments welcome. __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: refcards
gv refcard.ps still explains Emacs version 21 Then your Emacs checkout must be older than 2006-06-28: ls -l ... 2006-06-28 15:26 de-refcard.ps checked out today. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: refcards
Reiner Steib schrieb:
On Tue, Sep 26 2006, Andreas Roehler wrote:
gv refcard.ps
still explains Emacs version 21
Then your Emacs checkout must be older than 2006-06-28:
ls -l ... 2006-06-28 15:26 de-refcard.ps
As it concerns refcard.ps - not de-refcard -, the date above is not
indeed helpful.
Checking the cvs-repository via html,
refcard.ps there is shown as 1.2 four years old.
ps2ascii refcard.ps refcard.txt
head refcard.txt -
GNU Emacs Reference Card
(for version 21)
Starting Emacs To enter GNU Emacs 21, just type its name: emacs To read in a
file to edit, see Files, below.
Leaving Emacs suspend Emacs (or iconify it under X) C-z exit Emacs permanently
C-x C-c
;
My cvs-command was: cvs -z3 -d:pserver:[EMAIL PROTECTED]:/sources/emacs co .
Maybe I could do a better upload?
BTW: refcard.tex seems ok:
\title{GNU Emacs Reference Card}
\centerline{(for version 22)}
\section{Starting Emacs}
To enter GNU Emacs 22, just type its name: \kbd{emacs}
;;;
Maybe something with the translation from tex to ps
went wrong?
My build is GNU Emacs 22.0.50.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2006-09-11
__
Andreas Roehler
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: local chars displayed as numbers
Reiner Steib schrieb: On Thu, Sep 20 2006, Andreas Roehler wrote: Little correction, concerning last mail to Reiner Steib: Phenomen is gone if I - mark and delete a portion from the beginning of the buffer - mark and delete a portion from the end of the buffer - save and reopen; also - as reported - its gone, if I mark and copy the buffer into a new one. Probably you didn't include the problematic char in this situations. Plain opening, reopening, delete something without mark-region doesn't change it. Please try to visit that file by: C-x RET c iso-8859-1 RET C-x C-f FILENAME I get `jÃ1/4ngsten' instead of `jüngsten' `Ãsterreich' instead of `Österreich' I suppose this was _after_ converting the file to UTF-8. Saving with C-x RET f utf-8 RET C-x C-s can't help here. Please try again with Handa-san's changes to `language/european.el'. Bye, Reiner. Hi, thanks. Unfortunately I can't report success: With anew loaded european.el it's still the same. Strange beside - as I reported already: if I mark and delete big portions from the beginning and the end of the buffer, save the rest with new name and reopen, it's gone. But that's only with big portions: Tried it with a few lines, it remained unchanged. Also its gone if I copy it into a new buffer. Send you the test8.txt off-list. Have a good time __ Andreas Roehler +49306927863 ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
local chars displayed as numbers
Emacs -q When opening files written with previous Emacs versions, several chars - German Umlaute and also `-' for example - are displayed as numbers, not as symbol. So `Straße' is shown as `Stra\337e' C-x = at point gives the correct result and also shows the symbol: - Char: ß (223, #o337, #xdf, file #xDF) point=395 of 2660 (15%) column=13 C-h v buffer-file-coding-system - ... Its value is raw-text-unix If I copy that portion into a new buffer, it's displayed correctly. So far __ Andreas Roehler In GNU Emacs 22.0.50.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2006-09-11 X server distributor `The X.Org Foundation', version 11.0.60802000 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: de_DE.UTF-8 locale-coding-system: utf-8 default-enable-multibyte-characters: t Major mode: Text 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 p r o g tab v e r f tab f i n tab M-backspace M-backspace M-backspace v e r f a r backspace h tab f i n tab / 2 0 0 5 tab 0 3 tab return M-x r e p o r t - e m a c s - b u g return Recent messages: Finished loading /usr/local/share/emacs/site-lisp/egg/leim-list.el and load others... Loading /usr/local/share/emacs/22.0.50/leim/leim-list.el (source)...done (emacs -Q --debug-init) For information about the GNU Project and its goals, type C-h C-p. Making completion list... Loading help-mode...done Loading emacsbug... Loading regexp-opt...done Loading emacsbug...done ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: local chars displayed as numbers
Didn't you say in de.comp.editoren (the thread following news:[EMAIL PROTECTED]) that you cannot reproduce this problem anymore? So it is. After all files have been processed with the program published there, it never happened again until now. Also it seems to affect just one file in this directory. What makes it difficult to reproduce: it happens only just after opening. After a save, it reopens correct. Wll send you an example off-list. Thanks so far. __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: local chars displayed as numbers
Little correction, concerning last mail to Reiner Steib: Phenomen is gone if I - mark and delete a portion from the beginning of the buffer - mark and delete a portion from the end of the buffer - save and reopen; also - as reported - its gone, if I mark and copy the buffer into a new one. Plain opening, reopening, delete something without mark-region doesn't change it. Please try to visit that file by: C-x RET c iso-8859-1 RET C-x C-f FILENAME I get `jÃ1/4ngsten' instead of `jüngsten' `Ãsterreich' instead of `Österreich' Saving with C-x RET f utf-8 RET C-x C-s can't help here. Thanks all! __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Memory leak?
Andreas Roehler schrieb: Seems something wrong with my build GNU Emacs 22.0.50.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2006-09-11 Emacs consumes all the memory by time, as `top' indicates. Config.log reports the following: configure:13037: checking malloc/malloc.h usability configure:13049: gcc -c -I/usr/X11R6/include -O2 -I/usr/X11R6/include -D_BSD_SOURCE conftest.c 5 conftest.c:133:27: error: malloc/malloc.h: No such file or directory De facto malloc.h resides at /usr/include/malloc.h Didn't encounter that with a previews cvs-build from 2006-07-17. So far Thanks __ Andreas Roehler Andreas Roehler schrieb: Seems something wrong with my build GNU Emacs 22.0.50.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2006-09-11 Emacs consumes all the memory by time, as `top' indicates. Config.log reports the following: configure:13037: checking malloc/malloc.h usability configure:13049: gcc -c -I/usr/X11R6/include -O2 -I/usr/X11R6/include -D_BSD_SOURCE conftest.c 5 conftest.c:133:27: error: malloc/malloc.h: No such file or directory De facto malloc.h resides at /usr/include/malloc.h Didn't encounter that with a previews cvs-build from 2006-07-17. So far Cancel this report. Sorry, it's not the memory, it's the CPU which is taken. Probably no bug, as it gives resources free, if other program starts. A little bit strange, however, seems that a growing part of CPU - up to 99 % after an hour - is shown occupied even if there are no known actions with Emacs. __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Memory leak?
Jason Rumney schrieb: Andreas Roehler [EMAIL PROTECTED] writes: Emacs consumes all the memory by time, as `top' indicates. Sorry, it's not the memory, it's the CPU which is taken. Do you use semantic? There have been a couple of reports recently about semantic's idle timer functions taking 100% CPU on recent CVS versions of Emacs. This seems the reason. Thanks. Found a `semantic-idle-fix.el' on the net, will see if it helps. Have a nice day. __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Memory leak?
Seems something wrong with my build GNU Emacs 22.0.50.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2006-09-11 Emacs consumes all the memory by time, as `top' indicates. Config.log reports the following: configure:13037: checking malloc/malloc.h usability configure:13049: gcc -c -I/usr/X11R6/include -O2 -I/usr/X11R6/include -D_BSD_SOURCE conftest.c 5 conftest.c:133:27: error: malloc/malloc.h: No such file or directory De facto malloc.h resides at /usr/include/malloc.h Didn't encounter that with a previews cvs-build from 2006-07-17. So far Thanks __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: missing sit-for
Kept an old variant, because I changed something in order to have german names: (defvar calendar-day-name-array [Sonntag Montag Dienstag Mittwoch Donnerstag Freitag Samstag] Array of capitalized strings giving, in order, the day names.) instead of ;;(defvar calendar-day-name-array ;; [Sunday Monday Tuesday Wednesday Thursday Friday Saturday] ;; Array of capitalized strings giving, in order, the day names.) and (defvar calendar-month-name-array [Januar Februar März April Mai Juni Juli August September Oktober November Dezember] Array of capitalized strings giving, in order, the month names.) instead of ;;(defvar calendar-month-name-array ;; [January February March April May June ;; JulyAugust September October November December] ;; Array of capitalized strings giving, in order, the month names.) Probably there are better ways to do that. Why not use setq in your ~/.emacs file (instead of defvar in calendar.el)? Of course! BTW: As this tiny problem will be posed in many languages, a localisation effort seems worthwhile at least as a user option. What about to start a new thread with this question? Thanks! __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: missing sit-for
Richard Stallman schrieb: However, as I had a calendar.el in my path, from here resorts an error now: Symbol's value as variable is void: facemenu-unlisted-faces Are you saying this was caused by a spurious file? That would mean that we don't have a bug in Emacs, right? `calendar.el' from cvs-source seems ok. Kept an old variant, because I changed something in order to have german names: (defvar calendar-day-name-array [Sonntag Montag Dienstag Mittwoch Donnerstag Freitag Samstag] Array of capitalized strings giving, in order, the day names.) instead of ;;(defvar calendar-day-name-array ;; [Sunday Monday Tuesday Wednesday Thursday Friday Saturday] ;; Array of capitalized strings giving, in order, the day names.) and (defvar calendar-month-name-array [Januar Februar März April Mai Juni Juli August September Oktober November Dezember] Array of capitalized strings giving, in order, the month names.) instead of ;;(defvar calendar-month-name-array ;; [January February March April May June ;; JulyAugust September October November December] ;; Array of capitalized strings giving, in order, the month names.) Probably there are better ways to do that. Thanks! __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
missing sit-for
Hi, while trying `isearch' I get Symbol's function definition is void: sit-for. Thanks. __ Andreas Roehler ; In GNU Emacs 22.0.50.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2006-09-11 X server distributor `The X.Org Foundation', version 11.0.60802000 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: de_DE.UTF-8 locale-coding-system: utf-8 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 messages: and load others... Loading /usr/local/share/emacs/22.0.50/leim/leim-list.el (source)...done Source file `/usr/local/share/emacs/22.0.50/lisp/term/x-win.el' newer than byte-compiled file (emacs -Q --debug-init) For information about the GNU Project and its goals, type C-h C-p. isearch-lazy-highlight-new-loop: Symbol's function definition is void: sit-for Loading emacsbug... Source file `/usr/local/share/emacs/22.0.50/lisp/mail/sendmail.el' newer than byte-compiled file Loading regexp-opt...done Loading emacsbug...done ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: missing sit-for
Kim F. Storm schrieb: Andreas Roehler [EMAIL PROTECTED] writes: Hi, while trying `isearch' I get Symbol's function definition is void: sit-for. Try make maintainer-clean /configure make bootstrap Had to delete (rename) the directory, reload cvs-sources, ./configure, make bootstrap, make install. Now it works. However, as I had a calendar.el in my path, from here resorts an error now: Symbol's value as variable is void: facemenu-unlisted-faces Not serious for me at the moment; just to report it. Thanks a lot! __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: version-control customization
i.e. user sees only tag names while customizing, not the actual or chosen values. Why do you think this is a problem? The user sees three options, each clearly described. The problem IMO is a didactic one. Reading the manual, the user--that's me :)--keeps in mind three possible values. `t' `nil' `never' If he tries to set the variable according a chosen value, he gets this menu: Never If existing Always Should he remember, that for If existing the variable will be set to nil, if he checks the var afterwards? Probably. However, more easy seems to me a value-setting following logical pairs t = Always nil = Never conditional = If existing Given this, the tags may helpfully indicate the value being set. __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
version-control customization
Emacs Manual says , | 23.3.2.1 Numbered Backups | . | | The choice of single backup file or multiple numbered backup files is | controlled by the variable `version-control'. Its possible values are: | | `t' | Make numbered backups. | | `nil' | Make numbered backups for files that have numbered backups already. | Otherwise, make single backups. | | `never' | Never make numbered backups; always make single backups. ` which at a first glance seems not congruent with menu from files.el , | (defcustom version-control nil | *Control use of version numbers for backup files. | t means make numeric backup versions unconditionally. | nil means make them for files that have some already. | `never' means do not make them. | :type '(choice (const :tag Never never) | (const :tag If existing nil) | (other :tag Always t)) ` i.e. user sees only tag names while customizing, not the actual or choosen values. As providing a hint inside the tag as shown below. (const :tag If existing (nil) nil) (other :tag Always (t) t)) may lead into confusion--If existing isn't nil in the word sense--probably the cleanest way would be to put If existing the way as Never is handled - asigning a special symbol here, for example Conditional. __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
re-search-backward functions docu-string
Would consider it helpful, if the functions-docu-string to `re-search-backward' could give an explicit hint at the problem with regexp there, i.e. AFAIU repeats as [somechars]+ have no effect and are the same as [somechars]. As a result we see constructs as `skip-chars-backward somechars' after `re-search-backward' in the code. That's explained in the Elisp-Manual. However, the remark in the functions-docu-string Set point to the beginning of the match is easily overseen. So if it reads there something like In contrast to... I would esteem it much better. Probably also a hint there onto the Elisp Manual is appropriate. Thanks to all. __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
[Fwd: Re: [Fwd: Re: beginning-of-defun]]
---BeginMessage--- Richard Stallman schrieb: Have you had experience with a lot of beginners that got confused about this? No. Just a kind of active remembering. I am not yet convinced that we should change it. Our use of the term defun for editing commands has 30 years of history behind it, and I have not yet seen evidence that it is a problem. Propose to set aside the question. As this thread is splitted with that of thi, I'll switch there to continue. ---End Message--- ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: C-M-a
Stefan Monnier schrieb: Whereas C-M-e works fine and sends info via C-h k, C-M-a seems dead, just sends nothing, no reaction at all, no keyboard event, even not with C-h k followed by C-M-a. Probably caught by the window manager or something like that, Stefan Of course, thanks. Sorry for this posting. Kde took it. __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: C-M-a
Dieter Wilhelm schrieb: Andreas Roehler [EMAIL PROTECTED] writes: Emacs -q Whereas C-M-e works fine and sends info via C-h k, C-M-a seems dead, just sends nothing, no reaction at all, no keyboard event, even not with C-h k followed by C-M-a. With yesterdays CVS update it works for me emacs -q C-h k C-M-a GNU Emacs 22.0.50.3 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2006-07-17 on hans Thanks. This was my mistake. (Kde took the key.) __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: [Fwd: Re: beginning-of-defun]
Richard Stallman schrieb: Thanks for starting to explore this issue. Because it only finds `defun' calls, it fails to find other constructs that define functions or macros. Also, it would get rather confused when dealing with top-level forms that don't define functions at all: it just skips them. Correct my answer in this point. Here a hopefully better one: What was sent indeed was a `beginning-of-defun' in his true understanding (as I conceive that) - nothing more. After that we could have a function dealing with a group of function-forms in Emacs Lisp while extending the reg-rexp appropriate, i.e. a `beginning-of-function'. __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
C-M-a
Emacs -q Whereas C-M-e works fine and sends info via C-h k, C-M-a seems dead, just sends nothing, no reaction at all, no keyboard event, even not with C-h k followed by C-M-a. Have to cancel such a request and then get the explanation to C-g... BTW this is an old problem, I'm used to employ C-super-a to call `beginning-of-defun'. Not reported that because I did something with `beginning-of-defun' and thougt it my own result. Seems not so. The surprise is, that all other key and combinations work fine. In GNU Emacs 22.0.50.2 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2006-06-18 on kiste X server distributor `The X.Org Foundation', version 11.0.60802000 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: 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: C-h k C-g C-x 1 C-h k C-M-e M-x r e p o r t - e m a c s - b u g return Recent messages: Loading /usr/local/share/emacs/22.0.50/leim/leim-list.el (source)...done (emacs -Q --debug-init) For information about the GNU Project and its goals, type C-h C-p. Loading help-mode...done Loading help-fns...done Type C-x 1 to remove help window. [2 times] Loading emacsbug... Source file `/usr/local/share/emacs/22.0.50/lisp/mail/sendmail.el' newer than byte-compiled file Loading regexp-opt...done Loading emacsbug...done ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: [Fwd: Re: beginning-of-defun]
Richard Stallman schrieb: Thanks for starting to explore this issue. Because it only finds `defun' calls, it fails to find other constructs that define functions or macros. This would be the task of `beginning-of-form' - a more abstract utility. Also, it would get rather confused when dealing with top-level forms that don't define functions at all: it just skips them. Imagine to make a `beginning-of-form' working the way `thing-at-point' does: (beginning-of-form 'defvar) etc. The example suggests that this code avoids finding a match inside a string, but in fact there is no code to check that. It just checks that the (defun doesn't follow any non-indentation and that it includes a function name and argument list. Indeed. Will proceed here. Will it be possible to write a reg-exp which matches a functions definition reliable? Just couldn't get it until now. Probably a more prosperous way is to write genuine mode-functions, in Emacs Lisp using the list- and sexp-moving commands. I think it would be more useful to specially recognize certain top-level combining constructs, such as eval-when-compile and `when', and treat their subforms as Don't understand completely what this part means. Will reflect it further. defuns. IMO different meanings of `defun' in Emacs are the reason of a major difficulty for beginners (at least for non-programmers). Altogether I see no use and no reason to have it, beside of historical ones. To keep backward compatibility while replacing all `defun'-namings where `function' or just top-level-form is meant, it could be done while defining aliases at all cases where `function' is the right name. Of course the manuals must be corrected afterwards, but that's seems not a too complicated task, as quite often only a word is to change. ;; The mode should set this, if possible (defcustom beginning-of-function-return-value t Specify the return value if function succeeds: either t or the value of point :group 'lisp :type '(choice (const t) (sexp :tag Return function (point I think that feature is unhelpful complexity. It would be better to have just one return value convention. If the caller of beginning-of-function wants the value of point, it can do (if (beginning-of-function) (point)) Would not consider it a important question. Just need the point as return value and would save writing with it. `beginning-of-defun-raw' at the moment closes: and (re-search-backward ...) (progn (goto-char (1- (match-end 0 t)) Why the `t' instead of the more useful (point)? Isn't the value of point true anyway? As there are probably reasons to put it that way which I ignore, I didn't abolish it, just turned to (point). With the default as `t' the user won't remark a changing here. __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: [Fwd: Re: beginning-of-defun]
Thien-Thi Nguyen schrieb: From: Andreas Roehler [EMAIL PROTECTED] Date: Mon, 10 Jul 2006 15:46:02 +0200 It's not just for fun I entered this matter. `beginning-of-defun' is buggy - and a lot of forms which rely on it. given the discussion so far i remain unconvinced there is a bug. note however: i'm not stopping you from continuing, personally. if you post code as the way to propose the bug fix, it that will be easier to evaluate its merits. remember to not break callers (both included w/ emacs and external) of `beginning-of-defun'. thi Below a first draft with `beginning-of-function' aiming to work more precisely in Emacs Lisp. As already mentioned in the sources, to write a reliable `beginning-of-top-level-form' it's necessary to scan from the beginning of the buffer. This has been written, is the code available somewhere? `beginning-of-function' calls `beginning-of-defun' if not in Emacs Lisp. So it should work in all circumstances. New Features: - Customization of return value possible - t or value of point if successful. - Returns nil at the end or beginning of buffer. No push-mark then. - If starting with the searched form at place, just sends return value, moves only after repeated action or arg different from 1 Please have a look on it. Thanks __ Andreas Roehler Some examples I checked it with (defun bar () (interactive *) (message %s bar)) (defun bar () (interactive *)) (defun bar () (interactive *)) (defun foo () `beginning-of-function' should not pick a \ (defun\ construct inside a documentation string (interactive) (message %s bar)) ;;; ;; The mode should set this, if possible (defcustom modefunction-beginning-of-func nil If defined, specify your mode function to identify the beginning of a function :group 'lisp :type 'sexp) ;; The mode should set this (defcustom beginning-of-function-regexp ^[ \t]*(defun\\S(+\\s(\\S(*\\s) Regexp used by `beginning-of-function' to determine the beginning of a function :type '(choice (const nil) regexp) :group 'lisp) ;; (make-variable-buffer-local 'beginning-of-function-regexp) ;; The mode should set this, if possible (defcustom beginning-of-function-return-value t Specify the return value if function succeeds: either t or the value of point :group 'lisp :type '(choice (const t) (sexp :tag Return function (point (defcustom use-modefunction-beginning-of-func t Set it to nil, if `modefunction-beginning-of-func' doesn't work properly or is not defined. This takes only effect, if `modefunction-beginning-of-func' is defined in this mode. Otherwise it will be ignored. :type 'boolean :group 'lisp) (defcustom beginning-of-function-eob-return-nil t If t, `beginning-of-function' will return nil if called at the beginning or the end of buffer. Also it will not set the mark then. :type 'boolean :group 'lisp) ;; The mode should set this, if possible (defcustom force-beginning-of-function-regexp nil Set it to t, if `beginning-of-function-regexp' should be used in any case, ie if you are not in Emacs Lisp, but the reg-exp is OK. You may customize `beginning-of-function-regexp'). :type 'boolean :group 'lisp) (defun beginning-of-function (optional arg) Move backward to the beginning of a function. With ARG, do it that many times. Negative arg -N means move forward to Nth following beginning of function. Returns t unless search stops due to beginning or end of buffer. If Variables `use-modefunction-beginning-of-func' `modefunction-beginning-of-func' is non-nil, its value is called as a function to find the function's beginning. If not in Emacs Lisp-mode, `beginning-of-defun' is called anyway. (interactive p) ;; mark questions (or (not (eq this-command 'beginning-of-function)) (eq last-command 'beginning-of-function) (and transient-mark-mode mark-active) (when beginning-of-function-eob-return-nil (and ( 0 arg) (bobp)) (and ( 0 arg) (eobp))) (push-mark)) (beginning-of-function-raw arg)) (defun beginning-of-function-raw (optional arg) Move point to the character that starts a function. If variable `beginning-of-function-func' is non-nil, its value is called as a function to find the function's beginning. If not in Emacs Lisp-mode, `beginning-of-defun' is called anyway. (interactive p) (let ((arg (or arg 1))) (if (and modefunction-beginning-of-func use-modefunction-beginning-of-func) (if ( (setq arg (or arg 1)) 0) (dotimes (i arg) (funcall modefunction-beginning-of-func)) (end-of-function (- arg))) (and (not (eobp)) ( arg 1) (forward-char -1)) (if (or ;; while developing: specify here a list with ;; modes already provided with an new ;; `beginning-of-function-regexp' (string= major-mode emacs-lisp-mode) force-beginning-of-function-regexp) (progn (unless (eq last-command 'beginning-of-function
Elisp texi 2.3.13 Function Type
Having difficulties of understanding, I ask, if it could be said another way (proposals below with `-' to cancel, `+~' added/changed text) , | 2.3.13 Function Type | | | Just as functions in other programming languages are executable, Lisp | function objects are pieces of executable code. However, functions in | Lisp are primarily Lisp objects, and only secondarily the text which | represents them. ` - Just as functions in other programming languages ;; Doesn't contribute real information IMO; if at all, ;; the point that some other languages don't use this ;; terminus should be mentioned here +~ Regarding functions we have always to decide if we referring to them as the printed representation of a execution routine--i.e. as pieces of executable code defining a function when evaluated--or if we speak of the behavior of an already read-in (evaluated and interned) function, which might be called for execution. - However, functions in Lisp are primarily Lisp objects, and only secondarily the text which represents them. ;; IMO that remark makes no sense: while editing, it's ;; the textual representation which matters. Internals ;; of computation are fairly not the same as writing ;; programs; however, would not employ `primarily' here ;; to mark the difference. __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: [Fwd: Re: beginning-of-defun]
Thien-Thi Nguyen schrieb: Andreas Roehler [EMAIL PROTECTED] writes: `defun' is a special form with a special meaning in emacs-lisp yes, but defun is also in common parlance a top-level form. these two meanings are congruent but not identical. you have to sort of alternatively squint and relax your ears to hear the similarity... If you don't discriminate between termini top-level-form, function (which is a known name in many programing languages but not in all) and the special Emacs Lisp form defun, you will run into confusion when the difference matters. Think it's disturbing to introduce a different meaning employing the same name. you get used to being disturbed w/ a little practice. What about to take it as a chance, not being used to? Certainly a function `beginning-of-top-level-form' is useful. However, it should be callable separate from `beginning-of-defun' and vice versa. here is a (self-testable in the right context ;-) toy: (global-set-key \C-\M-a (defun beginning-of-defun-just-defun-really-i-mean-it! () (interactive) (let ((beginning-of-defun-function (lambda () (search-backward (defun (point-min) t (beginning-of-defun This form will fail, should there be a string (defun somewhere in a docu or other included text before the real beginning of function. Also its focus is on the less general form in this context. Propose a top-down proceeding while re-designing venerable `beginning-of-defun' function. beginning-of-top-level-form beginning-of-form ;; before and under point beginning-of-function The latter would - if in Emacs Lisp-mode - be provided with a spec to indentify the defun-form `beginning-of-defun' should work right out of the box at least in Emacs Lisp. That's easily to be done - if the need is recognised so far. it works for my understanding of defun. more importantly, my understanding of defun is shared by many people, most of whom are probably uninclined to add something like the above function to emacs. thi The author of edebug.el at least seems conscious of the problem. Doesn't seem an accident he named it edebug-eval-top-level-form providing just an alias (defalias 'edebug-defun 'edebug-eval-top-level-form) Also I read there (defun edebug-read-top-level-form () (let ((starting-point (point))) (end-of-defun) (beginning-of-defun) ... It's not just for fun I entered this matter. `beginning-of-defun' is buggy - and a lot of forms which rely on it. (unless t (defun foo () Explore the right \(defun-funktion\ (interactive) (message %s baz))) ^ M-x beginning-of-defun == (unless t ^ (defun foo () Explore the right \(defun-funktion\ (interactive) (message %s baz))) When the [ \t]* as regexp-prefix is set M-x beginning-of-defun == (unless t (defun foo () Explore the right \(defun-funktion\ (interactive) (message %s baz))) ^ __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: [Fwd: Re: beginning-of-defun]
Thien-Thi Nguyen schrieb: From: Andreas Roehler [EMAIL PROTECTED] Date: Mon, 10 Jul 2006 15:46:02 +0200 It's not just for fun I entered this matter. `beginning-of-defun' is buggy - and a lot of forms which rely on it. given the discussion so far i remain unconvinced there is a bug. note however: i'm not stopping you from continuing, personally. if you post code as the way to propose the bug fix, it that will be easier to evaluate its merits. remember to not break callers (both included w/ emacs and external) of `beginning-of-defun'. thi There are not many, but some cases, where `beginning-of-defun' fails To use a real existing inner form (cursor at roof-sign): (when (boundp 'bar) (defun e-r-t-l () (let ((starting-point (point))) (end-of-defun) (beginning-of-defun) (prog1 (edebug-read-and-maybe-wrap-form) ;; Recover point, but only if no error occurred. (goto-char starting-point) ^ M-x eval-defun == nil Evaluation fails caused by failure of (beginning-of-defun) (defun e-r-t-l () (let ((starting-point (point))) (end-of-defun) (beginning-of-defun) (prog1 (edebug-read-and-maybe-wrap-form) ;; Recover point, but only if no error occurred. (goto-char starting-point ^ M-x eval-defun == e-r-t-l However, it should also work in the first case. As I need it to call from programs, it should be possible to rely on. Hopeful to send some scratch next days. __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
beginning-of-defun
Problems with (beginning-of-defun): Cursor at roof-sign (when t (defun foo () (interactive) (message %s baz))) ^ M-x beginning-of-defun == (when t ^ (defun foo () (interactive) (message %s baz))) Wrong, as at the start of the enclosing form. Set `defun-prompt-regexp' via customize at [ \t]* (when t (defun foo () (interactive) (message %s baz))) ^ M-x beginning-of-defun == (when t (defun foo () (interactive) (message %s baz))) ^ Also wrong: cursor at the beginning of line now. The reason seems the conception of the variable `defun-prompt-regexp' which solely takes spaces before the defuns beginning in consideration. It could be avoided, if this var would take instead of `a regexp to ignore before a defun' a regexp `describing the beginning of a defun' Then we could specify [ \t]*(defun for example in Emacs Lisp mode and it would not fail if we are inside a defun or just after it already. __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
[Fwd: Re: beginning-of-defun]
---BeginMessage--- Thien-Thi Nguyen schrieb: Andreas Roehler [EMAIL PROTECTED] writes: Wrong, as at the start of the enclosing form. well, defun here actually means top-level form; the command works w/ all kinds of sexps, whether or not they are actually `defun's. `defun' is a special form with a special meaning in emacs-lisp , | 12.4 Defining Functions | === | | We usually give a name to a function when it is first created. This is | called defining a function, and it is done with the `defun' special | form. | | -- Spezielle Form: defun name argument-list body-forms | `defun' is the usual way to define new Lisp functions. ` Think it's disturbing to introduce a different meaning employing the same name. This pertains to the Emacs Manual were is said , | 31.2.2 Moving by Defuns | --- | | These commands move point or set up the region based on top-level major | definitions, also called defuns. ` A `top-level-form' might be a defun, but is a far more general terminus with his value at his own AFAIU. Certainly a function `beginning-of-top-level-form' is useful. However, it should be callable separate from `beginning-of-defun' and vice versa. the way to make the behavior arbitrarily more precise is to customize `beginning-of-defun-function'. for example, see `python-beginning-of-defun' in progmodes/python.el. `beginning-of-defun' should work right out of the box at least in Emacs Lisp. That's easily to be done - if the need is recognised so far. __ Andreas Roehler ---End Message--- ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: texinfo-format-buffer text.texi
Eli Zaretskii schrieb:
Date: Tue, 04 Jul 2006 07:54:34 +0200
From: Andreas Roehler [EMAIL PROTECTED]
Calling `texinfo-format-buffer' at text.texi
produces a line
@anchor-yes-refill{Definition of sentence-end-double-space}
which is probably not correct. (Line 1408 now)
AFAIR, `texinfo-format-buffer' is unmaintained and doesn't support all
the features of the latest versions of the Texinfo language. Don't
use it; use `makeinfo' instead. (I believe the Texinfo manual says
that as well somewhere.)
makeinfo-buffer doesn't work at all with
GNU Emacs 22.0.50.2 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of
2006-06-18
it even kills the output. Surprisingly all messages in
German. Program complains references at non-existing
nodes. Error-messages end with:
makeinfo: Entferne Ausgabe-Datei „../info/text“ wegen Fehler; --force
benutzen, um diese beizubehalten.
Compilation exited abnormally with code 1 at Wed Jul 5 09:07:36
The whole output at the end
Running `makeinfo-buffer' with Edebug I get the
following messages:
Loading edebug...done
Edebug: makeinfo-region
makeinfo-region
Edebug: makeinfo-next-error
makeinfo-next-error
Edebug: makeinfo-compile
makeinfo-compile
Edebug: makeinfo-compilation-sentinel-region
makeinfo-compilation-sentinel-region
Edebug: makeinfo-current-node
makeinfo-current-node
Edebug: makeinfo-buffer
makeinfo-buffer
Edebug: makeinfo-compilation-sentinel-buffer
makeinfo-compilation-sentinel-buffer
Edebug: makeinfo-recenter-compilation-buffer
makeinfo-recenter-compilation-buffer
Wrote /home/speck/texte/20060705-an-makeinfo.txt
Press Return to bury the buffer list
Result: /home/speck/emacs/lispref/text.texi
Result: nil [3 times]
Result: 1 (#o1, #x1, ?\C-a) [2 times]
Result: 0 (#o0, #x0, ?\C-@)
Result: 4639 (#o11037, #x121f) [3 times]
Result: 292 (#o444, #x124)
Result: 280 (#o430, #x118)
Result: 292 (#o444, #x124)
Result: #(../info/text 0 12 (fontified t))
Result: /home/speck/emacs/info/text [5 times]
Result: nil
Result: 1 (#o1, #x1, ?\C-a)
Result: nil
Result: Top [4 times]
Result: makeinfo
Result: --fill-column=70
Result: /home/speck/emacs/lispref/text.texi
Result: makeinfo --fill-column=70 /home/speck/emacs/lispref/text.texi
[2 times]
Result: #buffer *compilation* [2 times]
Result: nil
Result: compilation-next-error-function [3 times]
Result: #buffer *compilation*
Result: nil
Result: makeinfo-compilation-sentinel-buffer
Wrong type argument: processp, nil
error: Cannot return from the debugger in an error
;;;
With Emacs -q it's the same:
Here the bug-report:
In GNU Emacs 22.0.50.2 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
of 2006-06-18 on kiste
X server distributor `The X.Org Foundation', version 11.0.60802000
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: de_DE.UTF-8
locale-coding-system: utf-8
default-enable-multibyte-characters: t
Major mode: Texinfo
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:
help-echo C-x C-f e m tab / l i s p r e f tab
t e x t . t x backspace e x i return M-x m a k
e i n f o - b u f f e r return M-x r e p o r t -
e m a c s - b u g return
Recent messages:
text.texi has auto save data; consider M-x recover-this-file
Loading texinfo...
Loading regexp-opt...done
Loading easymenu...done
Loading texinfo...done
Loading vc-cvs...done
Loading makeinfo...done
Loading emacsbug...
Source file `/usr/local/share/emacs/22.0.50/lisp/mail/sendmail.el' newer
than byte-compiled file
Loading emacsbug...done
Here the full contents of *compilation*
-*- mode: compilation; default-directory: ~/emacs/lispref/ -*-
Compilation started at Wed Jul 5 09:37:16
makeinfo --fill-column=70 /home/speck/emacs/lispref/text.texi
/home/speck/emacs/lispref/text.texi:7: nächstesverweis auf nicht
existierenden Knoten „Non-ASCII Characters“ (vielleicht @section statt
@subsection o.ä.?).
/home/speck/emacs/lispref/text.texi:7: vorigesverweis auf nicht
existierenden Knoten „Markers“ (vielleicht @section statt @subsection
o.ä.?).
/home/speck/emacs/lispref/text.texi:7: aufwärtsverweis auf nicht
existierenden Knoten „Top“ (vielleicht @section statt @subsection o.ä.?).
/home/speck/emacs/lispref/text.texi:4353: Querverweis auf nicht
existierenden Knoten „Overlay Properties“ (vielleicht @section statt
@subsection o.ä.?).
/home/speck/emacs/lispref/text.texi:4146: Querverweis auf nicht
existierenden Knoten „Coding Systems“ (vielleicht @section statt
@subsection o.ä.?).
/home/speck/emacs/lispref/text.texi:4141: Querverweis auf nicht
existierenden Knoten „Text Representations“ (vielleicht @section statt
@subsection o.ä
Re: texinfo-format-buffer text.texi
Richard Stallman schrieb: makeinfo --fill-column=70 /home/speck/emacs/lispref/text.texi That file is not valid input, since it is just part of a manual. Try it with elisp.texi instead. With the complete elisp.texi it will work. Just took that file, as you asked Would someone please check lispref/text.texi for accuracy? To check a single texi I called `texinfo-format-buffer' before. BTW I like `texinfo-format-buffer' because it runs out of the box, you have not to switch to shell or something like that, no extra opening etc. The errors are mince; just reported them, because I wasn't sure where the few errors are coming from - could be something in the text.texi to correct still. Would be great to keep `texinfo-format-buffer' maintained. Will try to help this, but have to learn a little bit more about tex still. __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
delete-indentation - text.texi
I'm afraid, `delete-indentation' is labeled from a side affect of two other functions: join-lines and fixup-whitespace, implemented in C however. From a function `delete-indentation' I wouldn't expect the behavior as it is now (and shown below) -- Buffer: foo -- When in the course of human -!-events, it becomes necessary -- Buffer: foo -- (delete-indentation) = nil -- Buffer: foo -- When in the course of human-!- events, it becomes necessary -- Buffer: foo -- rather -- Buffer: foo -- When in the course of human -!-events, it becomes necessary -- Buffer: foo -- (delete-indentation) = nil -- Buffer: foo -- When in the course of human -!-events, it becomes necessary -- Buffer: foo -- Deleting indentation has no inert connection with deleting newline-chars, AFAIU. Altogether the false `delete-indentation'-function takes the place of the real one in this bad world! :) __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Emacs Info node head Indexes
IMO Emacs Info node head == Indexes (nodes containing large menus) == might be misleading, as the user may understand that the index entries pertain to nodes containing large menus only. AFAIU that's not the focus. Probably its intended as a hint, describing the contents of these indexes. Consider that not as worthwhile in relation to the danger of misinterpreting. __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
query-replace-regexp
~/emacs/src/emacs --debug-init With M-x `query-replace-regexp' I get an error: query-replace-read-from: Wrong number of arguments: #subr read-from-minibuffer, 8 __ Andreas Roehler ;; In GNU Emacs 22.0.50.3 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2006-06-05 X server distributor `The X.Org Foundation', version 11.0.60802000 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: 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: M-x q u e r tab - r e g tab return M-x r e p o r t - e m a c s - b u g return Recent messages: Source file `/home/speck/emacs/lisp/term/x-win.el' newer than byte-compiled file (/home/speck/emacs/src/emacs -Q --debug-init) For information about the GNU Project and its goals, type C-h C-p. Loading kmacro...done kmacro-call-macro: No kbd macro has been defined Quit query-replace-read-from: Wrong number of arguments: #subr read-from-minibuffer, 8 Loading emacsbug... Loading regexp-opt...done Loading emacsbug...done ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
write-abbrev-file
Two related bugs in abbrev.el M-x `edit-abbrevs', narrowing the buffer, calling `edit-abbrevs-redefine'. Then `write-abbrev-file' kills all abbrevs except the visible one in the narrowed buffer. At least this behavior misses the Manual where is written: writes a description of all current abbrev definitions. Happens even if the buffer has been widened before, but not, if `edit-abbrevs-redefine' has been called again. Bug was remarked only with an explicit `write-abbrev-file' after `edit-abbrevs-redefine', but not forcibly (maybe sometimes also?) if Emacs was closed and abbrevs written at this occasion. Proposed fix below. Also with this fix installed, the question `save-abbrevs?' while closing Emacs has to be denied if `write-abbrev-file' was called in this session; otherwise all abbrevs will be deleted and only void abbrev tables saved. This seems an other bug. diff -c /home/speck/progarbeit/weitere/easy/abbrev.el ~/emacs/lisp/abbrev.el *** /home/speck/progarbeit/weitere/easy/abbrev.el 2006-05-05 20:00:16.0 +0200 --- /home/speck/emacs/lisp/abbrev.el2006-04-30 08:58:26.0 +0200 *** *** 227,235 abbrev-file-name))) (or (and file ( (length file) 0)) (setq file abbrev-file-name)) - ;; 20060505 [EMAIL PROTECTED] - (edit-abbrevs-redefine) - ;; end of inserted section (let ((coding-system-for-write 'emacs-mule)) (with-temp-file file (insert ;;-*-coding: emacs-mule;-*-\n) --- 227,232 In GNU Emacs 22.0.50.2 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2006-02-23 on kiste X server distributor `The X.Org Foundation', version 11.0.60802000 Important settings: value of $LC_ALL: C 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: de_DE.UTF-8 locale-coding-system: nil default-enable-multibyte-characters: t Major mode: Edit-Abbrevs Minor modes in effect: 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: M-x e d i t - a b b r e v s return C-SPC C-s m o d e - a b b C-s up C-x n n y M- down down down right right right t C-x C-s M-x w r i t e - a b b r e tab return return M-x r e o p backspace backspace p o r t - e m tab return Recent messages: For information about the GNU Project and its goals, type C-h C-p. Mark set Mark saved where search started Loading novice...done Loading help-mode (compiled; note, source file is newer)...done Type y, n, ! or SPC (the space bar): Mark set Loading emacsbug... Loading regexp-opt...done Loading emacsbug...done ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: read-abbrev-file (2)
Richard Stallman wrote: For instance you couldn't call `quietly-read-abbrev-file' interactively at the moment, Why would you want to? Given that you're typing a command, how does it hurt you to use read-abbrev-file instead? The reason, why I care for this kind of - tiny or basic - matters - is, as explained already: an essay to meet the - naturally partly unrealistic - expectations of beginners, avoid bewildering and so on. I mean `quietly-read-abbrev-file' is a good idea in the case, the user keeps just one abbrev-file (as I do). So why get prompted for the name? All the best __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: read-abbrev-file (2)
Richard Stallman wrote: What about to use this until then?: ;(defalias 'read-abbrev-file 'ar-read-abbrev-file) ;(defalias 'quietly-read-abbrev-file 'ar-quietly-read-abbrev-file) (defun ar-read-abbrev-file (optional file) I do not understand. Who are you suggesting this to? What purpose is this code meant to serve? For instance you couldn't call `quietly-read-abbrev-file' interactively at the moment, because `interactive' is commented out in the function presently in abbrev.el. With the constructs given it's available. __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: read-abbrev-file (2)
Richard Stallman wrote: I cannot reproduce the problem. It only occurs at the very beginning, after starting Emacs. Maybe it has been fixed since February. Does it fail in the latest sources? Yes, noticed the change. If so, can you try to debug it by running under GDB and putting a breakpoint at Fsignal? Will try that, but it would take some time. I'm not familiar with. __ Andreas Roehler What about to use this until then?: ;(defalias 'read-abbrev-file 'ar-read-abbrev-file) ;(defalias 'quietly-read-abbrev-file 'ar-quietly-read-abbrev-file) (defun ar-read-abbrev-file (optional file) Read abbrev definitions from file written with `write-abbrev-file'. Optional argument FILE is the name of the file to read; it defaults to the value of `abbrev-file-name' (interactive (list (read-from-minibuffer (concat default: abbrev-file-name : (if (or (string-match [ \t]+ file) (string= file)) (setq file abbrev-file-name)) (load file nil) (setq abbrevs-changed nil)) (defun ar-quietly-read-abbrev-file (optional file) Read abbrev definitions from file written with `write-abbrev-file'. Optional argument FILE is the name of the file to read; it defaults to the value of `abbrev-file-name'. Does not display any message. (interactive) (let ((file file)) (unless (stringp file) (setq file abbrev-file-name)) (load file nil t) (setq abbrevs-changed nil))) ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: read-abbrev-file function
Richard Stallman wrote: Thanks for reporting the bug. I wrote a cleaner fix. Please send copy of the fix, couldn't see it in the CVS-Rep. AFAIS there is a related bug in abbrev.el, the fix depends on the way `read-abbrev-file' is written: ;; Bugged: quietly-read-abbrev-file: ;; old: Interactive calls have been disabled from ;; quietly-read-abbrev-file, probably to avoid ;; disturbance caused by the ;; `f'-interactive-kontroll-letter bug ;; new: `interactive' reinstalled (defun quietly-read-abbrev-file-ar (optional file) Read abbrev definitions from file written with `write-abbrev-file'. Optional argument FILE is the name of the file to read; it defaults to the value of `abbrev-file-name'. Does not display any message. (interactive) (read-abbrev-file-ar file t)) __ Andreas Roehler PS.: Meanwhile I rewrote `read-abbrev-file' with `cond', so its better to read: (defun read-abbrev-file-ar (optional file quietly) Read abbrev definitions from file written with `write-abbrev-file'. Optional argument FILE is the name of the file to read; it defaults to the value of `abbrev-file-name'. Optional second argument QUIETLY non-nil means don't print anything. (interactive) (let* ((abbrevs-to-load (cond ((when (boundp file)) file) ;; if quietly was specified but no file given, ;; load default abbrev-file ((when quietly abbrev-file-name)) ;; clear unavertedly inserted whitespaces ((string-strip (read-from-minibuffer (concat default: abbrev-file-name)) t t) (when (string= abbrevs-to-load ) (setq abbrevs-to-load abbrev-file-name)) (load abbrevs-to-load nil quietly)) (setq abbrevs-changed nil)) ;; Function needed to clear unavertedly by users ;; inserted whitespaces ;; Source: comment-string-strip, newcomment.el, GNU Emacs 22.0.50.1;; (defun string-strip (str beforep afterp) Strip STR of any leading (if BEFOREP) and/or trailing (if AFTERP) space. (string-match (concat \\` (if beforep \\s-*) \\(.*?\\) (if afterp \\s-*\n?) \\') str) (match-string 1 str)) ;; end ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: read-abbrev-file function
Richard Stallman wrote: Thanks for reporting the bug. I wrote a cleaner fix. Until it's in the CVS-rep; Here the present state of art: ;; Bugged: read-abbrev-file function in abbrev.el ;; The `(interactive f' - kontroll-letter takes just ;; the current buffer-file if you quit the demand ;; with RET. That's not what you want: If the file is ;; already open, there is no need to call ;; `read-abbrev-file', the `default-abbrev-file' should ;; be called in the case of no specified user input. ;; Fixed: ;; Loads the default-abbrev-file unless no file is specified. (defalias 'read-abbrev-file 'read-abbrev-file-ar) (defun read-abbrev-file-ar (optional file quietly) Read abbrev definitions from file written with `write-abbrev-file'. Optional argument FILE is the name of the file to read; it defaults to the value of `abbrev-file-name'. Optional second argument QUIETLY non-nil means don't print anything. (interactive (list ;; clear unavertedly inserted whitespaces (string-strip (read-from-minibuffer (concat default: abbrev-file-name)) t t))) (load (if (and file ( (length file) 0)) file abbrev-file-name) nil quietly) (setq abbrevs-changed nil)) ;; Function needed to clear unavertedly by users ;; inserted whitespaces ;; Source: comment-string-strip, newcomment.el, GNU Emacs 22.0.50.1;; (defun string-strip (str beforep afterp) Strip STR of any leading (if BEFOREP) and/or trailing (if AFTERP) space. (string-match (concat \\` (if beforep \\s-*) \\(.*?\\) (if afterp \\s-*\n?) \\') str) (match-string 1 str)) ;; Bugged: quietly-read-abbrev-file: ;; old: ;; Interactive calls have been disabled from ;; quietly-read-abbrev-file, probably to avoid the bug ;; with the `f'-interactive-kontroll-letter ;; new: `interactive' reinstalled (defun quietly-read-abbrev-file-ar (optional file) Read abbrev definitions from file written with `write-abbrev-file'. Optional argument FILE is the name of the file to read; it defaults to the value of `abbrev-file-name'. Does not display any message. (interactive) (read-abbrev-file-ar file t)) ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
read-abbrev-file function
;; Bugged: read-abbrev-file function in abbrev.el ;; The `(interactive f' - kontroll-letter takes just ;; the current buffer-file if you quit the demand ;; with RET. That's not what you want: If the file is ;; already open, there is no need to call ;; `read-abbrev-file', the `default-abbrev-file' should ;; be called in the case of no specified user input. ;; Proposed fix: ;; Loads the default-abbrev-file unless no file is specified. (defalias 'read-abbrev-file 'read-abbrev-file-ar) (defun read-abbrev-file-ar (optional file quietly) Read abbrev definitions from file written with `write-abbrev-file'. Optional argument FILE is the name of the file to read; it defaults to the value of `abbrev-file-name'. Optional second argument QUIETLY non-nil means don't print anything. (interactive) (let* ((abbrevs-to-load file) (abbrevs-to-load (if abbrevs-to-load abbrevs-to-load ;; clear unavertedly inserted whitespaces (string-strip (read-from-minibuffer (concat (default: abbrev-file-name) )) t t))) (abbrevs-to-load (if (string= abbrevs-to-load ) abbrev-file-name abbrevs-to-load))) (load abbrevs-to-load nil quietly)) (setq abbrevs-changed nil)) ;; Function needed to clear unavertedly ;; inserted whitespaces ;; Source: comment-string-strip, newcomment.el, GNU Emacs 22.0.50.1;; (defun string-strip (str beforep afterp) Strip STR of any leading (if BEFOREP) and/or trailing (if AFTERP) space. (string-match (concat \\` (if beforep \\s-*) \\(.*?\\) (if afterp \\s-*\n?) \\') str) (match-string 1 str)) ;; end ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
edit-abbrevs questions - new edit-sorted-abbrevs function
Herewith a more detailed description of already mentioned problems with `edit-abbrevs' - proposed solutions inclusive. 1) in contrast with the documentation, which declares edit-abbrevs and list-abbrevs to differ only in displaying, I see no way to call edit-abbrevs with an option `local'. `edit-abbrevs' starts at the top of the *Abbrev*-Buffer with the complete listing of all abbrevs below. Presently its up to the user to select the abbrev-table to edit. As the mode-line of `my-file.el' I switched from displayed (Emacs-Lisp Abbrev), I concluded to edit the `(emacs-lisp-mode-abbrev-table)' - what was a mistake. Editing there had no effect, I had to edit `(lisp-mode-abbrev-table)', only then are new definitions afterwards are available. 2) if editing *Abbrevs* with narrowed buffer, a call of edit-abbrevs-redefine on this narrowed buffer deletes all other abbrevs without warning. That's dangerous. Proposed Solutions: AFAIS there is a quick solution to #2 by providing `(widen)' to `edit-abbrevs-redefine': *** ar-emacs/lisp/abbrev.el 2006-03-20 10:43:26.0 +0100 --- emacs/lisp/abbrev.el2006-03-17 21:02:38.0 +0100 *** *** 159,165 (defun edit-abbrevs-redefine () Redefine abbrevs according to current buffer contents. (interactive) - (widen) (define-abbrevs t) (set-buffer-modified-p nil)) --- 159,164 Proposal to #1: To facilitate the selection of the abbrev-table to edit, AFAIS there is a minor and a major solution. The latter I conceive in reverting the global-abbrev-editing approach into an table-by-table style, always editing and re-writing a section in order to avoid loading a big abbrev-file at once. The minor solution would always load the complete abbrev_defs, - as its the current state - introduce narrowing and use `(abbrev-table-name local-abbrev-table)' to set the `region-beginning'. Together with the already described introduction of `widen' there will be no harm. My results so far in the minor way (the option now is global, not local, as I usually need the mode-abbrevs to edit:) (defun edit-sorted-abbrevs (optional global) (interactive P) (save-excursion (let ((table local-abbrev-table) (table-name (abbrev-table-name local-abbrev-table))) (set-buffer (get-buffer-create *Abbrevs*)) (switch-to-buffer *Abbrevs*) (erase-buffer) (dolist (table abbrev-table-name-list) (insert-abbrev-table-description table t)) (goto-char (point-min)) (set-buffer-modified-p nil) (edit-abbrevs-mode) (unless global (re-search-forward (format (%s) table-name) nil t 1) (let ((table-head (line-beginning-position)) (start (progn (re-search-forward ^\ nil t 1) (match-beginning 0))) (end (save-excursion (re-search-forward ^[ \t]*(.+mode-abbrev-table nil t 1) (forward-line -1) (point (narrow-to-region start end) ;; multiline-abbrevs will make trouble when sort (save-excursion (if (re-search-forward ^[A-Za-zäöüÄÖÜß0-9 \t] nil t 1) (message %s %s Cann't sort. Don't declare multiline-abbrevs. Error at point: (point))) (beginning-of-line) (sort-lines nil start end)) (widen) (narrow-to-region table-head end) (goto-char (point-min)) (forward-line 1) (just-one-empty-line))) (when global (widen) (point-min) __ Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
edit-abbrevs-redefine - user-error or bug
Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Two problems: 1) after abbrevs-edit - `edit-abbrevs' - followed by `edit-abbrevs-redefine' and switched back: the new definitions are not available. It still ignores the new definded, solely expands the old one. 2) if editing abbrevs with narrowed buffer and calling edit-abbrevs-redefine on the narrowed buffer, it deletes all other abbrevs. Is there a way out? Is it a bug? Thanks Andreas Roehler PS.: - Found a solution already in changing the code and may send the diffs. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
void-function mode-line-mode-name ?
After inserting (:eval (version)) in my mode-line-format via customize I get an Error during redisplay: (void-function mode-line-mode-name) with GNU Emacs 22.0.50.2 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2006-02-23 however its shown correctly. No error is signaled with GNU Emacs 21.4.3 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2006-02-26 Andreas Roehler PS.: Here the section from my ~/.emacs '(mode-line-format (quote (#(- 0 1 (help-echo mouse-1: select window, mouse-2: delete others, mouse-3: delete ...)) mode-line-mule-info mode-line-modified mode-line-frame-identification mode-line-buffer-identification #(0 3 (help-echo mouse-1: select window, mouse-2: delete others, mouse-3: delete ...)) (:eval (version)) global-mode-string #( %[( 0 6 (help-echo mouse-1: select window, mouse-2: delete others, mouse-3: delete ...)) (:eval (mode-line-mode-name)) mode-line-process minor-mode-alist #(%n 0 2 (help-echo mouse-2: widen local-map (keymap (mode-line keymap (mouse-2 . mode-line-widen) #()%]-- 0 5 (help-echo mouse-1: select window, mouse-2: delete others, mouse-3: delete ...)) (which-func-mode ( which-func-format #(-- 0 2 (help-echo mouse-1: select window, mouse-2: delete others, mouse-3: delete ... (line-number-mode (#(L%l 0 3 (help-echo mouse-1: select window, mouse-2: delete others, mouse-3: delete ...)) #(-- 0 2 (help-echo mouse-1: select window, mouse-2: delete others, mouse-3: delete ... (column-number-mode (#(C%c 0 3 (help-echo mouse-1: select window, mouse-2: delete others, mouse-3: delete ...)) #(-- 0 2 (help-echo mouse-1: select window, mouse-2: delete others, mouse-3: delete ... (-3 . #(%p 0 2 (help-echo mouse-1: select window, mouse-2: delete others, mouse-3: delete ...))) #(-%- 0 3 (help-echo mouse-1: select window, mouse-2: delete others, mouse-3: delete ...) ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Fwd: fill-region eats white-space after sentence end
Stefan Monnier wrote: I've just tried it and can't reproduce it. I get: Demontage nahezu all dessen, was fr?her als Recht galt, entgangen ist. Die einen haben ihre Unterwerfungshaltung noch gesteigert, die anderen Can you give a more precise recipe, starting from emacs -Q? Indeed it don't happen, if started with emacs -Q . Can you show us the value of the following variables in the buffer where the problem appears? - sentence-end - sentence-end-base - sentence-end-double-space - sentence-end-without-space Stefan - fill-region eats whitespace GNU Emacs 22.0.50.2 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2006-02-23 -- Before fill-region -- Emacs is the extensible, customizable, self-documenting real-time display editor. This Info file describes how to edit with Emacs and -- After fill-region -- Emacs is the extensible, customizable, self-documenting real-time display editor.This Info file describes how to edit with Emacs and Here the vars: - sentence-end: [.?!] - sentence-end-base: [.?!][]\'””)}]* - sentence-end-double-space: t - sentence-end-without-space: 。．？！。．？！。．？！。.?! As said: if I'm the only one... solved it at my-emacs. Thanks Andreas PS.: After start I always get: Error in post-command-hook: (void-variable self-insert-command) ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Multi- and single-line comment default
Presently commenting of single lines in C-Mode and others per default uses multiline comment signs as shown below /* Example code */ Seems no way to change this via customization, also after changing comment-style-Var to `plain' or `aligned', same result. Better default would be // Example code in the case, there is just a single line to comment. BTW: Suggest to change the default from region-transient-mark-mode-requiring to an line-oriented behavior, which respects region per default if transient-mark-mode is on. A draft of such an line-oriented implemention is given below. (Please check it and report bugs or further suggestions, if there are some). There should be a customization-utility, what to do if single-line-comments follow each other: to replace by a multiline-sign silently or not. Also needed: single-line-comments-only (nil or t). Per default it should switch to multiline-signs, if an active regions spreads over. So far. Andreas Roehler +49306927863 ;;; ar-comment-uncomment --- comments or uncomments a line or region according to state before. With key pressed, continues with next line. With arg it copies and reinserts last line. Works on region if region is active and no arg given. ;; author: Andreas Roehler, ;; Todo: replaces in C (and others probably) ;; // Zeilenkommentar, neu ab C99-ANSI ;; with ;; /* Zeilenkommentar, neu ab C99-ANSI */ ;; Should change that. (require 'newcomment) (global-set-key [M-kp-6] 'ar-comment-uncomment) (defun ar-comment-uncomment (optional arg) Comments or uncomments a line according to state before. Calls `comment-region' (unless line is already commented, in which case it calls `uncomment-region'). With key pressed, continues with next line. Works on region if mark and transient-mark-mode are active. With arg greater than 1 works on arg lines, neglecting region. With arg equal 1 copies, comments/uncomments and reinserts line. (interactive *P) (comment-normalize-vars) (let ((arg (if arg (prefix-numeric-value arg) 0)) (start (if (and mark-active transient-mark-mode) (region-beginning))) (startline (count-lines 1 (point))) (end (if (and mark-active transient-mark-mode) (region-end))) (endline (if (and mark-active transient-mark-mode) (count-lines 1 (region-end)) (count-lines 1 (save-excursion (forward-line arg) (line-end-position) (line-to-comment-or-uncomment (buffer-substring-no-properties (line-beginning-position) (line-end-position (cond ((eq 1 arg) ;; comment and reinsert (progn (comment-or-uncomment-region (line-beginning-position) (line-end-position)) (indent-according-to-mode) (end-of-line) (newline) (insert line-to-comment-or-uncomment) (indent-according-to-mode))) (( 1 arg) ;; comment/uncomment as lines are given (while (= 1 (prefix-numeric-value arg)) (comment-or-uncomment-region (line-beginning-position) (line-end-position)) (indent-according-to-mode) (end-of-line) (forward-line 1) (indent-according-to-mode) (setq arg (1- arg ((and start end) ;; region is active (comment-or-uncomment-region start end) (indent-according-to-mode) (if (eobp) (progn (newline) (indent-according-to-mode)) (progn (forward-line 1) (indent-according-to-mode (t ;; just one line (progn (comment-or-uncomment-region (line-beginning-position) (line-end-position)) (indent-according-to-mode) (if (eobp) (progn (newline) (indent-according-to-mode)) (progn (forward-line 1) (indent-according-to-mode ;; ar-comment-uncomment.el ends here ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
fill-region eats whitespace
fill-region eats whitespace after sentence-end-dot. Bug in fill.el, GNU Emacs 22.0.50.1 - CVS, Example: Filling the infotext-Node Checklist produces: - release.(If - Looks afterwards like this: The best way to send a bug report is to mail it electronically to the Emacs maintainers at bug-gnu-emacs@gnu.org, or to emacs-pretest-bug@gnu.org if you are pretesting an Emacs beta release.(If you want to suggest a change as an improvement, use the same address.) My bugfix suggestions (tested in text-mode): Just replace all the delete-region stuff with a simple `fixup-whitespace': 169,197c169,202 (delete-region (cond ;; `sentence-end' matched and did not match all spaces. ;; I.e. it only matched the number of spaces it needs: drop the rest. ((and (match-end 1) ( (match-end 0) (match-end 1))) (match-end 1)) ;; `sentence-end' matched but with nothing left. Either that means ;; nothing should be removed, or it means it's the old-style ;; sentence-end which matches all it can. Keep only 2 spaces. ;; We probably don't even need to check `sentence-end-double-space'. ((match-end 1) (min (match-end 0) (+ (if sentence-end-double-space 2 1) (save-excursion (goto-char (match-end 0)) (skip-chars-backward ) (point) (t ;; It's not an end of sentence. (+ (match-beginning 0) ;; Determine number of spaces to leave: (save-excursion (skip-chars-backward ]})\') (cond ((and sentence-end-double-space (or (memq (preceding-char) '(?. ?? ?!)) (and sentence-end-without-period (= (char-syntax (preceding-char)) ?w 2) ((and colon-double-space (= (preceding-char) ?:)) 2) ((char-equal (preceding-char) ?\n) 0) (t 1)) (match-end 0)) --- (fixup-whitespace) ;; (delete-region ;; (cond ;; ;; `sentence-end' matched and did not match all spaces. ;; ;; I.e. it only matched the number of spaces it needs: drop the rest. ;; ((and (match-end 1) ( (match-end 0) (match-end 1))) (match-end 1)) ;; ;; `sentence-end' matched but with nothing left. Either that means ;; ;; nothing should be removed, or it means it's the old-style ;; ;; sentence-end which matches all it can. Keep only 2 spaces. ;; ;; We probably don't even need to check `sentence-end-double-space'. ;; ((match-end 1) ;;(min (match-end 0) ;; (+ (if sentence-end-double-space 2 1) ;; (save-excursion (goto-char (match-end 0)) ;; (skip-chars-backward ) ;; (point) ;; (t ;; It's not an end of sentence. ;;(+ (match-beginning 0) ;; ;; Determine number of spaces to leave: ;; (save-excursion ;; (skip-chars-backward ]})\') ;; (cond ((and sentence-end-double-space ;; (or (memq (preceding-char) '(?. ?? ?!)) ;; (and sentence-end-without-period ;; (= (char-syntax (preceding-char)) ?w 2) ;;((and colon-double-space ;; (= (preceding-char) ?:)) 2) ;;((char-equal (preceding-char) ?\n) 0) ;;(t 1)) ;; (match-end 0)) Thanks for developing Emacs! Andreas Röhler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
documentation in outline.el
Seems to be a documentation flaw in outline.el: missing command names. Calling `describe-function' on `outline-mode' gives the following description: ... C-c C-t make all text invisible (not headings). C-c C-a make everything in buffer visible. C-c C-q make only the first N levels of headers visible. ... As the missing command names don't start with `outline-', it will be difficult to get them via expand. The following diff should fix the problem. outline.el 274,276c274,276 \\[hide-body] make all text invisible (not headings). \\[show-all] make everything in buffer visible. \\[hide-sublevels] make only the first N levels of headers visible. --- \\[hide-body] hide-body make all text invisible (not headings). \\[show-all] show-all make everything in buffer visible. \\[hide-sublevels] hide-sublevels make only the first N levels of headers visible. -- Andreas Roehler ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
