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

Add ability to easily switch between TaskWarrior databases #235

Open
thehunmonkgroup opened this issue Apr 15, 2020 · 4 comments
Open

Add ability to easily switch between TaskWarrior databases #235

thehunmonkgroup opened this issue Apr 15, 2020 · 4 comments
Assignees

Comments

@thehunmonkgroup
Copy link
Member

Feature request culled from #233

An approach like this would allow pretty easy switching between TaskWarrior databases:

  • A configuration option to specify 'shortcuts' to various task databases
  • A new action that would allow a user to enter a shortcut name, which would then reload VIT with the task database the shortcut refers to.

Should be pretty efficient, for the following reasons:

  • The action would be bound to a key, just hit the keyboard shortcut and enter the alias. Both history and tab completion would be supported for alias name
  • I believe you could also map additional keyboard shortcuts to do a direct switch to a particular task database.
@fdela
Copy link
Collaborator

fdela commented Jul 23, 2020

Only somewhat related, but it would be nice if vit could accept a command line parameter specifying data folder to use.
That could be used to feed task with e.g. a default rc.data.location override, or possibly setting the TASKDATA envvar appropriately beforehand.
Alternatively allow passthrough command line param, which could e.g. also be used to specify alternate taskrc location (but there could be dragons)

Anyway, thanks for the good work!

@scottkosty
Copy link
Member

I haven't tried it, but do things work as you want if you export TASKDATA to the location you want before calling vit?

@fdela
Copy link
Collaborator

fdela commented Jul 24, 2020

Yes, that variable is used by TaskWarrior (and indirectly by vit) once it's set/exported, and things work as expected

You can use task rc.data.location:alternateDataLocationDirectory rc:alternateTaskrcConfFile ... or set associated TASKDATA and TASKRC environment variables.

See "CONFIGURATION FILE AND OVERRIDE OPTIONS" section in task(1) manpage for details.

@thehunmonkgroup
Copy link
Member Author

@fdela I think your idea should probably be filed as a separate feature request.

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

No branches or pull requests

3 participants