nvim-tundra
vale
Our great sponsors
nvim-tundra | vale | |
---|---|---|
9 | 46 | |
246 | 4,178 | |
- | 3.1% | |
4.9 | 9.3 | |
2 months ago | 6 days ago | |
Lua | Go | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nvim-tundra
-
Changing color of my Telescope background, making it transparent as my terminal emulator
Might be worth checking out these highlight groups and seeing if any of those make a difference to your telescope window :)
-
nvim-tundra v0.2.0 - A punchy, dark theme for Neovim!
Hi r/Neovim! Today I released v0.2.0 for the [Tundra](https://github.com/sam4llis/nvim-tundra) theme so thought I’d post it here in case anybody is interested. ## Highlights: - Added `dim_inactive_windows` table in the Tundra `setup` function - when enabled, non-current windows will inherit the background colour `dim_inactive_windows.color`. - Added `:Tundra` command line sugar. This allows users to change configuration settings in real-time instead of having to reload their configuration. - `:Tundra toggle_transparency` - toggles `transparent_background` flag. - `:Tundra toggle_dim` - toggles `dim_inactive_windows.enabled` flag. - [nvim-treesitter](https://github.com/nvim-treesitter/nvim-treesitter) integration now requires Neovim 0.8. Obsolete `TS*` highlight groups were removed from nvim-treesitter and Tundra will no longer support older highlight groups. To use the obsolete highlight groups, downgrade to Tundra v0.1.0. See [this](https://github.com/nvim-treesitter/nvim-treesitter/pull/3656) for more information. - Support for common terminals and software including Alacritty, fzf, iTerm-2, WezTerm, and Windows Terminal. - Improvement of Tundra documentation. - Rewritten using [Vale](https://vale.sh) to keep a consistent style guide. You can find more information about the Tundra theme over at its [GitHub repository](https://github.com/sam4llis/nvim-tundra). Thanks for reading!
-
What color scheme do you use with transparent background enabled?
I don’t use transparent background, but you might like my theme Tundra with transparent background!
-
nvim-tundra - A punchy, dark colorscheme for Neovim!
I've included some niceties from other popular Neovim themes (mainly Catppuccin and NightFox) such as transparent background toggle, syntax overrides, and optional plugin highlight groups to try and make the user experience as pleasant as possible. You can download or read more about the theme over at its Github repository. Thanks for reading!
- Tundra: A punchy, customisable dark theme for Neovim
vale
- Software Technical Writing: A Guidebook [pdf]
- Grammarly editor writing service are malfunctioning
- Vale.sh – A Linter for Prose
- Ask HN: Best tool to proof-read technical documentation?
- Val, a high-level systems programming language
-
Common Bugs in Writing
Vale is an OSS tool that you can use as a "prose linter" with many of these rules. You can also write your own rules. Together with a spellchecker its a good replacement for proprietary tools like grammarly.
- https://github.com/errata-ai/vale
-
Just Simply – Stop saying how simple things are in our docs
> Write in US English with US grammar. (Tested in British.yml.)
heh, that was funny but it turns out the file is a list of British words checked using Vale, which I just learned existed: https://github.com/errata-ai/vale#readme (MIT)
Also, another TIL is that the "e" version of gray is British https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/.vale... I had previously erroneously assumed they were just one of those quirks of English (which, I guess is still true but it is less random than I thought)
-
Tools that enforce/promote corporate standards?
Off the top of my head, Vale and Acrolinx.
-
Over 60% of Writers Already Use AI in Their Writing Workflow
I have recently thought of feeding the suggestions from Vale (https://vale.sh/) into an LLM along with your writing. Currently I just simply ask an LLM to take what I wrote and put it into a more "active voice". I then manually edit my writing to make it more "active" if I choose -- I do not just publish LLM generated content unaltered.
Note: I did not ask an LLM for this comment.
-
What terminal apps are you using?
vale to spell check and enforce writing style on my articles
What are some alternatives?
catppuccin - 😸 Soothing pastel theme for the high-spirited!
proselint - A linter for prose.
noctis.nvim - A neovim port of the high contrast noctis theme for VSCode.
lsp-grammarly - lsp-mode ❤️ grammarly
vscode-codicons - The icon font for Visual Studio Code
nvim-lspconfig - Quickstart configs for Nvim LSP
iTerm2-Color-Schemes - Over 250 terminal color schemes/themes for iTerm/iTerm2. Includes ports to Terminal, Konsole, PuTTY, Xresources, XRDB, Remmina, Termite, XFCE, Tilda, FreeBSD VT, Terminator, Kitty, MobaXterm, LXTerminal, Microsoft's Windows Terminal, Visual Studio, Alacritty
write-good - Naive linter for English prose
.dotfiles - My configuration files.
markdownlint - Repository for the markdownlint-mdl-action Github Action
kanagawa.nvim - NeoVim dark colorscheme inspired by the colors of the famous painting by Katsushika Hokusai.
remark-lint - plugins to check (lint) markdown code style