This thing rules - but I have a few questions :)

[IngwiePhoenix]

Hello!

By sheer luck, I came across this project and have deployed flow on basically all my servers as a nano replacement - it is, infinitively, nicer. Still getting used to the slightly different keybindings (mainly TTY limitations and sometimes overridden keybindings from apps like Windows Terminal) but so far, I am beyond mindblown. Seriously, this is one of the cases of "Where have you been all this time?!" xD

So, I have a few questions:

• Tasks: Can I define tasks in a file that Flow can read and then use? When I "Add Task...", I see no file where that command is stored.
• Still tasks: Can I run them in a terminal instead of having the output plop into a file view? Think npm run dev or something that just lives in the terminal.
• Aside from ~/.config/flow, is there anything else I should check into a dotfiles repository?
• Speaking of config - can I do project-local configuration?
• Is there an "input tester"? I feel like some keybindings don't work - and I would love to test which ones actually go through and which ones potentially get "eaten" by my client. Would make adjusting the keybinds a little nicer. :) Just a small utility that shows the keystrokes / key combinations as they come in or something. A test mode, effectively.
• I know 0.6.0 just introduced LSP powered autocompletion; anything I can configure about those?
• Can I use flow for commit messages? Random, I know, but it might come in handy! Would love to just setenv EDITOR=flow and move on ;)
• Is there a CLI flag I can use to jump to a line directly? Like, flow file.php -L 15?

Many small things, didn't seem like I should make a ticket for each individual one - that'd feel a little spammy.

Thanks so much for this really epic editor! I never worked with Zig, but I would love to add V language server as a way to learn a little Zig on the side.

Kind regards,
Ingwie

[neurocyte]

• Tasks: Can I define tasks in a file that Flow can read and then use? When I "Add Task...", I see no file where that command is stored.

Technically, yes. Although it's not super easy. Tasks are stored in the project state file at ~/.local/state/flow/projects which is CBOR encoded JSON. You can dump it to JSON with something like cbor-tool dump --json {projectfile} | jq and then change it and convert it back. It's easy to mess up the structure though, so I wouldn't really recommend it.

A much easier option is to add it with flow itself:

flow --project ~/src/myproject --exec 'add_task:do_something;quit'

Or add it and run it in flow in one step:

flow --project ~/src/myproject --exec 'run_task:do_something'

• Still tasks: Can I run them in a terminal instead of having the output plop into a file view? Think npm run dev or something that just lives in the terminal.

No, flow doesn't have a built-in terminal (yet). You can run a shell script that starts a new terminal though.

• Aside from ~/.config/flow, is there anything else I should check into a dotfiles repository?

~/.config/flow is meant to hold everything that you might want to version. ~/.local/state/flow contains everything else.

So, no.

• Speaking of config - can I do project-local configuration?

Coming soon (tm)!

If you have any ideas on how you think this should work you are welcome to contribute them in a feature request, or add to an existing one.

• Is there an "input tester"? I feel like some keybindings don't work - and I would love to test which ones actually go through and which ones potentially get "eaten" by my client. Would make adjusting the keybinds a little nicer. :) Just a small utility that shows the keystrokes / key combinations as they come in or something. A test mode, effectively.

Yes, flow --show-input or press alt+i or f12 when in flow.

• I know 0.6.0 just introduced LSP powered autocompletion; anything I can configure about those?

You can configure the LSP with the Edit file type configuration command. File type changes are stored in ~/.config/flow/file_type. Most file types come pre-configured for the most popular LSP for that language, so you don't usually have to configure anything, just make sure the LSP binary is in your PATH.

• Can I use flow for commit messages? Random, I know, but it might come in handy! Would love to just setenv EDITOR=flow and move on ;)

Yes, I use flow for all my commit messages and it has specific support for the gitcommit, git-rebase and diff file types.

• Is there a CLI flag I can use to jump to a line directly? Like, flow file.php -L 15?

Yes, there are two styles. Compiler output style:

flow path/file.ext:123

Or classic vim style:

flow path/file.ext +123

See flow --help for a bunch of other options..

Many small things, didn't seem like I should make a ticket for each individual one - that'd feel a little spammy.

A discussions post is always a good place to start. 👍

Thanks so much for this really epic editor!

Thanks! Glad it's useful to you.

I never worked with Zig, but I would love to add V language server as a way to learn a little Zig on the side.

You don't actually need any zig to add a new file type. The basics you can add your self by creating a new file ~/.config/flow/file_type. Just create one with Edit file type configuration and save it under a new name.

To add syntax highlighting though you will need to do a little more, but still very little or no zig. You need to add a tree-sitter grammar to the neurocyte/tree-sitter repository, add the new file type to neurocyte/flow-syntax and then update the LSP config and flow-syntax reference in flow itself.

Or just open a feature request and ask me to do it. :D

[IngwiePhoenix]

Wow, so effectively, it has most of the things I asked already. That's pretty impressive!

I will think of a good spec for the project-local one; but honestly, I wonder if you could just reuse .editorconfig for simplicity or just a flat ini-like .flowrc in the project folder.

[tasks]
build = npm run build
dev = npm run dev
[editor]
...
[filetype javascript]
# overrides

...or just a .flow/ to mimic the ~/.config/flow, like a "soft overlay". Anyway - will look into things and then formulate a proper FR.

Thanks for answering my little onslaught. I am genuenly impressed with Flow, so I'll keep an eye out for updates!

[neurocyte]

I definitely plan to support .editorconfig first, yes.

I think it's pretty likely that few (if any) flow specific settings exist. At least not ones that you would want to commit.

More likely is that flow needs a way to discover project specific tasks and settings that are already committed somehow.

[IngwiePhoenix]

Procfiles have been around forever and have a dead-simple syntax. I suppose those could be a viable "nothing new but works as expected" method?

Example:

build: vite
dev: npm run dev
backend: go build -o app cmd/app

[neurocyte]

I think Procfile is more for deployment and not really for development.