Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Ability to implicitly set a default filename through environment variables #197

Closed
hovsater opened this issue Jul 8, 2022 · 1 comment
Closed

Comments

@hovsater
Copy link

hovsater commented Jul 8, 2022

I tend to have a one .klg file per project to track the amount of time I've spent on it. While bookmarks is a nice feature, it's also kind of repetitive having to specify it over and over again. It would be nice if you could implicitly tell klog what file to use through an environment variable. This goes really well together with direnv.

This would allow me to create a .envrc file in the root of my project, add export KLOG_FILE=./proj.klg to it and let direnv automatically export it for me. klog would then automatically pick up the KLOG_FILE environment variableif it were present.

What do you think?

@jotaen
Copy link
Owner

jotaen commented Jul 11, 2022

Thanks for the suggestion, I didn’t know about direnv.

I have to admit, I’m slightly reluctant to add more ways to specify input, in order to keep the complexity contained. I wouldn’t rule it out, but I probably have to think more about it.

it's also kind of repetitive having to specify it over and over again

Do you mean it’s repetitive to type the bookmark name when using it, or to set it up in the first place? Personally, I always assign two-letter bookmark names, e.g. @hw for housework.klg. I’m also hoping for klog to support shell completion soon, which would help to speed up the typing as well. (Unfortunately, that’s currently blocked on an issue with a third-party library.)

Repository owner locked and limited conversation to collaborators Jul 19, 2022
@jotaen jotaen converted this issue into discussion #203 Jul 19, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants