We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
nimble setup
config.nims
Running nimble setup (multiple times), every time there is some change in config.nims, it also adds a new empty line at the top of it.
--- a/config.nims +++ b/config.nims @@ -1,6 +1,8 @@ + # begin Nimble config (version 2) +--noNimblePath when withDir(thisDir(), system.fileExists("nimble.paths")): include "nimble.paths" # end Nimble config
Notice that two empty lines already exist (from previous buggy runs of that command), and now it adds a third empty line.
Removing nimble.lock and nimble.paths and running nimble setup again, produces:
nimble.lock
nimble.paths
--- a/config.nims +++ b/config.nims @@ -1,5 +1,7 @@ + + # begin Nimble config (version 2) when withDir(thisDir(), system.fileExists("nimble.paths")): include "nimble.paths"
Now, running nimble lock and then nimble setup produces:
nimble lock
--- a/config.nims +++ b/config.nims @@ -1,6 +1,10 @@ + + + # begin Nimble config (version 2) +--noNimblePath when withDir(thisDir(), system.fileExists("nimble.paths")): include "nimble.paths" # end Nimble config
The text was updated successfully, but these errors were encountered:
fixes #1181; nimble setup adds empty lines to config.nims
95cb0bf
fixes #1181; nimble setup adds empty lines to config.nims (#1193)
45282c4
fixes nim-lang#1181; nimble setup adds empty lines to config.nims (n…
c52a8cb
…im-lang#1193)
ringabout
Successfully merging a pull request may close this issue.
Running
nimble setup
(multiple times), every time there is some change inconfig.nims
, it also adds a new empty line at the top of it.Notice that two empty lines already exist (from previous buggy runs of that command), and now it adds a third empty line.
Removing
nimble.lock
andnimble.paths
and runningnimble setup
again, produces:Now, running
nimble lock
and thennimble setup
produces:The text was updated successfully, but these errors were encountered: