From: John J Foerch <jjfoerch@earthlink.net>
To: emacs-devel@gnu.org
Subject: Re: request: make-frame-visible hook
Date: Wed, 18 Feb 2009 20:27:15 -0500 [thread overview]
Message-ID: <87vdr7i5cc.fsf@earthlink.net> (raw)
In-Reply-To: E1LZvUG-0005w8-Cg@fencepost.gnu.org
Richard M Stallman <rms@gnu.org> writes:
> I have used the emacs irc clients Circe and Erc, which both provide
> modes to track activity in hidden irc buffers. "Hidden" may mean a
> buffer that is not visible in any frame, or a buffer shown in a
> non-visible frame. The irc channels with new activity are indicated in
> the mode-line. Switching to a tracked buffer removes that buffer's
> indicator from the mode-line.
>
> I don't think I would add an Emacs feature for the sake of this.
> However, you might be able to get more or less the same result
> by triggering off the arrival of output from a process or connection
> and seeing which IRC buffers are currently displayed.
What you describe is implemented in both of the irc clients I
mentioned. They update the mode-line tracking indicator when new data
arrives from the process, but this is not often enough, and it is the
situation I would like to improve upon. A typical case for the new
feature would be as follows:
I have an emacs frame open on workspace 1, and my mode-line indicates
that there is activity in an irc channel. I switch to workspace 2,
where I have a frame showing the active irc channel. Without the
ability to use the make-frame-visible event, the mode-line tracking
indicator will continue to show that buffer, possibly for minutes until
more data comes from the process. If I switch back to workspace 1, and
the tracking indicator still has not been updated, I cannot then know
when the next new data arrives from the process, because the indicator
is now falsely on, though I have already read the buffer.
I guess I am not sure what the point of having a make-frame-visible
event is, if there can only be one handler on it.
Thank you for your time. I hope you will reconsider.
--
John Foerch
next prev parent reply other threads:[~2009-02-19 1:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 20:14 request: make-frame-visible hook John J Foerch
2009-02-17 17:09 ` John J Foerch
2009-02-18 12:09 ` Richard M Stallman
2009-02-18 14:59 ` Lynbech Christian
2009-02-18 16:54 ` Stefan Monnier
2009-02-19 13:07 ` Lynbech Christian
2009-02-19 17:13 ` Stefan Monnier
2009-02-18 17:14 ` John J Foerch
2009-02-18 23:05 ` Richard M Stallman
2009-02-18 23:44 ` Stefan Monnier
2009-02-19 1:27 ` John J Foerch [this message]
2009-02-19 13:24 ` Lynbech Christian
2009-02-20 0:01 ` John J Foerch
2009-02-20 1:28 ` Miles Bader
2009-02-20 13:31 ` Richard M Stallman
2009-02-21 2:11 ` Kim F. Storm
2009-02-21 2:23 ` Stefan Monnier
2009-02-21 9:11 ` Eli Zaretskii
2009-02-21 14:10 ` martin rudalics
2009-02-21 17:41 ` Richard M Stallman
2009-02-21 20:59 ` Kim F. Storm
2009-02-22 3:31 ` Bo Lin
2009-02-22 14:35 ` Richard M Stallman
2009-02-21 20:43 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vdr7i5cc.fsf@earthlink.net \
--to=jjfoerch@earthlink.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.