winutil

Sun, 04 May 2025 15:26:19 +0800

ChrisTitusTech/winutil

Chris Titus Tech’s Windows Utility

This utility is a compilation of Windows tasks I perform on each Windows system I use. It is meant to streamline installs, debloat with tweaks, troubleshoot with config, and fix Windows updates. I am extremely picky about any contributions to keep this project clean and efficient.

💡 Usage

Winutil must be run in Admin mode because it performs system-wide tweaks. To achieve this, run PowerShell as an administrator. Here are a few ways to do it:

Start menu Method:
- Right-click on the start menu.
- Choose “Windows PowerShell (Admin)” (for Windows 10) or “Terminal (Admin)” (for Windows 11).
Search and Launch Method:
- Press the Windows key.
- Type “PowerShell” or “Terminal” (for Windows 11).
- Press Ctrl + Shift + Enter or Right-click and choose “Run as administrator” to launch it with administrator privileges.

Launch Command

Stable Branch (Recommended)

`1`	`irm "https://christitus.com/win" \| iex`

Dev Branch

`1`	`irm "https://christitus.com/windev" \| iex`

If you have Issues, refer to Known Issues

🎓 Documentation

WinUtil Official Documentation

YouTube Tutorial

ChrisTitus.com Article

💖 Support

To morally and mentally support the project, make sure to leave a ⭐️!
EXE Wrapper for $10 @ https://www.cttstore.com/windows-toolbox

💖 Sponsors

These are the sponsors that help keep this project alive with monthly contributions.

🏅 Thanks to all Contributors

Thanks a lot for spending your time helping Winutil grow. Thanks a lot! Keep rocking 🍻.

📊 GitHub Stats

nvim-lspconfig

Thu, 17 Apr 2025 15:30:46 +0800

neovim/nvim-lspconfig

nvim-lspconfig

nvim-lspconfig is a “data only” repo, providing basic, default Nvim LSP client configurations for various LSP servers.

View all configs or :help lspconfig-all from Nvim.

Important ⚠️

These configs are best-effort and supported by the community (you). See contributions.
If you found a bug in Nvim LSP (:help lsp), report it to Neovim core.
- Do not report it here. Only configuration data lives here.
This repo only provides configurations. Its programmatic API is deprecated and must not be used externally.
- The “framework” parts (not the configs) of nvim-lspconfig will be upstreamed to Nvim core.

Install

Requires Nvim 0.10 above. Update Nvim and nvim-lspconfig before reporting an issue.

Install nvim-lspconfig using Vim’s “packages” feature:

`1`	`git clone https://github.com/neovim/nvim-lspconfig ~/.config/nvim/pack/nvim/start/nvim-lspconfig`

Or use a 3rd-party plugin manager (consult the documentation for your plugin manager).

Quickstart

Install a language server, e.g. pyright
1

npm i -g pyright
Add the language server setup to your init.lua.
- Nvim 0.11+ (see vim.lsp.config)
  1
  
  vim.lsp.enable('pyright')
- Nvim 0.10 (legacy, not supported)
  1
  
  require'lspconfig'.pyright.setup{}
Ensure your project/workspace contains a root marker as specified in :help lspconfig-all.
Open a code file in Nvim. LSP will attach and provide diagnostics.
1

nvim main.py
Run :checkhealth lsp to see the status or to troubleshoot.

Read :help lspconfig for details. Read :help lspconfig-all for the full list of server-specific details. For servers not on your $PATH (e.g., jdtls, elixirls), you must manually set the cmd parameter, see vim.lsp.config.

Configuration

Nvim sets some default options and mappings when a buffer attaches to LSP (see :help lsp-config). In particular:

'tagfunc'
- Enables “go to definition” capabilities using <C-]> and other tag commands.
'omnifunc'
- Enables (manual) omni mode completion with <C-X><C-O> in Insert mode. For autocompletion, an autocompletion plugin is required.
'formatexpr'
- Enables LSP formatting with gq.
K maps to vim.lsp.buf.hover() in Normal mode.
[d and ]d map to vim.diagnostic.goto_prev() and vim.diagnostic.goto_next(), respectively.
<C-W>d maps to vim.diagnostic.open_float().

Further customization can be achieved using the LspAttach autocommand event. The LspDetach autocommand event can be used to “cleanup” mappings if a buffer becomes detached from an LSP server. See :h LspAttach and :h LspDetach for details and examples. See :h lsp-buf for details on other LSP functions.

Extra settings can be specified for each LSP server:

Nvim 0.11+ (see vim.lsp.config)

vim.lsp.config('rust_analyzer', {
  -- Server-specific settings. See `:help lsp-quickstart`
  settings = {
    ['rust-analyzer'] = {},
  },
})

Nvim 0.10 (legacy, not supported)

local lspconfig = require('lspconfig')
lspconfig.rust_analyzer.setup {
  -- Server-specific settings. See `:help lspconfig-setup`
  settings = {
    ['rust-analyzer'] = {},
  },
}

vim.lsp.config

nvim-lspconfig includes configurations compatible with vim.lsp under lsp/, so servers can be enabled (auto-activated when a filetype is opened) with:

`1`	`vim.lsp.enable('pyright')`

and configured with:

1
2
3

vim.lsp.config('pyright', {
  cmd = { … },
})

which extends the configuration under lsp/. For further information see :help lsp-config.

[!WARNING]
Some servers are currently missing.

Troubleshooting

The most common reasons a language server does not start or attach are:

Language server is not installed. nvim-lspconfig does not install language servers for you. You should be able to run the cmd defined in each server’s Lua module from the command line and see that the language server starts. If the cmd is an executable name instead of an absolute path to the executable, ensure it is on your path.
Missing filetype plugins. Certain languages are not detecting by Vim/Nvim because they have not yet been added to the filetype detection system. Ensure :set ft? shows the filetype and not an empty value.
Not triggering root detection. Some language servers will only start if it is opened in a directory, or child directory, containing a file which signals the root of the project. Most of the time, this is a .git folder, but each server defines the root config in the lua file. See doc/configs.md or the source for the list of root directories.
You must pass capabilities for each setup {} if you want these to take effect.
Do not call setup {} twice for the same server. The second call to setup {} will overwrite the first.

Bug reports

If you found a bug with LSP functionality, report it to Neovim core.

Before reporting a bug, check your logs and the output of :LspInfo. Add the following to your init.vim to enable logging:

`1`	`vim.lsp.set_log_level("debug")`

Attempt to run the language server, and open the log with:

:LspLog

Most of the time, the reason for failure is present in the logs.

Commands

:LspInfo (alias to :checkhealth vim.lsp) shows the status of active and configured language servers.
:LspStart <config_name> Start the requested server name. Will only successfully start if the command detects a root directory matching the current config. Pass autostart = false to your .setup{} call for a language server if you would like to launch clients solely with this command. Defaults to all servers matching current buffer filetype.
:LspStop [<client_id_or_name> ...] Stops the given server(s). Defaults to stopping all servers active on the current buffer. To force stop add ++force
:LspRestart [<client_id_or_name> ...] Restarts the given client(s), and attempts to reattach to all previously attached buffers.

Contributions

If a language server is missing from configs.md, contributing a new configuration for it helps others, especially if the server requires special setup. Follow these steps:

Read CONTRIBUTING.md.
Create a new file at lsp/SERVER_NAME.lua.
- Copy an existing config to get started. Most configs are simple. For an extensive example see texlab.lua.
Ask questions on GitHub Discussions or in the Neovim Matrix room.

Release process

To publish a release:

Create and push a new tag.
After pushing the tag, a GitHub action will automatically package the plugin and publish the release to LuaRocks.

License

nvim-lspconfig is licensed under the terms of the Apache 2.0 license.

See LICENSE.md

Troubleshooting on Producthunt daily

winutil

ChrisTitusTech/winutil

Chris Titus Tech’s Windows Utility

💡 Usage

Launch Command

Stable Branch (Recommended)

Dev Branch

🎓 Documentation

WinUtil Official Documentation

YouTube Tutorial

ChrisTitus.com Article

💖 Support

💖 Sponsors

🏅 Thanks to all Contributors

📊 GitHub Stats

nvim-lspconfig

neovim/nvim-lspconfig

nvim-lspconfig

Important ⚠️

Install

Quickstart

Configuration

vim.lsp.config

Troubleshooting

Bug reports

Commands

Contributions

Release process

License