Parse error after new installation

[lastcoolnameleft]

Check list

• [ X ] I have read through the README
• [ X ] I have the latest version of forgit
• [ X ] I have searched through the existing issues

Environment info

• OS
  • [ ] Linux
  • [ X ] Mac OS X
  • [ ] Windows
  • [ ] Others:
• Shell
  • [ ] bash
  • [ X ] zsh
  • [ ] fish

Problem / Steps to reproduce

My scenario:

• Install fzf via Brew
• Cloned forgit repo and source via . ~/git/tmp/forgit/forgit.plugin.zsh
• Run glo and get error in right-side window:

  zsh:1: parse error near `|`

[cjappl]

Assigning to @wfxr

[rablador]

Having the same setup and same error.

[cjappl]

EDIT: Sorry, this was a response to another ticket that got scrambled somehow. please disregard

[dykwok]

@lastcoolnameleft , @cjappl you can check your .gitconfig settings, and set "pager" as pager = less -FRSX. It works for me.

[rablador]

Still same problem for me :/

[cjappl]

@carlfriedrich any ideas here?

[carlfriedrich]

No concrete idea, but @lastcoolnameleft @rablador can you maybe checkout my branch from #241 and see if the error appears there as well?

[rablador]

Running git forgit from the branch "move-implementation-to-standalone-forgit", with PATH pointing to the bin folder yields:

git-forgit: line 526: forgit: command not found

[carlfriedrich]

@rablador Thanks for your feedback. What was the exact command that you tried? git forgit alone doesn't do anything, since we need to provide a forgit subcommand like git forgit log. But nevertheless git forgit alone should provide a useful error message, I will add a patch for that.

[rablador]

Ah, right, I forgot to add a command! It works! :D

[carlfriedrich]

@rablador Great, so the error from this issue is gone on the new branch? We will merge this in the next few days, so then the issue should be solved in master as well.

@lastcoolnameleft What about you, can you verify this in your environment?

[rablador]

@carlfriedrich Yeah, from the branch "move-implementation-to-standalone-forgit" everything works as expected as long as I supply a command for git forgit. :)

[carlfriedrich]

@rablador Great, thank you. I already added a commit to the branch which displays a useful error message if no or an invalid command is given, so that shouldn't be a problem anymore either. :-)

[carlfriedrich]

241 has been merged, so after the feedback from @rablador I am considering this fixed. If anyone still has this problem, please open a new issue.