Re: cannot activate font-lock-mode
Sorry for not answering earlier but I just retrieved your response from gmx's spam folder. So, what is now the recommended way to set file-specific font-lock keywords using file-local variables? If this has changed, it should be specified in the NEWS. I can write an entry once I understand the answer to my questions above. You could add to your .emacs something like (setq safe-local-eval-forms '((my-very-private-foobar))) ; customizable! (defun my-very-private-foobar () (setq font-lock-defaults '((^\\s-*:0 ##+))) (font-lock-mode 1)) and in the local variables section use # Local Variables: # eval: (my-very-private-foobar) # End: ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: visiting certain .c file adds to kill ring
With my recent cvs build or the debian snapshot, and starting from emacs -Q, visiting the file foo.c below with C-x C-f foo.c leaves the first line in the kill ring, C-y = inserts /* hello */ where I hoped it would leave the kill ring alone. (In particular it's not good to have the kill changed when you're doing a cut and paste from another file into that one.) I suspect c-remove-any-local-eval-or-mode-variables in cc-mode.el shouldn't be using kill-line, but cc-mode is hellishly complicated ... Would the attached patch do the right thing for you? cc-mode doesn't like `line-beginning-position' and `line-end-position'. *** progmodes/cc-mode.elMon Apr 2 07:45:14 2007 --- progmodes/cc-mode.elSat Apr 21 12:03:10 2007 *** *** 820,826 $) nil t) (beginning-of-line) ! (kill-line 1))) ;; Delete the first line, if we've got one, in case it contains a mode spec. (unless (and lv-point --- 820,826 $) nil t) (beginning-of-line) ! (delete-region (point) (progn (end-of-line) (point) ;; Delete the first line, if we've got one, in case it contains a mode spec. (unless (and lv-point *** *** 828,835 (forward-line 0) (bobp))) (goto-char (point-min)) ! (unless (eobp) ! (kill-line 1) (defun c-postprocess-file-styles () Function that post processes relevant file local variables in CC Mode. --- 828,834 (forward-line 0) (bobp))) (goto-char (point-min)) ! (delete-region (point) (progn (end-of-line) (point)) (defun c-postprocess-file-styles () Function that post processes relevant file local variables in CC Mode. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: patch for locate.el when called with prefix arg
Chong Yidong writes: Thanks. I've checked the patch in. (I see Luc made further changes.) There are still a few problems: (1) revert-buffer does not work in *Locate* buffers that result from C-u locate RET or C-u locate-with-filter RET. (2) While C-u locate RET gives the prompt Run locate (like this): , locate-with-filter gives the same prompt, Locate: , regardless of whether or not a prefix arg is used. The behaviour of C-u locate-with-filter is analogous to C-u locate (due to the value current-prefix-arg), but the use of a prefix arg is not documented for locate-with-filter. (All of this is also true for Emacs 21.) (FYI; not necessarily suggesting this is addressed before the release.) Thanks, Matt ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: visiting certain .c file adds to kill ring
martin rudalics [EMAIL PROTECTED] writes: cc-mode doesn't like `line-beginning-position' and `line-end-position'. [subr.el] ;; These are the XEmacs names: (defalias 'point-at-eol 'line-end-position) (defalias 'point-at-bol 'line-beginning-position) Here are other incorrect uses of kill-* functions in lisp/progmodes: cc-cmds.el:859: (kill-region (progn (forward-line 0) (point)) perl-mode.el:653: (kill-region (point) eol)) And there's a bunch of suspicious kill-line/kill-word/kill-region in mantemp.el and vhdl-mode.el. -- Johan Bockgård ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Link in define-key doc broken
The link to Extended Menu Items in the doc string for define-key is broken. In GNU Emacs 22.0.98.1 (i386-mingw-nt5.1.2600) of 2007-04-17 ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: visiting certain .c file adds to kill ring
cc-mode doesn't like `line-beginning-position' and `line-end-position'. [subr.el] ;; These are the XEmacs names: (defalias 'point-at-eol 'line-end-position) (defalias 'point-at-bol 'line-beginning-position) I think it's for Emacs 20 compatibility. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Bottom part of Extended Menu Items badly formatted
The bottom part of (info (elisp) Extended Menu Items) is badly formatted which makes it quite hard to understand. The very last paragraph should belong to :filter. In GNU Emacs 22.0.98.1 (i386-mingw-nt5.1.2600) of 2007-04-19 ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
flyspell and abbrev
hello, I don't know if this is a bug or some option that I need to set, but it's been there for a while: emacs-22.0.98 on gnu-linux redhat emacs -Q open a new file t.txt turn flyspell on set flyspell-abbrev-p to t type Cho the word is highlighted as a spelling mistake. use middle mouse to save it as a correct word. type CHo highlighted as a spelling mistake again, use middle mouse to correct to Cho. type CHospace the word is not automatically corrected to Cho even though it is now in the abbrev table. thanks... _ Mortgage rates near historic lows. Refinance $200,000 loan for as low as $771/month* https://www2.nextag.com/goto.jsp?product=10035url=%2fst.jsptm=ysearch=mortgage_text_links_88_h27f8disc=yvers=689s=4056p=5117 ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: visiting certain .c file adds to kill ring
Here are other incorrect uses of kill-* functions in lisp/progmodes: cc-cmds.el:859: (kill-region (progn (forward-line 0) (point)) perl-mode.el:653: (kill-region (point) eol)) And there's a bunch of suspicious kill-line/kill-word/kill-region in mantemp.el and vhdl-mode.el. In lisp/ array.el:688: (kill-line 1)) array.el:708: (kill-line 1) strokes.el:1361: (kill-region (1+ (point)) (point-max tumme.el:918: (kill-line 1) vc.el:2279: (or (eobp) (kill-line)) FWIW there are more in rnews.el, tramp.el, bib-mode.el, calc-... The two uses in ido.el don't appear very clean either. We should fix them up after the release (maybe using something like a generalized `woman-delete-line' for the `kill-line' case to be on the safe side). ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: No doc string for `read-number'
`read-number' should have a doc string. Ok, thanks. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
dired-virtual-mode doc
The doc string for dired-virtual-mode speaks about the nonexistent variable `buffer-contents-mode-alist'. Also, the regexp is wrong (the /?+ part) and a bunch of backslashes are missing. 2007-04-21 Johan Bockgård [EMAIL PROTECTED] * dired-x.el (dired-virtual-mode): Doc fix. *** dired-x.el 07 Apr 2007 00:27:05 +0200 1.78 --- dired-x.el 21 Apr 2007 11:39:53 +0200 *** *** 790,810 (revert-buffer))) ;; A zero-arg version of dired-virtual. - ;; You need my modified version of set-auto-mode for the - ;; `buffer-contents-mode-alist'. - ;; Or you use infer-mode.el and infer-mode-alist, same syntax. (defun dired-virtual-mode () Put current buffer into Virtual Dired mode (see `dired-virtual'). ! Useful on `buffer-contents-mode-alist' (which see) with the regexp ! \^ \\(/[^ /]+\\)/?+:$\ to put saved dired buffers automatically into Virtual Dired mode. ! Also useful for `auto-mode-alist' (which see) like this: ! \(setq auto-mode-alist (cons '(\[^/]\\.dired\\'\ . dired-virtual-mode) ! auto-mode-alist)\) (interactive) (dired-virtual (dired-virtual-guess-dir))) --- 790,807 (revert-buffer))) ;; A zero-arg version of dired-virtual. (defun dired-virtual-mode () Put current buffer into Virtual Dired mode (see `dired-virtual'). ! Useful on `magic-mode-alist' with the regexp ! \^ (/[^ /]+)+/?:$\ to put saved dired buffers automatically into Virtual Dired mode. ! Also useful for `auto-mode-alist' like this: ! (add-to-list 'auto-mode-alist !'(\[^/].dired'\ . dired-virtual-mode)) (interactive) (dired-virtual (dired-virtual-guess-dir))) -- Johan Bockgård ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: visiting certain .c file adds to kill ring
On Sat, Apr 21 2007, martin rudalics wrote: [subr.el] ;; These are the XEmacs names: (defalias 'point-at-eol 'line-end-position) (defalias 'point-at-bol 'line-beginning-position) I think it's for Emacs 20 compatibility. I think the comment is correct. XEmacs prefers point-at-[be]ol (which are defined src/cmds.c in whereas line-*-position are defined in lisp/obsolete.el) whereas Emacs prefers line-*-position (builtin; point-at-[be]ol are aliases since Emacs 21 [1]). Bye, Reiner. [1] , | revision 1.209 | date: 1999-08-16 22:57:24 +0200; author: kwzh; state: Exp; lines: +2 -0 | (point-at-eol, point-at-bol): New aliases. ` -- ,,, (o o) ---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/ ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: flyspell and abbrev
I think this is an issue for aspell or ispell (whichever one you are using). Not for Emacs. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Bottom part of Extended Menu Items badly formatted
I will try to improve this. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: visiting certain .c file adds to kill ring
You have found a real bug. Please install your patch. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: python.el
What's the reason for disregarding my legal concerns about that work? Maybe this message is meant for some specific recipients who will already know what this is about. If not, please could you explain in more detail what you mean? Precisely which work has potential legal concerns? I would also like to know the answer. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Link in define-key doc broken
Lennart Borgman (gmail) wrote: The link to Extended Menu Items in the doc string for define-key is broken. Thanks; fixed. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: patch for locate.el when called with prefix arg
(1) revert-buffer does not work in *Locate* buffers that result from C-u locate RET or C-u locate-with-filter RET. We have not generally implemented reverting for search command output. Locate implements a revert-buffer-function, locate-update. The reported bug can be annoying and confusing to the user. The following patch fixes the reported bug, as well as a related bug when locate-prompt-for-command is t, as well as a related bug with `C-u g' in locate buffers, and provides a doc fix for locate-prompt-for-command: ===File ~/locate-diff-4= *** locate.el 21 Apr 2007 00:00:52 -0500 1.42 --- locate.el 21 Apr 2007 14:27:15 -0500 *** *** 117,122 --- 117,123 (defvar locate-current-filter nil) (defvar locate-local-filter nil) (defvar locate-local-search nil) + (defvar locate-local-prompt nil) (defgroup locate nil Interface to the locate command. *** *** 221,227 (defcustom locate-prompt-for-command nil If non-nil, the `locate' command prompts for a command to run. ! Otherwise, that behavior is invoked via a prefix argument. :group 'locate :type 'boolean) --- 222,231 (defcustom locate-prompt-for-command nil If non-nil, the `locate' command prompts for a command to run. ! Otherwise, that behavior is invoked via a prefix argument. ! ! Setting this option non-nil actually inverts the meaning of a prefix arg; ! that is, with a prefix arg, you get the default behavior. :group 'locate :type 'boolean) *** *** 304,309 --- 308,314 (setq locate-current-filter filter) (set (make-local-variable 'locate-local-search) search-string) (set (make-local-variable 'locate-local-filter) filter) + (set (make-local-variable 'locate-local-prompt) run-locate-command) (if run-locate-command (shell-command search-string locate-buffer-name) *** *** 584,590 Revert the *Locate* buffer. If `locate-update-when-revert' is non-nil, offer to update the locate database using the shell command in `locate-update-command'. ! (let ((locate-buffer-name (buffer-name))) (and locate-update-when-revert (yes-or-no-p Update locate database (may take a few seconds)? ) ;; `expand-file-name' is used in order to autoload Tramp if --- 589,597 Revert the *Locate* buffer. If `locate-update-when-revert' is non-nil, offer to update the locate database using the shell command in `locate-update-command'. ! (let ((locate-buffer-name (buffer-name)) ! (locate-prompt-for-command locate-local-prompt) ! (current-prefix-arg nil)) (and locate-update-when-revert (yes-or-no-p Update locate database (may take a few seconds)? ) ;; `expand-file-name' is used in order to autoload Tramp if ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: dired-virtual-mode doc
Johan Bockgård wrote: The doc string for dired-virtual-mode speaks about the nonexistent variable `buffer-contents-mode-alist'. Also, the regexp is wrong (the /?+ part) and a bunch of backslashes are missing. Thank you; installed. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: patch for locate.el when called with prefix arg
Richard Stallman wrote: (2) While C-u locate RET gives the prompt Run locate (like this): , locate-with-filter gives the same prompt, Locate: , regardless of whether or not a prefix arg is used. The behaviour of C-u locate-with-filter is analogous to C-u locate (due to the value current-prefix-arg), but the use of a prefix arg is not documented for locate-with-filter. (All of this is also true for Emacs 21.) That's not serious. And apparently the feature is non-intentional. `locate-in-alternate-database' has a similar undocumented (and probably non-intentional) feature. Is the way the `locate' command uses `current-prefix-arg', outside an interactive declaration and without checking that `locate' itself was called interactively, actually legitimate? It means that any function that calls locate, and uses itself the prefix arg with unrelated meaning, has to bind `current-prefix-arg' to nil around the call to `locate', otherwise a bug results. (This is actually part of what my previous patch does for `locate-update', which was necessary, because otherwise `C-u g' produces a bug.) This does not seem very clean to me. In the case of `locate-with-filter' and `locate-in-alternate-database' the result could actually be considered a feature rather than a bug. Sincerely, Luc Teirlinck. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: patch for locate.el when called with prefix arg
(1) revert-buffer does not work in *Locate* buffers that result from C-u locate RET or C-u locate-with-filter RET. Note that, without my very latest suggested patch, you _can_ actually correctly revert such buffers using `C-u g'. Obviously, this is not a very clean feature. (But it is fun.) Sincerely, Luc Teirlinck. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: visiting certain .c file adds to kill ring
Please install your patch. Done. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
pending-undo-list is not buffer local
The variable pending-undo-list is used by for example undo-start and undo-more. The doc strings says that you should first call undo-start and then you can call one or several times undo-more later. If those calls are done in different buffers it looks like trouble to me. Should not pending-undo-list be buffer local? I think for the reason above that it should be buffer local and I also think that it should be permanent buffer local then. I asked before if it should not be permanent buffer local. That was said not to be necessary since it is not buffer local. I think that is wrong, but please see the thread here: http://lists.gnu.org/archive/html/emacs-devel/2007-03/msg01712.html In GNU Emacs 22.0.98.1 (i386-mingw-nt5.1.2600) of 2007-04-17 ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: flyspell and abbrev
I think this is an issue for aspell or ispell (whichever one you are using). Not for Emacs. thanks for the prompt response. actually I thought this might be an issue of dabbrev and emacs. flyspell is only the way in which the abbrev is defined in my bug report. So if I create an abbrev such that CHospace should be replaced by Cho, it wouldn't work right now (for me). again, the documentation regarding the treatment of case with abbrevs is not simple, and I may have not understood it. _ Download Messenger. Join the im Initiative. Help make a difference today. http://im.live.com/messenger/im/home/?source=TAGHM_APR07 ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: flyspell and abbrev
Richard Stallman wrote: I think this is an issue for aspell or ispell (whichever one you are using). Not for Emacs. No, I think rather that flyspell should downcase abbrevs before defining them, like define-mode-abbrev does. Beyond that, given the way expand-abbrev treats case, does it make any sense for define-abbrev to allow you to define an abbrev without downcasing it? They don't seem to work at all, eg: emacs -Q -f abbrev-mode (define-abbrev lisp-mode-abbrev-table FOO foobar) FOO - not expanded foo - not expanded (define-abbrev lisp-mode-abbrev-table bar foobar) bar - foobar Bar - Foobar BAr - Foobar BAR - FOOBAR *** flyspell.el 06 Apr 2007 19:55:53 -0700 1.117 --- flyspell.el 21 Apr 2007 16:30:23 -0700 *** *** 1827,1833 (defun flyspell-define-abbrev (name expansion) (let ((table (flyspell-abbrev-table))) (when table ! (define-abbrev table name expansion ;;*-*/ ;;*flyspell-auto-correct-word ... */ --- 1827,1833 (defun flyspell-define-abbrev (name expansion) (let ((table (flyspell-abbrev-table))) (when table ! (define-abbrev table (downcase name) expansion ;;*-*/ ;;*flyspell-auto-correct-word ... */ ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: [unicode-2] whitespace-auto-cleanup always replaces leading spaces with tabs
On Wed, 2007-04-11 at 23:23 +0200, martin rudalics wrote: I set it in custom-set-variables; another likely scenario, I would think. whitespace.el has this form (defcustom whitespace-check-indent-whitespace indent-tabs-mode which, as Miles explained, gets evaluated when whitespace is loaded with the value `indent-tabs-mode' has at that time. Apparently you set `indent-tabs-mode' to a different value afterwards. Hence, the values of `indent-tabs-mode' and `whitespace-check-indent-whitespace' eventually conflict in one of your buffers. I just wanted to know your particular usage pattern in order to propose a solution. As I said, I normally set these variables in custom-set-variables (in .emacs). With regard to your request, I'm unfamiliar with -Q and so far I haven't found documentation for it. So, more explicit instructions about what you'd like me to try would be appreciated. -Q is an initial option. From the Emacs manual: `-Q' `--quick' Start emacs with minimum customizations. This is like using `-q' and `--no-site-file', but also disables the startup screen. If I start with -Q and then set whitespace-global-mode to non-nil and set both whitespace-check-leading-whitespace and whitespace-check-indent-whitespace to nil, leading sequences of 8 spaces still get highlighted. IMHO there's no reasonable way to reconcile a user's settings of `indent-tabs-mode' with those of `whitespace-check-indent-whitespace'. I think `whitespace-indent-cleanup' should be executed iff `indent-tabs-mode' is non-nil in the current buffer. But I'm afraid that anything we change here will break existing customizations. Why isn't it reasonable for whitespace-indent-cleanup to change tabs in indentation to spaces when indent-tabs-mode is nil? It is reasonable. Unfortunately, the decisions of `whitespace-indent-cleanup' are based on the actual value of `whitespace-check-indent-whitespace' and not on that of `indent-tabs-mode'. I see. But I think this has gotten sidetracked from the real bug that was introduced here. Indeed, the fact that whitespace-check-indent-whitespace has never done what I want is exactly the reason I have it set to nil (along with whitespace-check-leading-whitespace; I'm not clear on how these two differ). So the bug that has been introduced recently is whatever causes whitesapce checking to flag indentation whitespace even though whitespace-check-indent-whitespace is nil. -- Braden McDaniel e-mail: [EMAIL PROTECTED] http://endoframe.comJabber: [EMAIL PROTECTED] ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: flyspell and abbrev
For now, I installed the flyspell change. I suggest we think about the wider issue after the release. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: read-number: Ask again if error reading input
Thanks. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: redisplay
(progn (new-frame) (redisplay t) (x-popup-dialog t '(Foo (Bar . 1 I tried this but it didn't fail -- the new frame was not empty. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Link in define-key doc broken
The link to Extended Menu Items in the doc string for define-key is broken. I think the reason is that it fails to specify which manual. Please try adding `(elisp)' to the node name. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
