unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Thien-Thi Nguyen <ttn@gnuvola.org>
Cc: emacs-devel@gnu.org
Subject: Re: sh.exe needed to bootstrap on Windows?
Date: Tue, 17 Jul 2007 15:13:19 +0200	[thread overview]
Message-ID: <86bqebuqa8.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <87y7hfry4y.fsf@ambire.localdomain> (Thien-Thi Nguyen's message of "Tue\, 17 Jul 2007 14\:51\:57 +0200")

Thien-Thi Nguyen <ttn@gnuvola.org> writes:

> () Andreas Schwab <schwab@suse.de>
> () Tue, 17 Jul 2007 13:45:45 +0200
>
>    loaddefs.el is not registered with CVS.
>
> i see in the manual:
>    
>    The variable `vc-handled-backends' determines which version
>    control systems VC should handle.  The default value is `(RCS CVS
>    SVN SCCS Arch MCVS)', so it contains all six version systems that
>    are currently supported.  If you want VC to ignore one or more of
>    these systems, exclude its name from the list.  To disable VC
>    entirely, set this variable to `nil'.
>
> maybe autoload processing should let-bind vc-handled-backends to nil?

Pretty much everything that is not going to end with a user-visible
buffer.  For example, with-temp-file.

If this was done in general, I would be tempted to let AUCTeX register
a pseudo-version control system for its parsing stuff (which looks for
a bunch of other files) so that the parsing stuff necessary for the
user backend happens only when necessary.

But perhaps the latter is a bit too much trickery.

-- 
David Kastrup

  reply	other threads:[~2007-07-17 13:13 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-16  9:10 sh.exe needed to bootstrap on Windows? Juanma Barranquero
2007-07-16 19:15 ` Eli Zaretskii
2007-07-16 19:54   ` Juanma Barranquero
2007-07-16 20:19     ` Eli Zaretskii
2007-07-16 20:28       ` Juanma Barranquero
2007-07-16 20:46         ` Eli Zaretskii
2007-07-16 21:01           ` Dan Nicolaescu
2007-07-16 21:19             ` Eli Zaretskii
2007-07-16 21:30               ` Dan Nicolaescu
2007-07-16 22:01                 ` Eli Zaretskii
2007-07-16 22:40                   ` Dan Nicolaescu
2007-07-16 22:44                     ` Eli Zaretskii
2007-07-16 22:53                       ` Dan Nicolaescu
2007-07-17  3:15                         ` Eli Zaretskii
2007-07-16 20:34       ` Dan Nicolaescu
2007-07-17  7:56       ` Jason Rumney
2007-07-17  8:43         ` Dan Nicolaescu
2007-07-17 11:26         ` Eli Zaretskii
2007-07-17 11:39           ` Juanma Barranquero
2007-07-17 11:45           ` Andreas Schwab
2007-07-17 12:51             ` Thien-Thi Nguyen
2007-07-17 13:13               ` David Kastrup [this message]
2007-07-17 20:02               ` Eli Zaretskii
2007-07-17 20:03             ` Eli Zaretskii
2007-07-17 16:52           ` Stefan Monnier
2007-07-17 20:06             ` Eli Zaretskii
2007-07-17 22:11               ` Juanma Barranquero
2007-07-16 22:47 ` Eli Zaretskii
2007-07-17 10:07   ` Juanma Barranquero
2007-07-17 10:33     ` Eli Zaretskii

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=86bqebuqa8.fsf@lola.quinscape.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=ttn@gnuvola.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).