Author Topic: git error - possibly due to exclude filespec in wildcard  (Read 1563 times)

JeffB

  • Senior Community Member
  • Posts: 273
  • Hero Points: 11
git error - possibly due to exclude filespec in wildcard
« on: December 11, 2016, 03:45:38 am »
V 21.0.1 Windows 64-bit

When I start Slickedit, I get this error in the output window:
fatal: Not a git repository (or any of the parent directories): .git<LF>

I am basically trying to exclude any svn and git files and add a wildcard subtree.  The project properties are setup with this for Include Filespec:
*;*.*
and this for Exclude Filespec:
.svn\;.git\

I still don't understand why something like "*\.git\*" didn't work, but I noticed in other posts that ".git\" would work, so I used that.

The directories actually added (as wildcard) to the project file list (as shown in Project Properties) is:
..\..\work\*
..\..\work\*.*

The "work" directory on the drive looks like this:
work\.git
work\src

I'm wondering if the files and directories under the ".git" directory are excluded, but not the ".git" directory itself.  And since I've configured the project for git, Slickedit is complaining ??  I've tried numerous ways to also explicity exclude the ".git" directory, but the error kept getting generated on startup.

The error doesn't seem to break git functionality.  This older post:
https://community.slickedit.com/index.php/topic,11572.0.html

indicated the same error, but in that case, git operation was affected.

Is there a better way to exclude scn-type files? 
 (it'd be nice if Slickedit automatically excluded these files when a VCS is configured)

Jeff

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2049
  • Hero Points: 98
Re: git error - possibly due to exclude filespec in wildcard
« Reply #1 on: December 12, 2016, 02:24:18 pm »
If you go to Tools>Version Control>Setup, and click the Setup button, is "Show status on file icons" on?

JeffB

  • Senior Community Member
  • Posts: 273
  • Hero Points: 11
Re: git error - possibly due to exclude filespec in wildcard
« Reply #2 on: December 12, 2016, 03:02:43 pm »
Yes, Dan.  That option is on.

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2049
  • Hero Points: 98
Re: git error - possibly due to exclude filespec in wildcard
« Reply #3 on: December 12, 2016, 03:27:45 pm »
OK, that must be where the error message is coming from.  Is it working?

JeffB

  • Senior Community Member
  • Posts: 273
  • Hero Points: 11
Re: git error - possibly due to exclude filespec in wildcard
« Reply #4 on: December 12, 2016, 03:36:52 pm »
No.  I don't think it is working.  I guess I never noticed that option. I turned it on for my Linux sandboxes also and see the same error.

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2049
  • Hero Points: 98
Re: git error - possibly due to exclude filespec in wildcard
« Reply #5 on: December 12, 2016, 04:12:48 pm »
OK.  Let me see if I can fix that.  It will probably be a 21.0.2 fix.

JeffB

  • Senior Community Member
  • Posts: 273
  • Hero Points: 11
Re: git error - possibly due to exclude filespec in wildcard
« Reply #6 on: December 12, 2016, 04:37:49 pm »
Thanks, Dan.

I don't know if this has been mentioned before, but another nice feature related to VCS would be a command to update the change bars based (in the column with line numbers) on the VCS status/diff.  I can see how this would be resource-consuming to do in the background, but a manual trigger would be nice.  I like the change bars that show up in real-time, but these are rarely up-to-date for me due to closing/re-opening or submitting files via command-line in a different window.

Jeff

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2049
  • Hero Points: 98
Re: git error - possibly due to exclude filespec in wildcard
« Reply #7 on: December 12, 2016, 04:41:43 pm »
Thanks, Dan.

I don't know if this has been mentioned before, but another nice feature related to VCS would be a command to update the change bars based (in the column with line numbers) on the VCS status/diff.  I can see how this would be resource-consuming to do in the background, but a manual trigger would be nice.  I like the change bars that show up in real-time, but these are rarely up-to-date for me due to closing/re-opening or submitting files via command-line in a different window.

Jeff

I have been considering a feature just like this.  It's not a small undertaking (There are certain cases where I'm not sure how it would work), but it is on my radar.

On an initial pass, the Git status bitmap feature is working for me on Windows.  What version of Git are you using?

Do you see any red bitmaps on the Projects Tool window?  If you don't, what happens if you right click and uncheck "Show relative paths"? and restart the editor?  The dots should appear on modified files.
« Last Edit: December 12, 2016, 04:53:07 pm by Dan »

JeffB

  • Senior Community Member
  • Posts: 273
  • Hero Points: 11
Re: git error - possibly due to exclude filespec in wildcard
« Reply #8 on: December 12, 2016, 05:28:02 pm »
I'm using v2.11 on Windows and 2.9.3 on Linux.

I don't see any blue or red icons on the Project Tools window - not for workspaces using svn nor workspaces using git on neither Windows nor Linux.  I see a yellow triangle (?) only.

Unselecting "Show Relative Paths" didn't affect anything that I could tell.

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2049
  • Hero Points: 98
Re: git error - possibly due to exclude filespec in wildcard
« Reply #9 on: December 12, 2016, 05:39:36 pm »
Hmm, can you send me a screenshot of that?

JeffB

  • Senior Community Member
  • Posts: 273
  • Hero Points: 11
Re: git error - possibly due to exclude filespec in wildcard
« Reply #10 on: December 12, 2016, 05:58:49 pm »
The help says that if the VCS command returns >8MB, VS will automatically disable the "show file status icons".  I think that is probably what is happening on my SVN workspaces (tens of thousands of files).

I'll PM you a screenshot.

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2049
  • Hero Points: 98
Re: git error - possibly due to exclude filespec in wildcard
« Reply #11 on: December 12, 2016, 06:03:33 pm »
I thought you were using Git?

JeffB

  • Senior Community Member
  • Posts: 273
  • Hero Points: 11
Re: git error - possibly due to exclude filespec in wildcard
« Reply #12 on: December 12, 2016, 06:06:47 pm »
I'm using both (in different workspaces).

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2049
  • Hero Points: 98
Re: git error - possibly due to exclude filespec in wildcard
« Reply #13 on: December 12, 2016, 06:13:01 pm »
Ah.  I fixed a bug with status bitmaps in Subversion for 21.0.2.  And the relative file path thing in the projects tool window is another issue (but turning that off should have worked around it).  So I'm not surprised that Subversion doesn't work, but I didn't change any C code for Git.  With that workaround, I would expect it to work.