02:27 <cc0> :P

02:27 <cc0> i appreciate that you'd be willing to add support for the spec to aerc even though youd not make use of it yourself. :)

02:42 <rockorager> Ah but I do use a specific aerc app-id!

09:50 <taupiqueur_shiny> hey

09:52 <taupiqueur_shiny> do you think it is out of the scope for foot to provide shell integration?

09:54 <taupiqueur_shiny> something like wezterm, which provides completion code from the cli

09:54 <taupiqueur_shiny> https://github.com/wez/wezterm/blob/main/wezterm/src/main.rs

09:54 <taupiqueur_shiny> shell completion*

09:55 <taupiqueur_shiny> it could be handy for shell integration (cd-ing, jumping between prompts, etc.) or shell completion

09:58 <taupiqueur_shiny> as it will slow down the shell init to use in `eval` I would rather use it as the source of truth and put the generated code in a ~/.local_bashrc or something (not sure about the convention)

13:06 <Riolku> like, you want foot to provide command line completion for commands?

13:09 <ifreund> taupiqueur_shiny: are you perhaps looking for this: https://codeberg.org/dnkl/foot/src/branch/master/completions

14:09 <taupiqueur_shiny> ifreund: yep :p

14:09 <taupiqueur_shiny> including shell integration

14:09 <taupiqueur_shiny> https://wezfurlong.org/wezterm/shell-integration.html

14:10 <taupiqueur_shiny> I realize the implementation is quite personal actually

14:10 <taupiqueur_shiny> so it might not be a good idea for `foot` to speak shell code to be evaluated for this integration

14:11 <taupiqueur_shiny> I have something like this in my bashrc for osc:

14:12 <taupiqueur_shiny> export PROMPT_COMMAND=_prompt_command

14:12 <taupiqueur_shiny> _prompt_command() {

14:13 <taupiqueur_shiny> printf '\e]7;file://%s%s\e\\\e]133;A\e\\' "$HOSTNAME" "$PWD"

14:13 <taupiqueur_shiny> }

14:13 <taupiqueur_shiny> it's not bulletproof sadly due to url escaping

14:14 <taupiqueur_shiny> might be possible to encode pwd with `curl` or `jq @uri`