-
Notifications
You must be signed in to change notification settings - Fork 93
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
Adds a colon after path 'project folder' on network folders #86
Comments
For the key bindings, you likely have a key conflict. You can enter Haven't done much testing with network drives so likely an issue with the plugin. Did you customize any of the settings for the plugin (See |
Yea, for the key binding, the sublime log commands didn't work. But I figured it out, it was another Windows program I use (Enounce MySpeed). So I just remapped it another key. For the network drive, the status bar displays what I showed above: It says this even before entering any content. |
Sorry I misread your initial comment. Is the input panel prefilled with the mentioned content? Also, have you modified the settings for AdvancedNewFile? You can do it either on a per project basis or in |
Sorry for the delay, I've pushed a fix that I believe addresses the issue in 1.2.4. Please confirm that it is fixed for you and close if it is. Thanks for using AdvancedNewFile. |
Issued fixed in 1.2.4. Thanks. |
I'm not sure if this is Windows only, but this is what happens when I try to use it with a network path:
When the input box on the bottom shows, the path is like this:
\NetworkShare\Code\projectname: (Notice the ending colon there)
So, whenever I try to create files, it always appends the project folder name, a colon, and then whatever I name the file.
It gives me an error when trying to create directories, because, well I don't think a colon is allowed for directories.
It works fine for local folders, but for network shares it adds a colon for some reason. Anyone know a workaround, or maybe I need to change a config somewhere?
The text was updated successfully, but these errors were encountered: