Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calling from visual mode gives "E481: No range allowed" #40

Open
benjstephenson opened this issue Aug 16, 2023 · 11 comments
Open

Calling from visual mode gives "E481: No range allowed" #40

benjstephenson opened this issue Aug 16, 2023 · 11 comments

Comments

@benjstephenson
Copy link

On neovim nightly on Mac M1 I've configured Silicon using Lazy (in Fennel) with

(lazy :krivahtoo/silicon.nvim
      {:build "./install.sh build"
       :opts {:font "Fira Code=16"
              :theme "Monokai Extended"
              :window_controls false
              :tab_width 2
              :pad_vert 0
              :pad_horiz 0}})

There are no errors in the build process but if I

  • call :Silicon I get an image successfully created but only containing the first line of the file.
  • call :%Silicon I get E481
  • select some text in visual mode and call :'<,'>Silicon I also get E481

I can't see any other error messages so I'm not too sure how to debug the issue further.

@krivahtoo
Copy link
Owner

What is the output of :command Silicon?

@benjstephenson
Copy link
Author

Not sure how to inspect the definition but here's the output of running :command Silicon

    Name              Args Address Complete    Definition
!   Silicon           0                        <Lua 156>

@amv-dev
Copy link

amv-dev commented Oct 2, 2023

This bug happens for me explicitly in neovim 0.10. Works fine in neovim 0.9

@Demianeen
Copy link

Same here. Also in normal mode, it takes only the first line. Feels like the condition to check the mode is reversed

CleanShot.2024-02-13.at.12.56.14.mp4

@jergason
Copy link

jergason commented Apr 8, 2024

I'm also encountering this error in Neovim nightly (541c2d3816cdef9aba7f55f74908fa07d0cfa3ec) on macOS.

@cwebster2
Copy link

I'm also encountering this issue

Linux
Rust 1.74.1
Neovim v0.10.0-dev-2859+g00e665188

@krivahtoo
Copy link
Owner

silicon.nvim currently does not support neovim-nightly.

@Demianeen
Copy link

Same issue on the new stable

@krivahtoo
Copy link
Owner

@Demianeen
Thanks for reporting. I didn't realize there was a new version on Neovim.

I have released a new update the should work on v0.10

@Demianeen
Copy link

Demianeen commented May 26, 2024

It started to work after the update!

It still crushes neovim after it screenshots though. The same behaviour on stable and nightly versions. Might you know where the issue is?

CleanShot.2024-05-26.at.10.08.09.mp4

Versions info:

Stable:

NVIM v0.10.0
Build type: Release
LuaJIT 2.1.1713484068
Run "nvim -V1 -v" for more info

Nightly:

NVIM v0.11.0-dev-49+g10601ac5f
Build type: RelWithDebInfo
LuaJIT 2.1.1713484068
Run "nvim -V1 -v" for more info

P.S. I already added plans to learn Rust in the next couple of months to help here 😄

@krivahtoo
Copy link
Owner

It still crushes neovim after it screenshots though. The same behaviour on stable and nightly versions. Might you know where the issue is?

I am unable to reproduce the issue in both v0.10 and nightly. I am on Linux so maybe the issue is with Mac builds.

P.S. I already added plans to learn Rust in the next couple of months to help here 😄

That would be awesome 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants