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.

Sign up for GitHub

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

Jump to bottom

Multiple Active Context #20

Closed
ChicK00o opened this issue Jun 11, 2020 · 7 comments
Closed

Multiple Active Context #20

ChicK00o opened this issue Jun 11, 2020 · 7 comments

Comments

@ChicK00o
Copy link

So using iterm, i would like to keep different context in different window, to use it as different active boards to work on, any ideas on this.
Tried doing it, but changing the context changes it globally across different iterm planes
@naggie
Copy link
Owner

naggie commented Jun 11, 2020

The only way you can currently do this is to use a different repository per tab. You could have a bash script in your bashrc that sets the dstask repo location based on the git project, for instance. The environment variable is DSTASK_GIT_REPO

I have considered allowing a .dstask-context file that dstask will search for to set context based on project, or an environment variable to set context. I'm not sure at the moment.

@stianlagstad
Copy link
Contributor

Setting the DSTASK_GIT_REPO using https://direnv.net/ could be a solution.

@naggie
Copy link
Owner

naggie commented Jun 13, 2020

Thinking about it, I think envdir plus a new environment variable, DSTASK_CONTEXT_OVERRIDE or something could be a nice solution. I'll leave this open as I will implement it.

dontlaugh added a commit to gloriousfutureio/dstask that referenced this issue Oct 31, 2020
@dontlaugh
Allow setting context with DSTASK_CONTEXT
2c68b4b 
If this env var is set to a valid context string, it takes precedence
over context stored in local state. The "--" ignore context token will
still be respected, however.

Refs naggie#20
@dontlaugh dontlaugh mentioned this issue Oct 31, 2020
Merged
@dontlaugh
Copy link
Contributor

Working on a version of this in #66

dontlaugh added a commit to gloriousfutureio/dstask that referenced this issue Oct 31, 2020
@dontlaugh
Allow setting context with DSTASK_CONTEXT
c962b4e 
If this env var is set to a valid context string, it takes precedence
over context stored in local state. The "--" ignore context token will
still be respected, however.

Space-separated strings are allowed in DSTASK_CONTEXT. We tokenize
before passing to ParseCmdLine

Refs naggie#20
@dontlaugh
Copy link
Contributor

If anyone is willing to build from the master branch, context can now be set/overridden with the DSTASK_CONTEXT environment variable. For example: export DSTASK_CONTEXT="+work -waiting"

@naggie
Copy link
Owner

naggie commented Nov 10, 2020

Actually it's built into v0.23.1 -- I forgot to add that to the release note, sorry! I've amended the release note. https://github.com/naggie/dstask/releases/tag/v0.23.1

@Dieterbe
Copy link
Contributor

looks like this can be closed.

@naggie naggie mentioned this issue Apr 5, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@Dieterbe @naggie @stianlagstad @ChicK00o @dontlaugh