-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pwsh not detecting eNum
#123
Comments
Same issue here. I think it's because Doskey apart from being incompatible with PSReadLine see: PowerShell/PSReadLine#353 Doskey doesn't work with pwsh, it also will not be supported by the devs as linked before so it should be replaced with PSReadLine completely. this is the file that should be changed in any case to make it work with PSReadline instead: Line 126 in a813038
|
One solution, instead of using doskey to create the aliases, is to generate a PowerShell module containing functions named I'm testing out a patch that does that currently. The difference is we:
This yields the following aliases file for me when invoked on the Function e0 { nvim.exe $args "src"}
Function e1 { nvim.exe $args "src/cli.rs"}
Function e2 { nvim.exe $args "src/diagram_formatting.rs"}
Function e3 { nvim.exe $args "src/file_tree.rs"}
Function e4 { nvim.exe $args "src/json_formatting.rs"}
Function e5 { nvim.exe $args "src/main.rs"}
Function e6 { nvim.exe $args "src/output.rs"}
Function e7 { nvim.exe $args "src/path_finders.rs"}
Function e8 { nvim.exe $args "src/tre.rs"}
Export-ModuleMember -Function * In the new
New # Remove the tre.exe aliases module created by the previous invocation
# if it exists
if (Get-Module tre_aliases_$env:USERNAME)
{
Remove-Module -Force tre_aliases_$env:USERNAME
}
# Call tre.exe with the args passed to this script and the editor flag
tre.exe $args -e
# Import the new aliases module created by tre.exe
Import-Module $Env:TEMP\tre_aliases_$env:USERNAME.psm1 I can then type |
Did you run into any issues with your patch @jman4747 |
I used the script from the readme:
Shell: PowerShell 7.3.0-preview.6
tre: tre-command 0.4.0
Same thing occurs on Windows' system PowerShell (5.1)
The text was updated successfully, but these errors were encountered: