unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Hansen <david.hansen@gmx.net>
To: emacs-devel@gnu.org
Subject: occur and a "Special" *Occur* Buffer.
Date: Fri, 09 Mar 2007 08:12:08 +0100	[thread overview]
Message-ID: <87hcsuao1j.fsf@localhorst.mine.nu> (raw)

[-- Attachment #1: Type: text/plain, Size: 230 bytes --]

Hello,

another one.  Is no one else using special display buffers?  BTW in
this case `t' seems to be the right choice for the optional
`get-buffer-window' argument, but i have to admit that i don't
really understand it ;)

David

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 675 bytes --]

*** replace.el	09 Mar 2007 06:07:54 +0100	1.253
--- replace.el	09 Mar 2007 08:09:07 +0100	
***************
*** 844,850 ****
         #'next-single-property-change)
       "No more matches")
      ;; In case the *Occur* buffer is visible in a nonselected window.
!     (set-window-point (get-buffer-window (current-buffer)) (point))
      (occur-mode-goto-occurrence)))
  \f
  (defface match
--- 844,850 ----
         #'next-single-property-change)
       "No more matches")
      ;; In case the *Occur* buffer is visible in a nonselected window.
!     (set-window-point (get-buffer-window (current-buffer) t) (point))
      (occur-mode-goto-occurrence)))
  \f
  (defface match

[-- Attachment #3: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

             reply	other threads:[~2007-03-09  7:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-09  7:12 David Hansen [this message]
2007-03-09 15:32 ` occur and a "Special" *Occur* Buffer Stefan Monnier
2007-03-26  2:32   ` David Hansen
2007-03-26 15:10     ` Stefan Monnier
2007-03-27  4:17       ` David Hansen
2007-03-28  0:54         ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87hcsuao1j.fsf@localhorst.mine.nu \
    --to=david.hansen@gmx.net \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).