Hope this is still active repo.

Somehow if creating object from System.Data namespace, "Data" word gets highlighted:

$dt = New-Object System.Data.DataTable

Would be great if the cmdlet parameters are highlighted as well :).

Error detected while processing /Users/cxu/.vim/ftdetect/ps1.vim:
line 7:
E492: Not an editor command: ^M

I've got an Ubuntu 16.04 Xenial Xerus VM with Vim 8.0 installed. I'm using Vundle to install the plug-in, but it's not automatically detecting the filetype for a .ps1 file. Any ideas what's wrong?

Seems similar to #16.

Cheers,
Trevor Sullivan
Docker Captain
Microsoft MVP: Cloud & Data Center Management
https://trevorsullivan.net
https://twitter.com/pcgeek86

I'm using Windows 10 and gvim 7.4.

I put vim-ps1 in ~\.vim\plugin but starting gvim doesn't seem to load the ps1 script correctly.

I also tried manually: :source ~\.vim\plugin\vim-ps1\ftplugin\ps1.vim. Still don't see Powershell among the languages.

Please use better versioning. Many tools consider 2.81 as the latest release
because they think 2.81 is higher than 2.9.
Maybe use semantic versioning -> 2.81 -> 2.8.1

I recently installed this plugin and everytime I open PS1 files, a terminal buffer is opening as well. This is happening both on my windows10 and Mac. It's not very obvious to me which option i should put. Any thoughts?

Currently, the syntax file recognizes all words-with-dashes as function invocations (syn match ps1FunctionInvocation /\w\+\(-\w\+\)\+/), which can yield many false positives, and is also incosistent with the line just above (syn match ps1FunctionDeclaration /\w\+\(-\w\+\)*/ contained -- no dash is needed for recognition).

A possibility to decrease the amount of false positives would be to require (perhaps togglable) additionally that the word starts with an uppercase letter (\u\w*), which is consistent with MS's style guide (https://docs.microsoft.com/en-us/dotnet/standard/design-guidelines/capitalization-conventions).

Currently ps1.vim overrides the 'formatoptions' as follows:

Unfortunately that means that set formatoptions+=j in my .vimrc is not applied for PowerShell files. As that format option seems to work with PowerShell syntax (at least for comments starting with '#', which is what I tried), I wanted to know whether that omission is intentional or accidental?

Hi there. Thanks for this handy plugin. I'm seeing behavior where a script named foo (with no ps1 extension) and the following content:

#!/usr/bin/env pwsh
Write-Output "foo"

Won't be highlighted properly until I explicitly run :set syn=ps1. For other languages the shebang line works to infer the appropriate syntax highlighter, so it'd be nice if this was the case for PowerShell scripts as well.

According to the Unicode standard, the BOM for UTF-8 files is not recommended.

https://stackoverflow.com/questions/2223882/whats-different-between-utf-8-and-utf-8-without-bom/2223926#2223926

The ps1 syntax sets cindent, which causes a general vim issue described here: http://vim.wikia.com/wiki/Restoring_indent_after_typing_hash. The problem goes away if I use this setting:

:set nocindent

The indentation of the powershell script is not correct when in braces blocks. For instance, the following lines are correct:

Write-Host "line 1"
Write-Host "line 2"

While, if they are inside a pair of braces, when use = to indent the code block, the outcome becomes:

If ($value -gt 0)
{
    Write-Host "line 1"
        Write-Host "line 2"
}

Hello. I added your plugin to the vim package index, so that I could install it automagically via my plugin manager. Please review and provide your input on the pull request, over on BitBucket.

Thanks!

This does not work out of the box on Linux because of the unexpected ^M.

You have to run the files with errors through dos2unix before it works correctly.

Hello,
Can someone please help me get this working?
Windows 10 ent, fully updated
I installed gvim81.exe
I have a _gvimrc file in c:\users\me
I downloaded this plugin vim-ps1-master.zip
I created a directory in c:\users\me.vim
I unzipped vim-ps1-master.zip in .vim
I also created c:\users\vimfile and unzipped vim-ps1-master.zip into it

When I edit a .ps1 file, I don't see any syntax highlighting. the setting in _gvimrc do work, so I am in the right directory, I think.

What else do I need to do?
Thanks

After vim/vim#8051 is merged, in this repo:

• Normalize headers
• Consider writing script to replace HiLink function, though it doesn't take much effort to fix that in vim/vim when needed.

The extension of Ruby language is ".rb" and filetype is "ruby".
The extension of Python language is ".py" and filetype is "python".
The extension of Perl language is ".pl" and filetype is "perl".

Why the name of filetype is "ps1", not "powershell"?