From: martin rudalics <rudalics@gmx.at>
To: ybaumes@gmail.com
Cc: help-gnu-emacs@gnu.org
Subject: Re: How to follow the end of *Messages* buffer in Emacs?
Date: Sat, 10 Nov 2012 12:56:14 +0100 [thread overview]
Message-ID: <509E40DE.9040607@gmx.at> (raw)
> I am playing with Elisp, and I find convenient to have the *Messages*
> buffer always open in a window in my frame.
>
> I discovered recently that sometimes the buffer stops following the last
> lines. If I want to see the last appended lines in this buffer, I need
> to go in the buffer and jump to the end manually, with M->. Which is
> quite annoying and disruptive.
Can you please tell us when and how this happens. Here, when I display
*Messages* in a window, I always see the last line but maybe something
about my setup is peculiar.
> I am trying to reproduce the "tail -f" command line, in a buffer. Of
> course 'auto-revert-tail-mode complains that the *Messages* is not a
> visited file... As a consequence, this mode does not want to work. But
> it gave me the idea to add a function hook when the buffer is modified.
> That function would jump to (point-max) each time that buffer is
> modified.
>
> Here is my own attempt, invoked from *Messages* buffer, with M-:
> (add-hook
> 'after-change-functions
> (lambda (s e l) (goto-char (point-max)))
> nil t)
>
> But it does not work. The (point) remains in the same place while I see
> the buffer is growing... The lambda function does not produce any error,
> otherwise it would have been removed from the 'after-change-functions
> hook and C-h k 'after-change-functions shows it is present.
The (goto-char (point-max)) just sets `point' in that buffer. It does
not care whether the buffer is currently displayed in a window. You
have to use something like
(walk-windows
(lambda (w)
(when (eq (window-buffer w) (current-buffer))
(set-window-point w (point-max))))))
within that function.
martin
next reply other threads:[~2012-11-10 11:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 11:56 martin rudalics [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-12 9:57 How to follow the end of *Messages* buffer in Emacs? martin rudalics
[not found] <mailman.12681.1352548591.855.help-gnu-emacs@gnu.org>
2012-11-10 15:55 ` Yves Baumes
[not found] ` <m2bof5l4lx.fsf@gmail.com>
2012-11-10 18:51 ` martin rudalics
[not found] ` <mailman.12702.1352573476.855.help-gnu-emacs@gnu.org>
2012-11-10 19:56 ` Yves Baumes
2012-11-10 21:02 ` martin rudalics
[not found] ` <mailman.12713.1352581388.855.help-gnu-emacs@gnu.org>
2012-11-10 22:00 ` Yves Baumes
2012-11-12 9:56 ` martin rudalics
2012-11-10 22:24 ` Yves Baumes
2012-11-11 17:25 ` Stefan Monnier
2012-11-09 22:52 Yves Baumes
2012-11-10 6:39 ` B. T. Raven
2012-11-10 10:07 ` Peter Dyballa
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=509E40DE.9040607@gmx.at \
--to=rudalics@gmx.at \
--cc=help-gnu-emacs@gnu.org \
--cc=ybaumes@gmail.com \
/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.
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).