From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>,
emacs-devel@gnu.org
Subject: Re: occur-mode-hook run too early to be useful
Date: Wed, 28 Aug 2002 11:11:37 -0400 [thread overview]
Message-ID: <200208281511.g7SFBbQ04441@rum.cs.yale.edu> (raw)
In-Reply-To: 20020828164804.A71C.LEKTU@terra.es
> On Wed, 28 Aug 2002 10:30:05 -0400, "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> wrote:
>
> > That would be wrong. The hook should be run at the end of the major mode's
> > function.
>
> Yes, sure. That's the normal way and that's why I asked.
>
> But in this case things aren't that clear, as the distinction between
> code in occur-mode and code in occur-1 seems rather arbitrary:
>
> 1. occur-mode is only called from occur-1
No. `occur-mode' in an interactive function.
Oops, scratch that:
Yes, except that `occur-mode' should be an interactive function.
> 4. M-x occur-mode in a non-occur buffer is meaningless
Maybe you're right. But how about
M-x occur RET foo RET
...
M-x some-other-mode RET
...
M-x occur-mode RET
I switch major modes like that sometimes in order to get a particular
kind of font-lock highlighting, or some particular set of key-bindings.
I must admit that I'm not convinced it's very compelling in the case of
an occur buffer.
> So I think that's what I'm going to do: changing occur-mode-hook to just
> occur-hook and executing it at the end of occur-1.
That sounds good to me.
Stefan
next prev parent reply other threads:[~2002-08-28 15:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 9:16 occur-mode-hook run too early to be useful Juanma Barranquero
2002-08-28 14:30 ` Stefan Monnier
2002-08-28 15:06 ` Juanma Barranquero
2002-08-28 15:11 ` Stefan Monnier [this message]
2002-08-28 15:25 ` Juanma Barranquero
2002-08-28 15:30 ` Juanma Barranquero
2002-08-29 17:50 ` Richard Stallman
2002-08-30 2:14 ` Juanma Barranquero
2002-08-28 15:29 ` Kai Großjohann
2002-08-28 15:32 ` Stefan Monnier
2002-08-28 15:39 ` Kai Großjohann
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=200208281511.g7SFBbQ04441@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--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).