default ignores don't ignore '.swp'

[Jan Hudec]

On Mon, Jan 09, 2006 at 14:15:37 -0500, Aaron Bentley wrote:
> > Also, a bzr upgrade can do something like make .DS_Store ignored
> > everywhere, rather than having to manually do it in every project that
> > now has a non-default ignore set.
> 
> Yes, there are other situations where it's handy to add new default
> ignores, too.  But if I have to chose between default-ignoring new types
> and being able to override defaults, I'll take the latter.  I'd be
> happier if I didn't have to make that choice.

Oh, no. Ignore patterns differing by client version! Aaargh! Flee!
Ok, I am exagerating a |=========================================| bit.
Basically, I don't think that adding new default ignores is a good
thing. I think the behaviour of things like this should depend on the
project and the user setting only.

I believe a project should only ignore files that actually appear in
that project. Ie. don't exclude *.o or core* in pure python project etc.

I thing the user should be able to add their local patterns. Eg. if
someone uses an editor that makes files like .{*}, they should have a
way to ignore that for all their projects. .*.swp would be default
there.

-- 
						 Jan 'Bulb' Hudec <bulb at ucw.cz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060110/17c584ba/attachment.pgp