Mercurial > emacs
view BUGS @ 53139:df3033332097
* progmodes/grep.el: New file with grep code from compile.el.
(grep): New defcustom group.
(grep-window-height): New defcustom, like compilation-window-height.
(grep-auto-highlight): New defcustom, like compile-auto-highlight.
(grep-scroll-output): New defcustom, like compilation-scroll-output.
(grep-command, grep-use-null-device, grep-find-command)
(grep-tree-files-aliases, grep-tree-ignore-case)
(grep-tree-ignore-CVS-directories): Move to grep custom group.
(grep-setup-hook): New hook variable.
(grep-mode-map): New keymap for grep commands. Add Grep menu.
(grep-use-compilation-buffer): New defcustom.
(grep-last-buffer): New defvar, override compilation-last-buffer.
(grep): Add optional arg HIGHLIGHT-REGEXP. Doc fix.
Call compile-internal with args highlight-regexp and grep-mode-map.
author | Kim F. Storm <storm@cua.dk> |
---|---|
date | Sun, 23 Nov 2003 20:56:10 +0000 |
parents | af68d12218d0 |
children | 8ce686bd7f4f |
line wrap: on
line source
If you think you may have found a bug in GNU Emacs, please read the Bugs section of the Emacs manual for advice on (1) how to tell when to report a bug, and (2) how to write a useful bug report and what information it needs to have. There are three ways to read the Bugs section. (1) In a printed copy of the Emacs manual. You can order one from the Free Software Foundation; see the file etc/ORDERS. But if you don't have a copy on hand and you think you have found a bug, you shouldn't wait to get a printed manual; you should read the section right away as described below. (2) With Info. Start Emacs, do C-h i to enter Info, then m Emacs RET to get to the Emacs manual, then m Bugs RET to get to the section on bugs. Or use standalone Info in a like manner. (Standalone Info is part of the Texinfo distribution, not part of the Emacs distribution.) (3) By hand. Do cat info/emacs* | more "+/^File: emacs, Node: Bugs," Please first check the file etc/PROBLEMS (e.g. with C-h P in Emacs) to make sure it isn't a known issue.