-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Question: Weird behavior with newly created go project files #1715
Comments
Yes, this should be considered a bug. |
This seems to work well for me. I actually fixed this before in #1618. |
@Carpetsmoker The issue remains for me even with the latest updates. |
#1618 doesn't solve this problem for me as described by @ stefanos82. All that #1618 does is to make sure the package name is determined correctly. Calling However, calling You can see this result pretty easily with our docker container:
|
I use the latest version of
vim-go
from github usingVim 8.0
under Debian testing 64-bit.vim-go
gives the user the opportunity to open a newmain.go
file in the form of a skeleton.What I usually do when I want to build a new project from scratch is to open a nonexistent folder combined with
main.go
and inside Vim I run a standard command:!mkdir -p %:h
to create my folder and then save my file so I can start working on my project.Immediately after I press my Enter key to return back to Vim from my terminal output, I press
:w
to write on the newly created file that is located in the newly created folder.With
vim-go
I get the following behavior though:As soon as I close Vim and reopen it from the newly created folder with the
main.go
and press the:w
command, now it writes it to the aforementioned location.Should this behavior be considered a bug or no?
Please advice, thank you.
The text was updated successfully, but these errors were encountered: