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

If try open file in FAR Manager via Emenu (windows explorer file context menu: Open with Code) I get error message to in console #41218

Closed
michalzobec opened this issue Jan 6, 2018 · 10 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug help wanted Issues identified as good community contribution opportunities windows VS Code on Windows issues workbench-os-integration Native OS integration issues
Milestone

Comments

@michalzobec
Copy link

  • VSCode Version: Code 1.19.1 (0759f77, 2017-12-19T09:46:23.884Z)
  • OS Version: Windows_NT x64 10.0.14393
  • Extensions:
Extension Author (truncated) Version
PowerShell ms- 1.5.1

Steps to Reproduce:

  1. in FAR Manager select PS1 multiple files (more than one file)
  2. Activate Plugins by F11 - select EMenu - Context menu - Text menu - Open with Code
  3. I get following error message to console attached in screenshot

problem is cannot reproduce if select only one file.
log file was created, but is empty.
I running FAR Manager and Code in User rights context.

Reproduces without extensions: Yes/No - not applicable

2018-01-06 10_24_34- k__ work_software_script-library_bitbucket_actual_my_scripts_myown_autoassembl

@bpasero bpasero assigned joaomoreno and sandy081 and unassigned bpasero Jan 6, 2018
@bpasero bpasero added workbench-diagnostics General VS Code built-in diagnostic issues and removed workbench labels Jan 6, 2018
@joaomoreno
Copy link
Member

Maybe FAR Manager tries to launch Code multiple times in the same second?

@joaomoreno joaomoreno added the bug Issue identified by VS Code Team member as probable bug label Jan 8, 2018
@joaomoreno joaomoreno added this to the December 2017/January 2018 milestone Jan 8, 2018
@joaomoreno joaomoreno added bug Issue identified by VS Code Team member as probable bug windows VS Code on Windows issues workbench-diagnostics General VS Code built-in diagnostic issues and removed bug Issue identified by VS Code Team member as probable bug workbench-diagnostics General VS Code built-in diagnostic issues labels Jan 9, 2018
@joaomoreno
Copy link
Member

Repro steps:

Paste the following in the Command Prompt, in VS Code's dev folder:

start "one" .\scripts\code.bat foo.txt
start "two" .\scripts\code.bat bar.txt

Code should come up with both foo.txt and bar.txt open. None of the newly opened command prompt windows should show an error.

@chrmarti
Copy link
Contributor

chrmarti commented Feb 2, 2018

@joaomoreno I cannot reproduce with these steps in 1.19.3. Any hints on how to do that?

@michalzobec
Copy link
Author

hello, I am sorry, I not get notification.

maybe you have right, this bug maybe initiate FAR Manager. I try use following command

C:\Users\u11478m>code K:!!work\software\script-library\bitbucket\actual\my\scripts\myown\AutoGenAssemblyVersion\ChangeLog.md K:!!work\software\script-library\bitbucket\actual\my\scripts\myown\AutoGenAssemblyVersion\License.md

and I not get any error messages to command line back.

but if I try open files via FAR Manager I still getting error messages as I wrote before.
2018-02-07 13_48_51- k__ work_software_script-library_bitbucket_actual_my_scripts_myown_autogenasse

this behavior is working only for more than one file. If will try only one file in FAR Manager I not get any error message.

@joaomoreno
Copy link
Member

@chrmarti Those steps reliably repro it for me on Windows.

@joaomoreno
Copy link
Member

@michalzobec The fix is still not out. It will come with 1.20.

@michalzobec
Copy link
Author

@joaomoreno hello, in what release this bug was fixed? I cannot found fix 41218 in 1.20.0 and 1.20.1.

@joaomoreno
Copy link
Member

K, I guess I'm going to have to try out FAR Manager.

@michalzobec
Copy link
Author

if you want, I can test it, if you have night build of vscode with this fix.

@bpasero bpasero added workbench-os-integration Native OS integration issues and removed workbench-diagnostics General VS Code built-in diagnostic issues labels Mar 1, 2018
@joaomoreno joaomoreno added the help wanted Issues identified as good community contribution opportunities label Sep 19, 2018
@joaomoreno
Copy link
Member

@michalzobec Is this still an issue for you?

@github-actions github-actions bot locked and limited conversation to collaborators Dec 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug help wanted Issues identified as good community contribution opportunities windows VS Code on Windows issues workbench-os-integration Native OS integration issues
Projects
None yet
Development

No branches or pull requests

5 participants