Git Product home page Git Product logo

Comments (5)

BatmanAoD avatar BatmanAoD commented on June 2, 2024 1

@fredizzimo I'm not sure how that addresses my use case? What I want is to be able to download my config onto any machine, any OS, and have a reasonable choice of fonts auto-selected, without a warning message about invalid fonts, and without needing to manually tweak the downloaded files. Then, when I do get around to installing my preferred font, I'll automatically get that font instead of the fallback, again without modifying a config file. This is the behavior of gvim and of all neovide versions before 0.12.

I appreciate the concept of local files for machine-specific config, but that's essentially the opposite of what I want for this feature.

from neovide.

fredizzimo avatar fredizzimo commented on June 2, 2024

I don't think so, in the past we have got way too many issues where people have made typos in their font names and those are completely pointless, since the users could have figured it out themselves.

Additionally, I can't think of a single valid reason why you have configured a fallback font, and don't want to use it. For machine specific configuration, the config file is the preferred way.

from neovide.

yourboirusty avatar yourboirusty commented on June 2, 2024

Noted, I'll switch to using the config file or work around it in Lua.

from neovide.

BatmanAoD avatar BatmanAoD commented on June 2, 2024

@fredizzimo I added a comment here to this effect, but I do actually rely on silent fallback, and it seems like there's no way to get my preferred behavior without a more complex configuration. Would you consider a config option to let users opt-in to the silent-fallback behavior? This would make it easy to debug font selection by opting back out, but also enable the old behavior for people who use it.

from neovide.

fredizzimo avatar fredizzimo commented on June 2, 2024

Your use case is one of the reasons why added the font settings to the confg.toml file. https://neovide.dev/config-file.html#runtime-settings

That file is machine specific, so you can have different fonts and font sizes on all your client machines, while using the same main neovim configuration. It's also always loaded from the same host as Neovide, so it's unaffected by any remote settings when you connect to remote Neovim instances.

from neovide.

Related Issues (20)

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.