You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Refactor mise documentation and enhance journal entries
- Updated the May 10, 2025 journal entry to improve organization and clarity regarding MCP servers and CLI tools.
- Added a new journal entry for May 11, 2025, detailing mise documentation, including tools and usage instructions.
- Created new pages for mise tools, including core and overview documentation, enhancing accessibility and usability for users.
- Revised existing documentation to clarify nested configurations and common commands for mise, improving overall guidance.
- `~/work/project/mise.local.toml` - Project-specific settings that should not be shared
13
13
- `mise` will use all the parent directories together to determine the set of tools—overriding configuration as it goes lower in the hierarchy.
14
14
- #Tip - Use [[mise/config/ls]] to see the configuration files currently used by mise.
15
+
- ### [[My Notes]] on `mise.toml`
16
+
- [[2025-05-11 Sun]]
17
+
- #### [[CLI command]] to find the currently active mise config #card
18
+
- [[mise/config/ls]] - `mise config ls` - run this to find the currently active mise config
19
+
- Here's a [[mise/Task]] definition for the mise config file which will use [[mise/config/ls]] to find the currently active mise config and open it in preferred [[IDE]] - (Cursor, here)
20
+
- ```toml
21
+
[tasks]
22
+
config = "cursor $(mise config ls | head -n1 | awk '{print $1}' | sed \"s|~|$HOME|\")"
23
+
```
15
24
-## Setting [[EnvVar]]s - [[mise/EnvVar]]s
16
25
- #Example - note, this can also be added to [[mise/Config/mise.toml]]
- tasks can be defined in [[mise/Config/mise.toml]]
97
+
collapsed:: true
88
98
- ```toml
89
99
[tasks]
90
100
build = "npm run build"
91
101
test = "npm run test"
92
102
```
93
103
- or in your project dir, apparently one can put `mise-tasks/build.sh` and `mise run build` will work just as well
94
-
- > [[mise/run]] sets up the "mise environment" before running task.
104
+
- collapsed:: true
105
+
> [[mise/run]] sets up the "mise environment" before running task.
95
106
- ir you activate mise, you don't need to worry about this, but if not, `mise run X` will set up env vars first.
96
107
- ### Task Usage Spec
108
+
collapsed:: true
97
109
- [[Observation/My]] mise has what appears to be its own language for describing a custom way to invoke a command. much as one can use a makefile, using mise, one can make `mise-tasks/gree` with a shell script like this, and it will set up tab complete and make it so certain CLI arguments are actually created as [[EnvVar]]s.
98
110
- ```sh
99
111
#!/usr/bin/env bash
@@ -132,6 +144,7 @@ tags:: [[Tutorial]]
132
144
The directory to greet from
133
145
```
134
146
- example run
147
+
collapsed:: true
135
148
- ```
136
149
mise run greet --user me -g "hey" "how are you"
137
150
[greet] $ ~/Documents/GitHub/logseq-encode-garden/mise-tasks/greet --user me -g hey how are you
@@ -143,24 +156,27 @@ tags:: [[Tutorial]]
143
156
hey, me! Your message is: how are you
144
157
```
145
158
- In my testing, the tab completion did not play well with [[Zsh/OhMyZsh]] autocompletions
- `mise use -g python@3.13` to set the default version of python in [[mise/Config/mise.toml]]. An advantage of this over [[mise/install]] is that it installs it and updates it in the config at the same time.
6
+
- `mise use -g uv@latest` - this will install [[uv]] as well and mise will utilize it going forwards for python.
- ## [How it works](https://mise.jdx.dev/dev-tools/#how-it-works)
5
+
id:: 682090e2-b6c2-47ae-a404-d806aab03b3d
6
+
- mise hooks into your shell (with `mise activate zsh`) and sets the `PATH` environment variable to point your shell to the correct runtime binaries. When you `cd` into a directory containing a `mise.toml`/`.tool-versions` file, mise will automatically set the appropriate tool versions in `PATH`.
0 commit comments