%global _empty_manifest_terminate_build 0
Name: python-td-cli
Version: 2.0.3
Release: 1
Summary: A todo command line manager
License: MIT
URL: https://github.com/darrikonn/td-cli
Source0: https://mirrors.aliyun.com/pypi/web/packages/c4/d5/66b8103345f8bab68b6d00b9571fe8744622cb557d3ab5a8c9d08b38a14b/td-cli-2.0.3.tar.gz
BuildArch: noarch
%description
td-cli is a command line todo manager,
where you can organize and manage your todos across multiple projects
## Installation
[**td-cli**](https://pypi.org/project/td-cli/) only works for `python 3`, so it needs to be installed with `pip3`
```bash
pip3 install td-cli
```
## Getting started
Run `td --help` to see possible commands.
Here are some to get you started:
- Run `td` to list all your todos.
- Run `td add "my new awesome todo"` to add a new todo.
- Run `td complete` to complete your todo. You don't have to specify the whole `id`, a substring will do. It'll fetch the first one that it finds in the same order as when you list your todos.
Note that `global` is a preserved group name where you can list all your global groups. You can always set it as the default with:
```bash
td group global preset
```
## API
Check out the [`api`](https://github.com/darrikonn/td-cli/blob/master/API.md).
## Configuring
The location of your todos and your configuration will depend on these environment variables (in this order):
1. **TD_CLI_HOME**: determines where your `todo.db` and `todo.cfg` file will live
2. **XDG_CONFIG_HOME**: a fallback if `$TD_CLI_HOME` is not set
3. **HOME**: a fallback if `$XDG_CONFIG_HOME` is not set. If `$HOME` is used; all files will be transformed to a dotfile, i.e.`~/.todo.db` and `~/.todo.cfg`.
### Database name
Your database instance will be located in in the before-mentioned configuration directory.
By default the database will be named `todo`.
You can change your database name by specifying `database_name` in your `$TD_CLI_HOME/.todo.cfg` file:
```cfg
[settings]
database_name: something_else
```
This results in a database instance at `$TD_CLI_HOME/.something_else.db`
### Format
You can specify your preferred format of your todo's details via the format config keyword:
```cfg
format: md
```
This would result in the `.md` (Markdown) file extension when editing a todo. This allows you to use the power of your editor to e.g. syntax highlight the details, and etc.
### Editor
When editing a todo, `td edit`, you can both specify the todo's `name` and the todo's `details` via options (see `td edit --help`). If no option is specified, your todo will be opened in `vi` by default (your `environement EDITOR` will override this) where you can edit the todo's details. You can change the default editor by updating your config:
```cfg
[settings]
editor: nvim
```
### Group
When listing todos, you have the option of specifying what group to list from:
```bash
td -g my-group
# or
td g my-group
```
If no group is provided, `td` will list from the current default group. You can globally set the default group with:
```bash
td g my-group preset
```
However, there's an option to set the default group per git project (this is not possible from the root config `$TD_CLI_HOME/.todo.cfg`).
In any root of your projects, you can create a `.td.cfg` config file to specify what group to default on (this will override the global default group):
```cfg
[settings]
group: my-group
```
If you run `td` within your git project, td will default to *my-group*.
I recommend globally ignoring `.td.cfg` in `~/.gitignore`.
%package -n python3-td-cli
Summary: A todo command line manager
Provides: python-td-cli
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-td-cli
td-cli is a command line todo manager,
where you can organize and manage your todos across multiple projects
## Installation
[**td-cli**](https://pypi.org/project/td-cli/) only works for `python 3`, so it needs to be installed with `pip3`
```bash
pip3 install td-cli
```
## Getting started
Run `td --help` to see possible commands.
Here are some to get you started:
- Run `td` to list all your todos.
- Run `td add "my new awesome todo"` to add a new todo.
- Run `td complete` to complete your todo. You don't have to specify the whole `id`, a substring will do. It'll fetch the first one that it finds in the same order as when you list your todos.
Note that `global` is a preserved group name where you can list all your global groups. You can always set it as the default with:
```bash
td group global preset
```
## API
Check out the [`api`](https://github.com/darrikonn/td-cli/blob/master/API.md).
## Configuring
The location of your todos and your configuration will depend on these environment variables (in this order):
1. **TD_CLI_HOME**: determines where your `todo.db` and `todo.cfg` file will live
2. **XDG_CONFIG_HOME**: a fallback if `$TD_CLI_HOME` is not set
3. **HOME**: a fallback if `$XDG_CONFIG_HOME` is not set. If `$HOME` is used; all files will be transformed to a dotfile, i.e.`~/.todo.db` and `~/.todo.cfg`.
### Database name
Your database instance will be located in in the before-mentioned configuration directory.
By default the database will be named `todo`.
You can change your database name by specifying `database_name` in your `$TD_CLI_HOME/.todo.cfg` file:
```cfg
[settings]
database_name: something_else
```
This results in a database instance at `$TD_CLI_HOME/.something_else.db`
### Format
You can specify your preferred format of your todo's details via the format config keyword:
```cfg
format: md
```
This would result in the `.md` (Markdown) file extension when editing a todo. This allows you to use the power of your editor to e.g. syntax highlight the details, and etc.
### Editor
When editing a todo, `td edit`, you can both specify the todo's `name` and the todo's `details` via options (see `td edit --help`). If no option is specified, your todo will be opened in `vi` by default (your `environement EDITOR` will override this) where you can edit the todo's details. You can change the default editor by updating your config:
```cfg
[settings]
editor: nvim
```
### Group
When listing todos, you have the option of specifying what group to list from:
```bash
td -g my-group
# or
td g my-group
```
If no group is provided, `td` will list from the current default group. You can globally set the default group with:
```bash
td g my-group preset
```
However, there's an option to set the default group per git project (this is not possible from the root config `$TD_CLI_HOME/.todo.cfg`).
In any root of your projects, you can create a `.td.cfg` config file to specify what group to default on (this will override the global default group):
```cfg
[settings]
group: my-group
```
If you run `td` within your git project, td will default to *my-group*.
I recommend globally ignoring `.td.cfg` in `~/.gitignore`.
%package help
Summary: Development documents and examples for td-cli
Provides: python3-td-cli-doc
%description help
td-cli is a command line todo manager,
where you can organize and manage your todos across multiple projects
## Installation
[**td-cli**](https://pypi.org/project/td-cli/) only works for `python 3`, so it needs to be installed with `pip3`
```bash
pip3 install td-cli
```
## Getting started
Run `td --help` to see possible commands.
Here are some to get you started:
- Run `td` to list all your todos.
- Run `td add "my new awesome todo"` to add a new todo.
- Run `td complete` to complete your todo. You don't have to specify the whole `id`, a substring will do. It'll fetch the first one that it finds in the same order as when you list your todos.
Note that `global` is a preserved group name where you can list all your global groups. You can always set it as the default with:
```bash
td group global preset
```
## API
Check out the [`api`](https://github.com/darrikonn/td-cli/blob/master/API.md).
## Configuring
The location of your todos and your configuration will depend on these environment variables (in this order):
1. **TD_CLI_HOME**: determines where your `todo.db` and `todo.cfg` file will live
2. **XDG_CONFIG_HOME**: a fallback if `$TD_CLI_HOME` is not set
3. **HOME**: a fallback if `$XDG_CONFIG_HOME` is not set. If `$HOME` is used; all files will be transformed to a dotfile, i.e.`~/.todo.db` and `~/.todo.cfg`.
### Database name
Your database instance will be located in in the before-mentioned configuration directory.
By default the database will be named `todo`.
You can change your database name by specifying `database_name` in your `$TD_CLI_HOME/.todo.cfg` file:
```cfg
[settings]
database_name: something_else
```
This results in a database instance at `$TD_CLI_HOME/.something_else.db`
### Format
You can specify your preferred format of your todo's details via the format config keyword:
```cfg
format: md
```
This would result in the `.md` (Markdown) file extension when editing a todo. This allows you to use the power of your editor to e.g. syntax highlight the details, and etc.
### Editor
When editing a todo, `td edit`, you can both specify the todo's `name` and the todo's `details` via options (see `td edit --help`). If no option is specified, your todo will be opened in `vi` by default (your `environement EDITOR` will override this) where you can edit the todo's details. You can change the default editor by updating your config:
```cfg
[settings]
editor: nvim
```
### Group
When listing todos, you have the option of specifying what group to list from:
```bash
td -g my-group
# or
td g my-group
```
If no group is provided, `td` will list from the current default group. You can globally set the default group with:
```bash
td g my-group preset
```
However, there's an option to set the default group per git project (this is not possible from the root config `$TD_CLI_HOME/.todo.cfg`).
In any root of your projects, you can create a `.td.cfg` config file to specify what group to default on (this will override the global default group):
```cfg
[settings]
group: my-group
```
If you run `td` within your git project, td will default to *my-group*.
I recommend globally ignoring `.td.cfg` in `~/.gitignore`.
%prep
%autosetup -n td-cli-2.0.3
%build
%py3_build
%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
find usr/lib -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
find usr/lib64 -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
find usr/bin -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
find usr/sbin -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
find usr/share/man -type f -printf "\"/%h/%f.gz\"\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .
%files -n python3-td-cli -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Tue Jun 20 2023 Python_Bot - 2.0.3-1
- Package Spec generated