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

Placement of the nimsuggest.log #6199

Closed
samdmarshall opened this issue Aug 7, 2017 · 4 comments · Fixed by #10646
Closed

Placement of the nimsuggest.log #6199

samdmarshall opened this issue Aug 7, 2017 · 4 comments · Fixed by #10646
Labels

Comments

@samdmarshall
Copy link
Contributor

When using nim-mode in emacs (with nimsuggest), a new log file gets created in my home directory (nimsuggest.log) which contains what i assume is debugging output from the nimsuggest tool. This default placement is really not ideal and was wondering if there was any way I could direct it to a more appropriate directory for writing a log to.

@dom96
Copy link
Contributor

dom96 commented Aug 9, 2017

I noticed this myself for VS code. Strange that nimsuggest would create that, this clutter shouldn't be created by default.

@krux02
Copy link
Contributor

krux02 commented Oct 28, 2018

I removed the "question" tag, because the question part is solved my now. The real issue is "nimsuggest.log shouldn't be created in home". I just checked it nimsuggest.log is still generated. My old log had the size of over 1 GB (that is a problem). But that file was really old I don't know if the same amount of spam is still being generated.

@krux02 krux02 removed the Tools label Oct 29, 2018
@Araq
Copy link
Member

Araq commented Oct 29, 2018

We should simply not generate this file unless nimsuggest is started in a debug/logging mode.

@samdmarshall
Copy link
Contributor Author

did this ship in 0.19.4? or is it still not in a public release yet?

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

Successfully merging a pull request may close this issue.

6 participants