In short, yes it has to be in a terminal. I appreciate it, but the problem
isn't my command, it's that the textbox isn't basic enough to connect.
On Thu, Dec 2, 2021 at 5:06 AM David Nebauer wrote:
> Does nvim have to run in a terminal? On my system the gui version of nvim
> is nvim-qt and I
That worked! Well, insofar as it worked on a simple text box. Thank you!
I actually had to hunt a bit for a simple text box, as rich text boxes are
becoming more ubiquitous.
Thank you Florian. I'll keep my eye on this bug. I appreciate all of your
hard work.
On Wed, Dec 1, 2021 at 3:29 AM
Hey,
On Mon, Nov 29, 2021 at 03:31:56PM -0700, Bearcat M. Şándor wrote:
> Thank you. Hunting around on-line, the command *c.editor.command =
> ["alacritty", "-e", "nvim", "{}", "+call cursor({line}, {column})"] *seems
> to work for people.
That looks fine.
> In my case the temp file is
Trying ['/usr/bin/alacritty', '-e', '/usr/bin/nvim', '{}']
and ["alacritty", "-e", "nvim", "{file}", "+call cursor({line}, {column})"]
both of them fire off neovim in a terminal with no errors. However, neovim
is always empty regardless of the textbox's contents, and the textbox is
never altered
Thank you. Hunting around on-line, the command *c.editor.command =
["alacritty", "-e", "nvim", "{}", "+call cursor({line}, {column})"] *seems
to work for people. In my case the temp file is created, has my content in
it when I save it, but is then deleted when nvim closes. The text box
never
Try changing it to ['usr/bin/alacritty', '-e', '/usr/bin/nvim/', '{}']
On Mon, Nov 29, 2021, at 17:44, Bearcat M. Şándor wrote:
> I have the common problem of opening an editor for a text box and
> having that fail.
>
> */usr/bin/alacritty '-e /usr/bin/nvim' /tmp/qutebrowser-editor-pc7oapv1
>
I have the common problem of opening an editor for a text box and having
that fail.
*/usr/bin/alacritty '-e /usr/bin/nvim' /tmp/qutebrowser-editor-pc7oapv1 *is
the command that it's running but of course the single quotes around the -e
switch shouldn't be there, and alacritty errors out.
