all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Torsten Bronger <bronger@physik.rwth-aachen.de>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: 768@debbugs.gnu.org
Subject: bug#768: 23.0.60; vc-bzr.el re-reads metadata files in an endless loop
Date: Sun, 11 Sep 2011 19:45:17 +0200	[thread overview]
Message-ID: <87pqj7otw2.fsf@physik.rwth-aachen.de> (raw)
In-Reply-To: <20080823150616.E3D2C32803D@wilson.homeunix.com>

Hallöchen!

Lars Magne Ingebrigtsen writes:

> Torsten Bronger <bronger@physik.rwth-aachen.de> writes:
>
>> I think I know what happens: I set (auto-revert-check-vc-info t)
>> which probably means that Emacs re-reads VC metadata every five
>> seconds.  However, it is questionable whether this makes sense
>> for remote files through Tramp.
>
> I think special-casing the action of that variable for tramp files
> sounds non-optimal.  If your files are too slow to be read in that
> way, then you shouldn't switch that on, but Emacs has no way of
> determining that.

But tramp files are special-cased also when it comes to restoring
the desktop after an Emacs start: They are not restored (at least
not by default).  I think it is fair to assume that probing a file
every five seconds through SSH is more critical than probing a local
file.

Moreover, I have dozens of local version-controlled files open but I
open a remote file only seldomly.  Without special-casing, the whole
workflow suffered due to a rare use case.

Tschö,
Torsten.

-- 
Torsten Bronger    Jabber ID: torsten.bronger@jabber.rwth-aachen.de
                                  or http://bronger-jmp.appspot.com





      reply	other threads:[~2011-09-11 17:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-23 15:06 bug#768: 23.0.60; vc-bzr.el re-reads metadata files in an endless loop Torsten Bronger
2008-08-28  6:05 ` Torsten Bronger
2011-09-11 17:24   ` Lars Magne Ingebrigtsen
2011-09-11 17:45     ` Torsten Bronger [this message]

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=87pqj7otw2.fsf@physik.rwth-aachen.de \
    --to=bronger@physik.rwth-aachen.de \
    --cc=768@debbugs.gnu.org \
    --cc=larsi@gnus.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.