Tabs to spaces

[Olaf van der Spek]

Some editors/people prefer/use tabs, others use spaces. Could you add a rule to the rules file that allows bzr to convert tabs to a specified number of spaces?

[Jelmer Vernooij (jelmer)]

Rather than putting this in core it might make sense for us to publish an example plugin that demonstrates things like this. There are lots of variations to this theme.

[Olaf van der Spek (olafvdspek)]

On Wed, Mar 23, 2011 at 9:56 PM, Jelmer Vernooij
<email address hidden> wrote:
> Rather than putting this in core it might make sense for us to publish
> an example plugin that demonstrates things like this. There are lots of
> variations to this theme.

What are the variations?

--
Olaf

[Jelmer Vernooij (jelmer)]

On Wed, 2011-03-23 at 21:14 +0000, Olaf van der Spek wrote:
> On Wed, Mar 23, 2011 at 9:56 PM, Jelmer Vernooij
> <email address hidden> wrote:
> > Rather than putting this in core it might make sense for us to publish
> > an example plugin that demonstrates things like this. There are lots of
> > variations to this theme.
> What are the variations?
Expanding tabs, checking copyright headers for years, checking files for
licenses, stripping trailing whitespace, enforcing particular C
indentation styles, etc.

It is certainly possible to add options to bzr for these things, and for
the common ones (like expanding tabs) I think it's reasonable to do so.
That said, there are a lot of things we are working on at the moment and
this isn't very high on our list. In the short term I think it'd be much
more useful if we provided some better infrastructure that allowed users
to write a ten-line python plugin that enforced their particular style
guide.

Cheers,

Jelmer

[Olaf van der Spek (olafvdspek)]

On Thu, Mar 24, 2011 at 2:13 PM, Jelmer Vernooij
<email address hidden> wrote:
> On Wed, 2011-03-23 at 21:14 +0000, Olaf van der Spek wrote:
>> On Wed, Mar 23, 2011 at 9:56 PM, Jelmer Vernooij
>> <email address hidden> wrote:
>> > Rather than putting this in core it might make sense for us to publish
>> > an example plugin that demonstrates things like this. There are lots of
>> > variations to this theme.
>> What are the variations?
> Expanding tabs, checking copyright headers for years, checking files for
> licenses, stripping trailing whitespace, enforcing particular C
> indentation styles, etc.

Trailing whitespace affects diffs and leading whitespace differences
are invisible and depended on editor settings.
But yeah, a generic way to handle this with a plugin would be nice.

Olaf