Code Monkey home page Code Monkey logo

zengarden's Introduction

About me

I am a professional software developer, journeyman in everything agile, and believe in the minimalism of all things. Since recently, I am also an ergonomics enthusiast.

I am currently working as engineering team lead for an IT security company. Technically, I am most proficient in C, C++ and Python, though I like to dabble with technologies, just to get a feel for them (Rust, Perl, Lisp, and frontend frameworks/libraries such as Vue.js or d3.js).

Ask me about Fantasy books (actually, don't, unless you have too much time)

Fun fact: The fear of the number 13 is called "triskaidekaphobia". The fear of bugs is called "software development".

zengarden's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar

zengarden's Issues

Some colours are different in neovim 0.10.0

I just upgraded to neovim 0.10.0 and noticed that some colours are not set correctly anymore.

The upper panel in the screenshot below uses neovim 0.10.0, the lower one 0.9.5. Settings, plugins, etc. are identical.

image

According to the release notes of 0.10 there were some changes affecting the default colours. I guess this causes the difference.

Default color scheme has been updated to be "Nvim branded" and accessible. Use :colorscheme vim to revert to the old legacy color scheme.

  • These Nvim specific highlight groups are now defined in a meaningfully different way and might need an update:
    • hl-FloatBorder is linked to hl-NormalFloat instead of hl-WinSeparator.
    • hl-NormalFloat is not linked to hl-Pmenu.
    • hl-WinBar has different background.
    • hl-WinBarNC is similar to hl-WinBar but not bold.
    • hl-WinSeparator is linked to hl-Normal instead of hl-VertSplit.
  • This also might result into some color schemes looking differently due to them relying on implicit assumptions about how highlight groups are defined by default. To account for this, define all attributes of highlight groups explicitly. Alternatively, use :colorscheme vim or :source $VIMRUNTIME/colors/vim.lua to restore previous definitions.

I can also try to fix it, but any pointers what/where to change would be helpful, in case you already have some understanding of the issue.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.