Skip to content

Haskell-mode crashing and buffer erased (not sure exactly where problem is) #594

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

Closed
rietmann opened this issue Apr 23, 2015 · 3 comments
Closed

Comments

@rietmann
Copy link
Contributor

In the last days, I've had some very strange behavior when working on my latest haskell project. I'm editing along normally, I think I hit save, or maybe switch buffers and suddenly the buffer I was editing is blank and has been saved to disk! (no text at all, 0 bytes in filesystem). Additionally it seems that haskell-mode has crashed (it doesn't show in status bar). It's only happened twice, and I can never quite remember which keys I just hit; I was just in the flow, if you know what I mean. I don't know if there is a log of keystrokes or commands in emacs.

I'm running Haskell-mode, with stylish-haskell, Helm, and company mode, mostly installed via the Prelude emacs setup, with a few vanilla customizations, and flycheck.

Luckily I'm running Dropbox, so when it happens I can quickly go to their web interface and get the version just before the file is wiped out.

Now, I'm mostly looking for help to debug the issue. I'm reasonably proficient with Emacs, but I'm at a total loss here.

I'm running the newest stable emacs (24.5.1) and haskell-mode version 13.12 (elpa/haskell-mode-20150420.2132). Stylish-haskell (stylish-haskell-0.5.11.0).

My only idea is that somehow something goes wrong in the stylish-haskell update, that it crashes while updating the text?

How can I debug this, or what might be the problem? It's a little scary because sometimes Dropbox crashes on my Linux machine and could lose quite a bit of work.

@geraldus
Copy link
Contributor

@rietmann, you can hit C-h l to see last 300 input keystrokes.

@rietmann
Copy link
Contributor Author

@geraldus Thanks for the tip. If it happens again, I'll make sure to try that and post back.

@gracjan
Copy link
Contributor

gracjan commented Oct 16, 2015

Reopen if you have experienced this issue again. Thanks.

@gracjan gracjan closed this as completed Oct 16, 2015
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