take-note-cli 1.2.0__tar.gz → 1.2.1__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {take_note_cli-1.2.0 → take_note_cli-1.2.1}/PKG-INFO +25 -40
- {take_note_cli-1.2.0 → take_note_cli-1.2.1}/README.md +24 -39
- {take_note_cli-1.2.0 → take_note_cli-1.2.1}/pyproject.toml +1 -1
- {take_note_cli-1.2.0 → take_note_cli-1.2.1}/LICENSE +0 -0
- {take_note_cli-1.2.0 → take_note_cli-1.2.1}/src/take_note_cli/__init__.py +0 -0
- {take_note_cli-1.2.0 → take_note_cli-1.2.1}/src/take_note_cli/__main__.py +0 -0
- {take_note_cli-1.2.0 → take_note_cli-1.2.1}/src/take_note_cli/core/__init__.py +0 -0
- {take_note_cli-1.2.0 → take_note_cli-1.2.1}/src/take_note_cli/core/notes.py +0 -0
- {take_note_cli-1.2.0 → take_note_cli-1.2.1}/src/take_note_cli/utils/__init__.py +0 -0
- {take_note_cli-1.2.0 → take_note_cli-1.2.1}/src/take_note_cli/utils/args.py +0 -0
- {take_note_cli-1.2.0 → take_note_cli-1.2.1}/src/take_note_cli/utils/dates.py +0 -0
- {take_note_cli-1.2.0 → take_note_cli-1.2.1}/src/take_note_cli/utils/paths.py +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.1
|
|
2
2
|
Name: take-note-cli
|
|
3
|
-
Version: 1.2.
|
|
3
|
+
Version: 1.2.1
|
|
4
4
|
Summary: Create and open notes in your favourite editor.
|
|
5
5
|
Home-page: https://github.com/wsinned/take-note
|
|
6
6
|
License: MIT
|
|
@@ -35,6 +35,7 @@ Description-Content-Type: text/markdown
|
|
|
35
35
|
- Open notes files for specified week using the `code` command line for VS Code.
|
|
36
36
|
- --thisWeek, --lastWeek and --nextWeek are supported.
|
|
37
37
|
- Organises notes in a date based folder structure from your root notes folder, e.g. 2023/08
|
|
38
|
+
- The default folder is $HOME/Notes
|
|
38
39
|
- set the root notes folder using --notesFolder
|
|
39
40
|
- Choose which editor to use with --editor
|
|
40
41
|
- Specify a VS Code workspace to open along with the note file with --workspace
|
|
@@ -78,12 +79,11 @@ A note will be created in the under the MyNotes/YYYY/mm folder named with the da
|
|
|
78
79
|
Setting up aliases in you preferred shell is a great way to make accessing your notes quick and easy.
|
|
79
80
|
|
|
80
81
|
```bash
|
|
81
|
-
|
|
82
|
-
args="--notesFolder $notes_folder --workspace notes.code-workspace --template Home-weekly-log-template.md"
|
|
82
|
+
NOTES_FOLDER="$HOME/SomePath/MyNotes"
|
|
83
83
|
|
|
84
|
-
alias thisWeek="take-note --thisWeek $
|
|
85
|
-
alias nextWeek="take-note --nextWeek $
|
|
86
|
-
alias lastWeek="take-note --lastWeek
|
|
84
|
+
alias thisWeek="take-note --thisWeek --notesFolder $NOTES_FOLDER --workspace notes.code-workspace"
|
|
85
|
+
alias nextWeek="take-note --nextWeek --notesFolder $NOTES_FOLDER --workspace notes.code-workspace --batch 5"
|
|
86
|
+
alias lastWeek="take-note --lastWeek --editor hx"
|
|
87
87
|
```
|
|
88
88
|
|
|
89
89
|
All you have to do now is type one of the following to open the desired note file.
|
|
@@ -116,43 +116,29 @@ venv/bin/pip install -e .
|
|
|
116
116
|
|
|
117
117
|
The supplied shell.nix definition provides support for entering a nix-shell directly in the repository with all dependencies.
|
|
118
118
|
|
|
119
|
-
```
|
|
119
|
+
```bash
|
|
120
120
|
nix-shell --run zsh # ensure using zsh over default bash session
|
|
121
|
-
|
|
122
|
-
# only needed once, or to recreate the virtual environment
|
|
123
|
-
python -m venv venv
|
|
124
|
-
|
|
125
|
-
source venv/bin/activate
|
|
126
|
-
|
|
127
|
-
# install with tests as editable src
|
|
128
|
-
venv/bin/pip install -e '.[test]'
|
|
129
|
-
|
|
130
|
-
# run the tests
|
|
131
|
-
pytest
|
|
132
|
-
|
|
133
|
-
# close the virtual environment and exit the shell when done
|
|
134
|
-
deactivate
|
|
135
|
-
exit
|
|
136
121
|
```
|
|
137
122
|
|
|
123
|
+
Then follow the instructions for other OS.
|
|
124
|
+
|
|
138
125
|
### Other Linux or macOS
|
|
139
126
|
|
|
140
|
-
```
|
|
127
|
+
```bash
|
|
141
128
|
# only needed once, or to recreate the virtual environment
|
|
142
|
-
|
|
143
|
-
|
|
144
|
-
source venv/bin/activate
|
|
145
|
-
|
|
146
|
-
venv/bin/pip install -r requirements.txt -r requirements.dev.txt
|
|
129
|
+
# install dependencies
|
|
130
|
+
poetry install
|
|
147
131
|
|
|
148
|
-
#
|
|
149
|
-
|
|
132
|
+
# enter an activated shell and run tests
|
|
133
|
+
poetry shell
|
|
134
|
+
pytest
|
|
135
|
+
ruff . --config pyproject.toml
|
|
150
136
|
|
|
151
|
-
# run the tests
|
|
152
|
-
|
|
137
|
+
# run the tests without activating a shell
|
|
138
|
+
poetry run pytest
|
|
153
139
|
|
|
154
|
-
#
|
|
155
|
-
|
|
140
|
+
# exit the shell
|
|
141
|
+
exit
|
|
156
142
|
```
|
|
157
143
|
|
|
158
144
|
## Linting
|
|
@@ -160,22 +146,21 @@ deactivate
|
|
|
160
146
|
The project uses [ruff](https://github.com/charliermarsh/ruff) for linting and optionally for formatting.
|
|
161
147
|
|
|
162
148
|
```bash
|
|
163
|
-
|
|
149
|
+
poetry run ruff . --config pyproject.toml
|
|
164
150
|
```
|
|
165
151
|
|
|
166
152
|
## Build & Publish
|
|
167
153
|
|
|
168
154
|
From an installed and tested venv, do the following:
|
|
169
155
|
|
|
170
|
-
|
|
171
|
-
# check the version:
|
|
172
|
-
cat src/takenote/__version__.py
|
|
156
|
+
Bump the version inpyproject.tom
|
|
173
157
|
|
|
158
|
+
```bash
|
|
174
159
|
# build the package
|
|
175
|
-
|
|
160
|
+
poetry build
|
|
176
161
|
|
|
177
162
|
# publish the package
|
|
178
|
-
|
|
163
|
+
poetry publish
|
|
179
164
|
```
|
|
180
165
|
|
|
181
166
|
Credentials for twine should be either:
|
|
@@ -9,6 +9,7 @@
|
|
|
9
9
|
- Open notes files for specified week using the `code` command line for VS Code.
|
|
10
10
|
- --thisWeek, --lastWeek and --nextWeek are supported.
|
|
11
11
|
- Organises notes in a date based folder structure from your root notes folder, e.g. 2023/08
|
|
12
|
+
- The default folder is $HOME/Notes
|
|
12
13
|
- set the root notes folder using --notesFolder
|
|
13
14
|
- Choose which editor to use with --editor
|
|
14
15
|
- Specify a VS Code workspace to open along with the note file with --workspace
|
|
@@ -52,12 +53,11 @@ A note will be created in the under the MyNotes/YYYY/mm folder named with the da
|
|
|
52
53
|
Setting up aliases in you preferred shell is a great way to make accessing your notes quick and easy.
|
|
53
54
|
|
|
54
55
|
```bash
|
|
55
|
-
|
|
56
|
-
args="--notesFolder $notes_folder --workspace notes.code-workspace --template Home-weekly-log-template.md"
|
|
56
|
+
NOTES_FOLDER="$HOME/SomePath/MyNotes"
|
|
57
57
|
|
|
58
|
-
alias thisWeek="take-note --thisWeek $
|
|
59
|
-
alias nextWeek="take-note --nextWeek $
|
|
60
|
-
alias lastWeek="take-note --lastWeek
|
|
58
|
+
alias thisWeek="take-note --thisWeek --notesFolder $NOTES_FOLDER --workspace notes.code-workspace"
|
|
59
|
+
alias nextWeek="take-note --nextWeek --notesFolder $NOTES_FOLDER --workspace notes.code-workspace --batch 5"
|
|
60
|
+
alias lastWeek="take-note --lastWeek --editor hx"
|
|
61
61
|
```
|
|
62
62
|
|
|
63
63
|
All you have to do now is type one of the following to open the desired note file.
|
|
@@ -90,43 +90,29 @@ venv/bin/pip install -e .
|
|
|
90
90
|
|
|
91
91
|
The supplied shell.nix definition provides support for entering a nix-shell directly in the repository with all dependencies.
|
|
92
92
|
|
|
93
|
-
```
|
|
93
|
+
```bash
|
|
94
94
|
nix-shell --run zsh # ensure using zsh over default bash session
|
|
95
|
-
|
|
96
|
-
# only needed once, or to recreate the virtual environment
|
|
97
|
-
python -m venv venv
|
|
98
|
-
|
|
99
|
-
source venv/bin/activate
|
|
100
|
-
|
|
101
|
-
# install with tests as editable src
|
|
102
|
-
venv/bin/pip install -e '.[test]'
|
|
103
|
-
|
|
104
|
-
# run the tests
|
|
105
|
-
pytest
|
|
106
|
-
|
|
107
|
-
# close the virtual environment and exit the shell when done
|
|
108
|
-
deactivate
|
|
109
|
-
exit
|
|
110
95
|
```
|
|
111
96
|
|
|
97
|
+
Then follow the instructions for other OS.
|
|
98
|
+
|
|
112
99
|
### Other Linux or macOS
|
|
113
100
|
|
|
114
|
-
```
|
|
101
|
+
```bash
|
|
115
102
|
# only needed once, or to recreate the virtual environment
|
|
116
|
-
|
|
117
|
-
|
|
118
|
-
source venv/bin/activate
|
|
119
|
-
|
|
120
|
-
venv/bin/pip install -r requirements.txt -r requirements.dev.txt
|
|
103
|
+
# install dependencies
|
|
104
|
+
poetry install
|
|
121
105
|
|
|
122
|
-
#
|
|
123
|
-
|
|
106
|
+
# enter an activated shell and run tests
|
|
107
|
+
poetry shell
|
|
108
|
+
pytest
|
|
109
|
+
ruff . --config pyproject.toml
|
|
124
110
|
|
|
125
|
-
# run the tests
|
|
126
|
-
|
|
111
|
+
# run the tests without activating a shell
|
|
112
|
+
poetry run pytest
|
|
127
113
|
|
|
128
|
-
#
|
|
129
|
-
|
|
114
|
+
# exit the shell
|
|
115
|
+
exit
|
|
130
116
|
```
|
|
131
117
|
|
|
132
118
|
## Linting
|
|
@@ -134,22 +120,21 @@ deactivate
|
|
|
134
120
|
The project uses [ruff](https://github.com/charliermarsh/ruff) for linting and optionally for formatting.
|
|
135
121
|
|
|
136
122
|
```bash
|
|
137
|
-
|
|
123
|
+
poetry run ruff . --config pyproject.toml
|
|
138
124
|
```
|
|
139
125
|
|
|
140
126
|
## Build & Publish
|
|
141
127
|
|
|
142
128
|
From an installed and tested venv, do the following:
|
|
143
129
|
|
|
144
|
-
|
|
145
|
-
# check the version:
|
|
146
|
-
cat src/takenote/__version__.py
|
|
130
|
+
Bump the version inpyproject.tom
|
|
147
131
|
|
|
132
|
+
```bash
|
|
148
133
|
# build the package
|
|
149
|
-
|
|
134
|
+
poetry build
|
|
150
135
|
|
|
151
136
|
# publish the package
|
|
152
|
-
|
|
137
|
+
poetry publish
|
|
153
138
|
```
|
|
154
139
|
|
|
155
140
|
Credentials for twine should be either:
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|