I think LSP's (language service provider) could be used to build interesting UX in text editors.
As a boring example: "git add this hunk" could be offered as a code action by a git LSP.
Nowadays said command is usually an editor native command. With an LSP, the benefit would be that it'd "just work" across editors.
Though that might end up being a pandora's box for the protocol.
lynn / Lynn Zenn
npub1ze…wp3st
2023-04-25 17:18:50
Author Public Key
npub1zenn0vgcy2st7dz7gexxtuuan860ucryg26kdlnap2kndwrqmy0swwp3stPublished at
2023-04-25 17:18:50Event JSON
{
"id": "728afc5c5e0ce9726819d2b49e8ed37e42c4a2c21a6e66e9cd23bce52cee554b",
"pubkey": "166737b11822a0bf345e464c65f39d99f4fe606442b566fe7d0aad36b860d91f",
"created_at": 1682443130,
"kind": 1,
"tags": [],
"content": "I think LSP's (language service provider) could be used to build interesting UX in text editors.\n\nAs a boring example: \"git add this hunk\" could be offered as a code action by a git LSP.\n\nNowadays said command is usually an editor native command. With an LSP, the benefit would be that it'd \"just work\" across editors.\n\nThough that might end up being a pandora's box for the protocol.",
"sig": "658fb8601d8c5953fdf9bfc041466fc69cf331e3fe3c1c23f39b659d495769c7478bb4946c37958396661a46b62aec3bc8a197971bb5f2dfd7d2c542a8dd2b28"
}