Similar repository name with 'c' shortcut

[dmitry-saritasa]

$ c --list
8 Git repositories in /home/dmitry/code:

backend              ~/code/anyevent/backend
backend              ~/code/trivver/backend
batching             ~/code/trivver/batching
cascalog-examples    ~/code/experiments/cascalog-examples
phind                ~/code/phind
sa3p                 ~/code/sa3p/sa3p
storm                ~/code/trivver/storm
streamparse          ~/code/experiments/storm/streamparse

as you can see we have 2 'backend' repository. Is there a way to give (like put .scm file inside directory to give it a different name) it a different name?

[ghthor]

I don't use the code manager. Could you reply with how this causes a problem? Is the behavior consistent if you try to cd to backend? You may want to talk test this in isolation via a VM env

On Wednesday, October 26, 2016, Dmitry Semenov notifications@github.com wrote:

$ c --list 8 Git repositories in /home/dmitry/code:

backend ~/code/anyevent/backend backend ~/code/trivver/backend batching ~/code/trivver/batching cascalog-examples ~/code/experiments/cascalog-examples phind ~/code/phind sa3p ~/code/sa3p/sa3p storm ~/code/trivver/storm streamparse ~/code/experiments/storm/streamparse

as you can see we have 2 'backend' repository. Is there a way to give (like put .scm file inside directory to give it a different name) it a different name?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/scmbreeze/scm_breeze/issues/214, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJyKjB9sAidYzQh20PR1bYxOJn2QLvfks5q4AwpgaJpZM4Kh4Ip .

[dmitry-saritasa]

the problem is how to get to 2nd backend? c backend routes you to first element ~/code/anyevent/backend

however It would be nice if I can place a local file in ~/code/anyevent/backend/.scmbreeze with just single line 'anyevent' that should be used during scmbreeze indexing

[ghthor]

Well it's good that's it's consistent. I'll dig into the code to see if I come up with any other ideas. I'd rather have it be smarter then have to add a dot file into repository root, but maybe that will be a simple solution :)

On Thursday, October 27, 2016, Dmitry Semenov notifications@github.com wrote:

the problem is how to get to 2nd backend? c backend routes you to first element ~/code/anyevent/backend

however It would be nice if I can place a local file in ~/code/anyevent/backend/.scmbreeze with just single line 'anyevent' that should be used during scmbreeze indexing

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/scmbreeze/scm_breeze/issues/214#issuecomment-256754977, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJyKrtx2NaFcXQjVUuzZDVFqYs4vyTgks5q4QUWgaJpZM4Kh4Ip .

[dmitry-saritasa]

by the way pyenv uses such approach after calling pyenv local - it will place dot file in the root to activate virtualenv automatically. I find it elegant and not obtrusive.