IndexError: list index out of range

[Steve Borho]

On Tue, Sep 9, 2008 at 8:56 AM, Vincent Danjean <
Vincent.Danjean at ens-lyon.org> wrote:

> Matt Mackall wrote:
> > On Tue, 2008-08-26 at 19:29 +0200, Vincent Danjean wrote:
> >> Matt Mackall wrote:
> >>> The hgweb problem is just bizarre. Mercurial's fairly popular main repo
> >>> is served off a virtual server on a loaded box in my basement using
> slow
> >>> CGI over DSL, and the load from Mercurial is negligible. He's probably
> >>> got Pygments turned on by the silly Debian packaging.
> >> Can you tell me what should be changed in the Debian packaging ?
> >>
> >> Are you saying that turning off all extensions when installing mercurial
> >> would be better ?
> >
> > YES!
> >
> > Extensions provide *non-standard* functionality that may be unsafe,
> > slow, fragile, underdocumented, undersupported, or even just plain
> > discouraged (like keywords). If you want this non-standard
> > functionality, you should have to go through a manual step to enable it.
>
> Opening a bug with these arguments would have made me react quicker...
> Note that I tried to enable by default only extension that add features
> without modifying the plain behavior of mercurial. This means that
> extensions
> such as keywords, win32text, ... have *never* been enabled by default in
> any
> Debian package.
>  Another strong argument I read in this thread is the fact that a extension
> enabled system-wide cannot be disabled by a user. I thing that this is a
> really good reason not to enable any extension by default in the debian
> package.


Last I looked, you could disable an extension in your local hgrc with this
syntax:

[extensions]
qct = !
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20080909/10bd2511/attachment.htm