Mercurial > emacs

view BUGS @ 95137:06ea1d241e00

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
* proced.el (proced-goal-header-re): Renamed from proced-procname-column-regexp. (proced-goal-column): Renamed from proced-procname-column. (proced-move-to-goal-column): Renamed from proced-move-to-procname. (proced-header-face, proced-header-regexp): Removed. (proced-font-lock-keywords): Remove proced-header-face. (proced-header-alist, proced-sorting-schemes-re): New variables. (proced): Rename Proced buffer to *Proced*. (proced-next-line, proced-previous-line): New commands. (proced-do-mark, proced-do-mark-all, proced-toggle-marks) (proced-hide-processes): Do not treat first line as special. (proced-header-space): New function. (proced-update): Use header-line-format. Initialize proced-header-alist and proced-sorting-schemes-re. Set proced-goal-column. Include proced-command in mode-name. (proced-send-signal): Use header-line-format for *Marked Processes* buffer. (proced-sort): Restrict minibuffer completion to applicable sorting schemes. (proced-sorting-scheme-p): Use proced-sorting-schemes-re.
author Roland Winkler <Roland.Winkler@physik.uni-erlangen.de>
date Tue, 20 May 2008 10:19:06 +0000
parents 8ce686bd7f4f
children fb8bf24d2eb9
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 C-e in Emacs) to
make sure it isn't a known issue.