Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Where t out does not honor parent .timetrap.sheet file #109

Open
kotp opened this issue Mar 25, 2015 · 1 comment
Open

Where t out does not honor parent .timetrap.sheet file #109

kotp opened this issue Mar 25, 2015 · 1 comment

Comments

@kotp
Copy link

kotp commented Mar 25, 2015

If I am in a child folder of a project and I want to check out of timetrap it should honor the same sheet. I have several sheets and noticed this today.

I don't often change into sub-folders, but it surprised me, as it should probably search up the folder chain and look for that file.

What happened for me is that it complained that I was not on the "other project" time sheet when I did t out.

To simplify this:

When I am in a project
and I t in
I should start time on that project
when I change to a child folder of that project
and then I t out
I should stop time on that project

@kotp kotp changed the title Where .timetrap-sheet does not honor child folders location for t out Where t out does not honor parent .timetrap.sheet file Mar 25, 2015
@samg
Copy link
Owner

samg commented Apr 12, 2015

I agree that having timetrap look up the directory structure for a .timetrap-sheet file wouild be an improvement. I believe @UnderpantsGnome did the implementation of the .timetrap-sheet autosheets functionality and might be interested in making that change. You could also check out the docs on AutoSheets (https://github.com/samg/timetrap#autosheets) since that system was designed to be extensible to match various user workflows. I won't have time to work on this in the near future but would happily accept a pull request if you or someone else felt like making this improvement.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants