From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: refreshing all frames from files
Date: Thu, 01 Mar 2007 20:50:56 -0700 [thread overview]
Message-ID: <es86ul$utq$1@sea.gmane.org> (raw)
In-Reply-To: <m33b4ocu45.fsf@localhost.localdomain>
Gary Wessle wrote:
> Xavier Maillard <zedek@gnu.org> writes:
>
>> Gary Wessle <phddas@yahoo.com> wrote:
>>
>>>>> the files get changed by another process and I want to view the
>>>>> changes with out having to do C-x C-v for each and every one.
>>>> `M-x global-auto-revert-mode' avoids the need to do anything explicitly.
>>> the mode is ON.
>>> how do you fire it?
>> It is *automatic* when ON. That is, just activate this minor-mode
>> globally and all will be okay.
>>
>> Xavier
>
> any way to make the buffer "once it gets updated" to show the last
> line and not the beginning as it does now, i.e, move the pointer down
> to the end so that I can see whats just been inserted?
From `M-x finder-commentary RET autorevert':
,----
| After reverting a file buffer, Auto Revert Mode normally puts point
| at the same position that a regular manual revert would. However,
| there is one exception to this rule. If point is at the end of the
| buffer before reverting, it stays at the end. Similarly if point
| is displayed at the end of a file buffer in any window, it will stay
| at the end of the buffer in that window, even if the window is not
| selected. This way, you can use Auto Revert Mode to `tail' a file.
| Just put point at the end of the buffer and it will stay there.
| These rules apply to file buffers. For non-file buffers, the
| behavior may be mode dependent.
|
| While you can use Auto Revert Mode to tail a file, this package
| contains a third minor mode, Auto Revert Tail Mode, which does so
| more efficiently, as long as you are sure that the file will only
| change by growing at the end. It only appends the new output,
| instead of reverting the entire buffer. It does so even if the
| buffer contains unsaved changes. (Because they will not be lost.)
`----
--
Kevin Rodgers
Denver, Colorado, USA
next prev parent reply other threads:[~2007-03-02 3:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 1:44 refreshing all frames from files Gary Wessle
2007-03-01 2:16 ` weber
2007-03-01 3:00 ` Gary Wessle
2007-03-01 4:28 ` Matthew Flaschen
2007-03-01 5:25 ` Kevin Rodgers
[not found] ` <mailman.241.1172726970.7795.help-gnu-emacs@gnu.org>
2007-03-01 6:11 ` Gary Wessle
2007-03-01 11:57 ` Xavier Maillard
2007-03-01 12:07 ` weber
[not found] ` <mailman.244.1172750433.7795.help-gnu-emacs@gnu.org>
2007-03-02 1:27 ` Gary Wessle
2007-03-02 3:50 ` Kevin Rodgers [this message]
[not found] ` <mailman.296.1172813363.7795.help-gnu-emacs@gnu.org>
2007-03-02 17:21 ` Gary Wessle
2007-03-03 5:20 ` Stefan Monnier
2007-03-03 17:01 ` Gary Wessle
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='es86ul$utq$1@sea.gmane.org' \
--to=kevin.d.rodgers@gmail.com \
--cc=help-gnu-emacs@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.