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

Helm leaving temp files scattered around working directories #5296

Closed
edrex opened this issue Feb 28, 2016 · 6 comments
Closed

Helm leaving temp files scattered around working directories #5296

edrex opened this issue Feb 28, 2016 · 6 comments
Labels
- Forum - Question stale marked as a stale issue/pr (usually by a bot)

Comments

@edrex
Copy link
Contributor

edrex commented Feb 28, 2016

I keep ending up with files like this in random directories:

%2AHelm%20Help%2A#181729Q1

Not sure what action causes these to be created, but I assume it has something to do with helm and help.

Writing to the working directory without user consent is kind of a violation of trust IMO.

@TheBB
Copy link
Contributor

TheBB commented Feb 28, 2016

They look like lockfiles. They can be disabled by setting create-lockfiles to nil. Thought I don't understand what business a helm buffer has doing this kind of thing. I've never seen these.

@edrex
Copy link
Contributor Author

edrex commented Feb 28, 2016

Huh, I think I've been seeing them with low intensity since I started using Spacemacs a few months back. I'm guessing maybe I'm visiting some functionality that you're not, due to my newbity.

I actually already have (setq-default create-lockfiles nil) in my user-config, so double weird.

@edrex
Copy link
Contributor Author

edrex commented Feb 28, 2016

I was wondering if maybe they were left over from before I turned off lockfiles a few weeks ago, but their creation dates are within a couple of days.

@sooheon
Copy link

sooheon commented Feb 29, 2016

I'm seeing something similar using ivy, but they look like #foo.file#. I guess these are lockfiles as well?

@edrex
Copy link
Contributor Author

edrex commented Feb 29, 2016

@sooheon yeah, i think those are just regular lockfiles, and the setting above should stop them being created.

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label Feb 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
- Forum - Question stale marked as a stale issue/pr (usually by a bot)
Projects
None yet
Development

No branches or pull requests

3 participants