evilhero wrote: ↑Sat Jan 19, 2019 6:51 pm
What sir bbq said
If your git is on master, but your git_branch is set to development, you're on master - and the search patches for dog went into master a few days ago. If you're git is on dev, and your git_branch says master then you're on dev. Either way if your git_branch isn't the same as the actual git branch running the update will result in it not cloning properly.
Also, your git_path should be set to the full path to your git.exe file just to ensure things are correct.
If you can't find stuff via dog, since none of us use dog - paste in the debug log for a search and we can see but with the new search code changes it should be working fine when titles in the search results have decimals as space delimiters.
Heh Interesting from the UI
Mylar Version: development
-- git build 2bee5d46574e0f0bc7d0c067d8231444affd356d.
Python Version : 2.7.9
Language : en_US.cp1252
From the ini
git_user = evilhero
check_github = True
git_path = C:\Program Files\Git\bin
check_github_on_startup = True
git_branch = development
Try doing a git status |more from the command line in the root directory of mylar. It'll say at the top of the output what branch you're actually running. When you did the git pull it showed only the master branch syncing up with master commits.
Also, it needs the full path in your git_path variable so you need to include the git.exe in there as well.
evilhero wrote: ↑Sat Jan 19, 2019 8:57 pm
Try doing a git status |more from the command line in the root directory of mylar. It'll say at the top of the output what branch you're actually running. When you did the git pull it showed only the master branch syncing up with master commits.
Also, it needs the full path in your git_path variable so you need to include the git.exe in there as well.
On branch development
Your branch is up-to-date with 'origin/development'.
Untracked files:
(use "git add <file>..." to include in what will be committed)