NeoVim getting slower when choose colorscheme
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 44.7k
- Forks
- 3.6k
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Description
-
I am on the latest Hyper.app version
-
I have searched the issues of this repo and believe that this is not a duplicate
-
OS version and name: 22.04.1 LTS (Jammy Jellyfish) Ubuntu Linux
-
Hyper.app version: 3.3.0
-
Link of a Gist with the contents of your .hyper.js: https://gist.github.com/pandasoli/837841a09c0f44ffb75bb906bc0380d0.js
-
Relevant information from devtools (CMD+ALT+I on macOS, CTRL+SHIFT+I elsewhere): CTRL+SHIFT+I
-
The issue is reproducible in vanilla Hyper.app: Is Vanilla
Issue
I was moving on to NeoVim and when I chose any colorscheme (except the default, and including the other default color schemes), it makes NeoVim very slow and difficult to code.
But it's not a NeoVim issue, 'cause when I tried to run it in the standard Linux terminal NeoVim ran normally.
I really don't know what could be the problem, but hope you fix it.
Here is a video:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the slowdown in Hyper 3.3.0 on Ubuntu 22.04 with NeoVim and a non-default colorscheme, then compare it with the standard Linux terminal. Use the linked .hyper.js gist and video as supporting evidence; done means identifying the Hyper-specific cause and confirming that NeoVim remains responsive with those colorschemes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100