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

acmego - check for existing instances #40

Open
skuzzymiglet opened this issue Sep 4, 2020 · 1 comment
Open

acmego - check for existing instances #40

skuzzymiglet opened this issue Sep 4, 2020 · 1 comment

Comments

@skuzzymiglet
Copy link

acmego doesn't report exisiting acmego instances, which can cause weird behaviour (gofmt text doubling). Maybe there should be a lock file? Or just a pidof-like check?

@rsc
Copy link
Contributor

rsc commented Apr 17, 2021

It's OK to have more than one as long as they are attached to different acmes.
I've been meaning to figure out some better way to detect the conflict.
Back when goimports was slow sometimes you'd do a Put and keep editing
and then acmego would show up and change bytes, which was no good either.
If we fix that, it would fix double acmego too.

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

2 participants