plugin doesn't run on vs code 1.6 - Githubissues

nemesv / vscode-copy-file-name

Extension for Visual Studio Code for coping the name of the currently active file.

https://marketplace.visualstudio.com/items?itemName=nemesv.copy-file-name

MIT License

8 stars 1 forks source link

plugin doesn't run on vs code 1.6 #1

Closed sakirsensoy closed 7 years ago

sakirsensoy commented 7 years ago

Plugin didn't work after updating vs code to 1.6 version.

nemesv commented 7 years ago

So far I was not able to reproduce this on my 2 laptops (for me it is working fine in 1.6)

Could you please answer the following questions:

Have you cleanly installed the plugin to 1.6 or you have upgraded your vs code from 1.5?
Have you tried to execute the commands with the shortcuts or selecting them from the command palette (crtl + shift + P)
What do you see in the status bar at the bottom when you try to copy? Do you see the "The filename ",,, was copied to the clipboard." massage?
Which OS are you using?
Have you tried to re-install the plugin?

sakirsensoy commented 7 years ago

i am using ubuntu 16.04 i don't see "The filename ",,, was copied to the clipboard." message. my vs code updated from 1.5 re-installed plugin but problem still continues.

nemesv commented 7 years ago

I'm working on Win 10, so I've installed Ubuntu 16.04 on a VM to try to reproduce your issues, so far without success. For me copying the filename also working on Ubuntu.

But I have noticed that when you are switching between the files in the Explorer pane the keyboard shortcuts are not working and you have to have the cursor in the file window to make them work (although this behavior existed in vs code 1.5)

Could you please try now the followings:

make sure that you have the cursor inside the file window, when using the shortcuts
try to execute the commands from the command palette (ctrl+shift+P) and type "Copy" to find them
how many other extensions are you using? Could you maybe post their name and versions?

nemesv commented 7 years ago

@sakirsensoy have you had time to try out my suggestions? Do you still have this problem?

sakirsensoy commented 7 years ago

Unfortunately, the problem could not be resolved.

nemesv commented 7 years ago

Could you try one more thing?

Open the developer tools (from the Help menu or from the command palette: "Developer: Toggle Developer Tools" and check whether you see any errors in the console, when you try to use the shortcut?

nemesv commented 7 years ago

@sakirsensoy Could you please check this issue with with the new 1.7.1 version?

nemesv commented 7 years ago

I'm closing this now. Feel free to reopen this issue if you still have this problem in the latest version of VS Code (1.7.2).