From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: autorevert and vc
Date: Thu, 1 Apr 2004 10:46:36 -0600 (CST) [thread overview]
Message-ID: <200404011646.i31Gkaj22768@raven.dms.auburn.edu> (raw)
In-Reply-To: <hdw4gfhb.fsf@blue.sea.net> (message from Jari Aalto on Thu, 01 Apr 2004 12:27:44 +0200)
Jari Aalto wrote:
| On the other hand, the problem only occurs while editing the same
| version controlled buffer from two distinct Emacs buffers. Why waste
| _any_ CPU if one knows that that situation is not going to occur?
I give an example where occurs.
I was not contesting that the situation _can_ occur. To state more
precisely what I meant:
Why should a particular user waste any CPU if that user knows that the
situation is not going to occur for him?
Since yesterday evening, there is a customizable variable
auto-revert-check-vc-info that works for all supported VC systems.
Setting it to t will update all VC info every auto-revert-interval
seconds. The default is nil. In personal rudimentary testing, it did
not seem to consume terribly much CPU for RCS and CVS. I tested on a
1.7 GHZ dual Xeon. I did not test the four other supported systems.
I do not know anything about them. I did not yet write a NEWS entry,
but I will.
If there would be performance problems for certain VC systems, one
could try to take care of them, for instance using Stefan's idea of a
`vc-stale-state-p' function.
Sincerely,
Luc.
next prev parent reply other threads:[~2004-04-01 16:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 3:52 autorevert and vc Luc Teirlinck
2004-03-29 4:24 ` Stefan Monnier
2004-03-29 4:43 ` Luc Teirlinck
2004-03-30 2:27 ` Luc Teirlinck
2004-03-30 19:56 ` Stefan Monnier
2004-04-01 10:27 ` Jari Aalto
2004-04-01 16:46 ` Luc Teirlinck [this message]
2004-03-30 15:17 ` Luc Teirlinck
2004-03-30 20:51 ` Andre Spiegel
2004-03-31 0:24 ` Stefan Monnier
2004-03-31 2:02 ` Luc Teirlinck
2004-03-31 2:15 ` Luc Teirlinck
2004-03-31 7:19 ` 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
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=200404011646.i31Gkaj22768@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.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).