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

Make SpellBad less intrusive? #155

Open
volo1st opened this issue Apr 28, 2019 · 3 comments
Open

Make SpellBad less intrusive? #155

volo1st opened this issue Apr 28, 2019 · 3 comments

Comments

@volo1st
Copy link

volo1st commented Apr 28, 2019

Thanks for the amazing colour palette, really liked the colours and I am using it almost everywhere I can apart from Vim because:
The current way it highlights SpellBad is so intrusive that it makes you hard to concentrate on an ordinary code snippet as all the SpellBad matches are shown in Red with Underline. Just a few examples:
With spell turned on:
Screenshot from 2019-04-28 19-41-13
Screenshot from 2019-04-28 19-47-53

With nospell set:
Screenshot from 2019-04-28 19-48-52
Screenshot from 2019-04-28 19-48-34

Is it possible to make less intrusive like only set underline/undercurl for misspelt words instead of default to red text? Or at least provide an option to turn it on and off?

@HiPhish
Copy link

HiPhish commented Sep 14, 2019

I was wondering the same and this is the solution I found: add the following lines somewhere to your Vim configuration:

augroup nord-theme-overrides
	autocmd!
	autocmd ColorScheme nord highlight clear SpellBad
augroup END

For more information see :h hl-SpellBad (scroll down to :hi[ghlight] clear {group-name}) and :h hl-SpellBad. Of course instead of clearing the highlighting you could also apply your own highlighting instead.

@arcticicestudio
Copy link
Contributor

Hi @vincentzhezhang 👋, thanks for your contribution 👍
Sorry for the really late reply, must have missed this issue in the large amount of daily notifications.
I guess changing the style is indeed an improvement since this might also be mistaken as possible syntax error when using linter or compiler/evaluation plugins.

@HiPhish This is the recommended way to customize the theme for individual styles without breaking other themes 😄
➡️ The documentation also describes this technique in more detail so other users coming to this issue here might also like to take a look over there.

@svengreb
Copy link
Member

Thank you for your patience! 🙏🏼
It‘s been a while since I had free time to focus more on Nord, and my open source projects in general, and invest time in this issue due to work-life balance.

I recently published the first “Northern Post — The state and roadmap of Nord“ announcement which includes all details about the plans and future of the Nord project, including the goal of catching up with the backlog. This issue is part of the backlog and therefore I want to triage and process it to get one step closer to a “clean state“. Read the announcement about reaching the “clean“ contribution triage state in Nord‘s discussions for more details about the goal.

Therefore it has been added to the queue in the central and single-source-of-truth project board that is also described in more detail in the roadmap announcement.

@svengreb svengreb removed their assignment May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: queued
Development

No branches or pull requests

4 participants