Where the heck is the default setting for Exclude Filespecs?

[mrothman]

Somewhere in the paleolithic era (I've been using Slickedit for a couple decades) I somehow set things up so that when I go to the "Project Properties" dialog, and then select "Add Tree", it has an already populated entry in the Exclude Filespecs.  I used to want this (it excluded CVS directories from being added).  But now I don't (company switched to Perforce) and I cannot remember how I put it there.  Or, more accurately, I thought I remembered putting it there by modifying userpjrtemplates.vpt or indirectly by customizing a project type through the GUI.  But it's not in the vpt file, or any of several project (vpj) files I checked, and in fact it shows up regardless of what project type/language I am in, including project types I have never used.  Where would it be?  Did I somehow get it stuck in some global binary configuration that doesn't get changed?  Or maybe I just am totally mis-remembering.

[Graeme]

If you click the dropdown arrow for exclude filespecs, it should show you all values you've ever entered there.  These values are stored in a file called vrestore.slk but you can't just go editing vrestore.slk.
http://community.slickedit.com/index.php/topic,10007.msg42441.html#msg42441
The dialog should come up with whatever value you last entered there.  Does it not do that?

[mrothman]

Hi Graeme.  Thanks for the reply, and I experimented further. If I put something new in the text box, it does indeed show up the next time.  But if I just clear the box, then the previous non-blank value shows up the next time.  I'd like the default to be blank, since I don't normally want to exclude anything.  Of course, now that you've shown me what's happening, I could put some nonsense value there that will not actually exclude anything, but that's just a workaround.

I also tried (after backing it up) carefully removing the old values from vrestore.slk with another editor.  That did the trick, but of course as soon as I ever need to exclude some filespec again, I'm in the same situation.  That is, having the most recent value be "no exclusions" doesn't seem to stick, but the others do.  I'm going to try it one more time, since it's possible that years of modification had gotten my vrestore.slk file into some kind of loop.

[Sandra]

We are not saving the last value if it is blank.  I can fix that for the next release.  Thanks for the bug report!

[mrothman]

Great, thanks again, that sounds good.

[JeffB]

Sandra, While you are in there, could you also fix the "Include filespecs".  I always use "*", but it nearly always defaults to "*.*".  I'm on Linux if it matters.

Jeff

[Sandra]

Sure, I'll check on that, too.