sadly no; position of hint is determined by the LSP server.

you could use this plugin (now archived) which was the way many people used hints pre-0.10:

https://github.com/lvimuser/lsp-inlayhints.nvim

might switch from alacritty to kitty almost just for this (although I’ve been meaning to for a while). the “immediately get scroll back into an nvim buffer to edit as a command” is pretty sweet

another way to start is to only do small configurations at first. as you code maybe you realize you want a tool that shows git diffs, install a plug-in that does that. over time, you gradually build your config. maybe you want to start using leader for custom key maps. a couple days later maybe you think you want a file picker so you add telescope. this 100% will take longer, but you’ll intimately understand why every line in your config is there.