use of # is awkward for bash users about gr

[luolong]

+1

I do agree, that using a hash is awkward, and the results are umm less than imformative.

I would suggest revising README and documentation to reflect this. -t <tag> ... works perfectly.

[alexgorbatchev]

👍 can't run hashtags at all in zsh...

$ gr #app git status
zsh: bad pattern: #app

[alexgorbatchev]

I found an awkward workaround in zsh

$ gr '+#app' ./foo

[memming]

+1

I agree. '#' doesn't work very well for bash users since it makes rest of the line a comment.

[cackovic]

+1

I put in pull request #9 that adds support for '@'

[mixu]

Hi all, sorry for the delay on getting this merged. I realized I had accidentally unsubscribed from notifications on the repo so a lot of the recent issues went unnoticed. Will take a more active approach from now on, since it seems that a bunch of people find this project useful based on the number of stars. As a first step I'll merge that PR from @cackovic (thanks!) and get a new version out on npm, then see if I can get at least a few of the outstanding issues fixed. Thanks for you patience & support & interest.

[mixu]

published as v0.3.0

[alexcb]

awesome - thanks for making this happen. Thanks to @cackovic too. I'll give the project a try again.

[cackovic]

Thanks for the merge. I’m not sure about ‘@‘ as a longterm solution because I want my git commands to be fast to enter. Maybe we could remove the need for ‘#’ or ‘@‘? This would streamline my typing. What does anyone else think?

On Nov 30, 2014, at 3:33 PM, Alex Couture-Beil [email protected] wrote:

awesome - thanks for making this happen. Thanks to @cackovic https://github.com/cackovic too. I'll give the project a try again.

—
Reply to this email directly or view it on GitHub #1 (comment).

[mixu]

That would be OK, but I'd like to have some tests around it so that it doesn't cause issues when there are directories with the same name, e.g. gr ./foo status is a valid invocation but I'm not sure what should happen if you run gr foo status and both ./foo and the foo tag exist.

Edit:
Another case is if you have a tags called git and status:

with gr git status ./sub is it

• gr #git status ./sub (run status with ./sub argument in a tag set) or
• gr #git #status ./sub (run ./sub in two tag sets)
• gr ./git status ./sub (run status with ./sub argument in local folder) or
• gr ./git ./status ./sub (run ./sub in two local folders)

Seems like this could become a bit too complicated...

[luolong]

I am personally pretty used to invoking tags with gr -t tag by now that I really do not care all that much. I think typing @ instead of -t is already a big win in terms of keystrokes.

In any case, using tag names without any prefix what so ever seems way too ambiguous to justify.