Skip to content
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

psedit cannot open an empty file in a remote PSSession #842

Closed
daviwil opened this issue Jun 7, 2017 · 3 comments
Closed

psedit cannot open an empty file in a remote PSSession #842

daviwil opened this issue Jun 7, 2017 · 3 comments
Labels
Issue-Bug A bug to squash.

Comments

@daviwil
Copy link
Contributor

daviwil commented Jun 7, 2017

It seems that psedit is having an issue opening an empty file in a remote PSSession, need to investigate.

/cc @sstodd7532

@daviwil daviwil added this to the June 2017 milestone Jun 7, 2017
@sstodd7532
Copy link

Here are a copy of the logs that I had from the test that I just ran
1496861214-ed36508f-ecf3-45d3-a463-97d6a9111dbb1496857080988.zip

@sstodd7532
Copy link

It also does not appear to be saving the edits that I make to a file once I have content in them.

@daviwil daviwil modified the milestones: June 2017, 1.4.1 Jun 22, 2017
@daviwil daviwil modified the milestones: 1.4.2, 1.5.1 Aug 24, 2017
@muzzar78
Copy link

muzzar78 commented Sep 18, 2017

When I remote into a server within the integrated terminal, run psedit the file appears in VSCode. However, when I make an edit and save the file the changes aren't getting saved back to the remote server. I have attached the verbose log output.
vscode-powershell-psedit.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug A bug to squash.
Projects
None yet
Development

No branches or pull requests

3 participants