unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: nickrob@snap.net.nz, storm@cua.dk, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Display feature request: gud-overlay-arrow
Date: Tue, 21 Mar 2006 17:01:03 -0500	[thread overview]
Message-ID: <87veu7cvnp.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20060322.044009.07761515.jet@gyve.org> (Masatake YAMATO's message of "Wed, 22 Mar 2006 04:40:09 +0900 (JST)")

>> I guess it would be easier to do if we had a "post-switch-buffer-hook" that
>> is called (after post-command-hook) whenever a new buffer is selected
>> in the command loop.
>> 
>> I really don't like the idea that Emacs could run hooks when switching
>> buffers.  It would make things rather uncontrollable.
> 
> Why it would do?
> I think `post-switch-buffer-hook' may be quite useful.
> e.g. we can give different colors for different buffers.

I don't understand how those three points of view relate to each other.
I strongly suspect that you all three talk about something very different.
Here is my guess at what's happening:

- Yamamoto wants a set-display-buffer-hook.
- Richard is afraid of the idea of set-buffer-hook.
- Kim suggested yet some other kind of hook.  I'm not sure what it's
  supposed to do and how/when/why someone would use it, based on
  his description.  All I understand is that it would be called at most
  once per command and only if "a new buffer is selected", tho it's no clear
  what might have caused this change (the command, presumably?) and whether
  he's talking about a change in (current-buffer) or in (window-buffer
  (selected-window)).


-- Stefan

  reply	other threads:[~2006-03-21 22:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-20 22:59 Display feature request: gud-overlay-arrow Nick Roberts
2006-03-20 23:42 ` Kim F. Storm
2006-03-21  3:55   ` Nick Roberts
2006-03-21  9:27     ` Kim F. Storm
2006-03-21 10:35       ` Nick Roberts
2006-03-21 13:43         ` Kim F. Storm
2006-03-22  3:20           ` Nick Roberts
2006-03-22 20:43             ` Kim F. Storm
2006-03-23  5:15               ` John S. Yates, Jr.
2006-03-23  5:04                 ` Miles Bader
2006-03-23  5:51                   ` Nick Roberts
2006-03-23  6:26                     ` Miles Bader
2006-03-23 21:28                 ` Nick Roberts
2006-03-23  8:59           ` Nick Roberts
2006-03-23 10:23             ` Kim F. Storm
2006-03-23 21:59               ` Nick Roberts
2006-03-21 19:26   ` Richard Stallman
2006-03-21 19:40     ` Masatake YAMATO
2006-03-21 22:01       ` Stefan Monnier [this message]
2006-03-21 21:58     ` Kim F. Storm
2006-03-22 13:44       ` Richard Stallman
2006-03-22 17:50         ` Kim F. Storm
2006-03-23 19:47           ` Richard Stallman

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=87veu7cvnp.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=nickrob@snap.net.nz \
    --cc=rms@gnu.org \
    --cc=storm@cua.dk \
    /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).