several improvements in occur and *Occur* buffer functionality

[Daniel Ortmann]

This bug report will be sent to the Free Software Foundation,
not to your local site managers!
Please write in English, because the Emacs maintainers do not have
translators to read other languages for them.

Your bug report will be posted to the bug-gnu-emacs@gnu.org mailing list,
and to the gnu.emacs.bug news group.

In GNU Emacs 21.1.2 (i386--freebsd, X toolkit, Xaw3d scroll bars)
 of 2001-12-09 on pyrl.eye
configured using `configure  --prefix=/usr/local i386--freebsd'
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: nil
  locale-coding-system: nil
  default-enable-multibyte-characters: t

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

Actions:

- open a buffer on a file (such as /usr/share/dict/words)
- M-x occur <enter> ^ab <enter>
- you should see some words such as Ab, aba, Ababdeh, etc.
- click mouse2 on one of the matching lines in the *Occur* buffer
- the result is that the *Occur* buffer remains unchanged

(The following suggestions to "occur" are basically taken from grep.)

Improvement 1:

Occur functionality would be highly improved if mouse2 caused the
selected *Occur* line to be moved to the top of the buffer.

Improvement 2:

Point should also be moved to the line mentioned above, i.e. the
selected line.  If this was done then I could leave my mouse over that
one line and continue to click the selection button without having to
move around to other lines.  It would greatly speed up the use of occur
functionality.

Improvement 3:

A local-set-key binding be made to made in the buffer from where occur
is run to enable quick selection of occur-next lines from the *Occur*
buffer (similar to the M-` binding to next-error in grep).

Improvement 4:

It would be *WONDERFUL* if a custom occur variable could be set to
enable grep-like behavior in occur mode.  For example, I have M-` set to
run "next-error".  If the custom setting is active then M-` might run
occur-next ... or perhaps next-error could process the *Occur* buffer
too?

You see at what I am getting ... The custom setting would increase
grep-like behavior.

Improvement 5:

A custom occur variable setting should enable multiple *Occur* buffers,
where new *Occur* buffers have unique names and are associated with only
the buffer from which the occur command was run.

The local-set-key binding mentioned above should enable this.

Recent input:
C-k C-k M-< C-n C-n C-n C-y <help-echo> <down-mouse-2> 
<mouse-2> C-a C-k C-k M-< M-} C-y C-x C-s M-> C-x n 
n M-< M-x o c c u r <return> w o n d e r . * c r e 
a t i o n <return> <help-echo> <down-mouse-2> <mouse-2> 
C-a C-k C-k M-< C-n C-n C-y <help-echo> <down-mouse-2> 
<mouse-2> C-a C-k C-k M-< C-n C-n C-n C-y C-x C-s <help-echo> 
<down-mouse-2> <mouse-2> C-a C-k C-k M-< M-} C-y C-x 
C-s M-> C-x n n M-< C-x 1 M-x r e p o r t - e m <tab> 
<return>

Recent messages:
4 lines matched
Mark set [6 times]
Wrote /usr/home/ortmann/ICR_comprehensive_listing
Mark set [2 times]
4 lines matched
Mark set [4 times]
Wrote /usr/home/ortmann/ICR_comprehensive_listing
Mark set [2 times]
Wrote /usr/home/ortmann/ICR_comprehensive_listing
Mark set [2 times]

-- 
Daniel Ortmann, 2414 30 Av NW, #D, Rochester, MN 55901
ortmann@isl.net (h)   / 507.288.7732 (h)
dortmann@lsil.com (w) / 507.529.3887 (w)