Michael Brouwer wrote:
> Am I the only one who thinks it's actually useful to see that I have
> unsaved
> changes open in an editor when a run svn st? Whenever I see a .swp file I
> first make sure to save my changes in progress and them run svn update or
> whatever command I was going to run.
The .swp file exists when a file is open, so it's really not that great
of an indicator of whether there are unsaved changes or not. In cases
where someone may have several files open, but only editing a few, the
extra output can get in the way.
I do think that adding it to SVN_CONFIG_DEFAULT_GLOBAL_IGNORES would be
a good idea, though. It wouldn't be on by default, of course, and you'd
still see everything when running 'svn st'.
-Hyrum
> On 4/1/07, Daniel Rall <dlr@collab.net> wrote:
>>
>> On Sat, 31 Mar 2007, David Glasser wrote:
>>
>> > On 3/31/07, Hyrum K. Wright <hyrum_wright@mail.utexas.edu> wrote:
>> > >Martin Furter wrote:
>> > >> Those .swp files aren't project specific so why not add it to the
>> > >> default global-ignores?
>> > >
>> > >One may also argue that *~ and .*~ aren't project specific, either. :)
>> > >
>> > >Either way, I'm beyond caring at this point.
>> >
>> > Right, which is why it seems like a reasonable suggestion to add
>> > .*.swp (and .*.swo, etc) to SVN_CONFIG_DEFAULT_GLOBAL_IGNORES.
>>
>> +1, go for it.
>>
>>
>
Received on Mon Apr 2 23:02:25 2007