Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/TheLeoP/powershell.nvim below:

TheLeoP/powershell.nvim: First class powershell editor integration into Neovim

This extension provides rich PowerShell language support for Neovim. Now you can write and debug PowerShell scripts using the excellent IDE-like interface that Neovim provides.

• Powershell LSP support (via Powershell Editor Services)
• Powershell Extension Terminal support
• Debugging support (requires nvim-dap)
• $psEditor API support

• Powershell Editor Services (can be installed manually or using something like mason.nvim)
• Neovim >= 0.11
• (Optional) nvim-dap (needed for debugging)

use {
    "TheLeoP/powershell.nvim"
}

{
    "TheLeoP/powershell.nvim",
    ---@type powershell.user_config
    opts = {
      bundle_path = 'path/to/your/bundle_path/'
    }
}

Plug 'TheLeoP/powershell.nvim'

The only required field for the plugin to work is bundle_path, this has to be the path of where Powershell Editor Services is installed.

For example, if you are using mason with default settings, you would have to do something like the following:

require('powershell').setup({
  bundle_path = vim.fn.stdpath "data" .. "/mason/packages/powershell-editor-services",
})

-- This is the default configuration
require('powershell').setup({
  capabilities = vim.lsp.protocol.make_client_capabilities(),
  bundle_path = "",
  init_options = vim.empty_dict(),
  settings = vim.empty_dict(),
  shell = "pwsh",
  handlers = base_handlers, -- see lua/powershell/handlers.lua
  root_dir = function(buf)
    return fs.dirname(fs.find({ ".git" }, { upward = true, path = fs.dirname(api.nvim_buf_get_name(buf)) })[1])
  end,
})

require('powershell').toggle_term()

To create a keymap only for powershell files, put the following in your config.

-- this should go in ~/.config/nvim/ftplugin/ps1.lua
vim.keymap.set("n", "<leader>P", function() require("powershell").toggle_term() end)

You could also use a filetype autocmd to create the keymap.

Can be used both in normal (evaluates current line) and visual mode (evaluates visual selection).

require('powershell').eval()

To create a keymap only for powershell files, put the following in your config.

-- this should go in ~/.config/nvim/ftplugin/ps1.lua
vim.keymap.set({ "n", "x" }, "<leader>E", function() require("powershell").eval() end)

You could also use a filetype autocmd to create the keymap.

By default, the plugin includes the following nvim-dap configurations:

dap.configurations.ps1 = {
  {
    name = "PowerShell: Launch Current File",
    type = "ps1",
    request = "launch",
    script = "${file}",
  },
  {
    name = "PowerShell: Launch Script",
    type = "ps1",
    request = "launch",
    script = function()
      return coroutine.create(function(co)
        vim.ui.input({
          prompt = 'Enter path or command to execute, for example: "${workspaceFolder}/src/foo.ps1" or "Invoke-Pester"',
          completion = "file",
        }, function(selected) coroutine.resume(co, selected) end)
      end)
    end,
  },
  {
    name = "PowerShell: Attach to PowerShell Host Process",
    type = "ps1",
    request = "attach",
    processId = "${command:pickProcess}",
  },
}

To use them, simply call require('dap').continue() inside of a ps1 file.

NOTE: currently, debugging does not support launching an integrated terminal because of PowerShell/PowerShellEditorServices#2164

• Tests

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4