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

creation of nimsuggest.log in home directory #162

Open
samdmarshall opened this issue May 30, 2017 · 4 comments
Open

creation of nimsuggest.log in home directory #162

samdmarshall opened this issue May 30, 2017 · 4 comments

Comments

@samdmarshall
Copy link

samdmarshall commented May 30, 2017

Information

ProductName:	Mac OS X
ProductVersion:	10.12.5
BuildVersion:	16F73

GNU Emacs 25.2.1 via brew

nim-mode 20170409.1737 via https://melpa.org/packages/

contents of ~/.config/nim.cfg:

--verbosity: "2"

Bug

So far I haven't had any issues with using nim-mode, however it does seem to create a nimsuggest.log file in my user home directory. I don't mind this log file being created if i was able to control where it was being written to. Is there any options around how this file is created and where it is placed?

@krux02
Copy link
Contributor

krux02 commented May 31, 2017

Interesting I did not know about nimsuggest.log. It had a size of 1839172114 bytes on my system. I just deleted it. Maybe that is the reason for some problems. I would like to turn it off if I can, because I don't need it.

I think the file is created by nimsuggest. So maybe if you look in the nim projet you can find something there. I found an option called --log to enable verbose logging, but that is the opposite of what I want to do. Nothing else yet.

@yuutayamada
Copy link
Contributor

nim-mode doesn't explicitly specify the "--log" option, so I have no idea about the nimsuggest.log... maybe you could get meaningful answer at nimsuggest repository's issue tracker. (or maybe nimsuggest's bug?)

@yuutayamada
Copy link
Contributor

nim-lang/Nim#6199

@samdmarshall
Copy link
Author

hi, it looks like the sister issue to this has been closed; has anyone tried the fix to see if it works? (i believe it would require using devel version of nim)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants