haskell / haskell/haskell-mode
error "Marker does not point anywhere"
- Dominant language
- Emacs Lisp
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 2
Description
Hi,
I just got started with haskell-mode and am facing a weird issue: whenever I run `haskell-process-load-file` on a file that contains an error, any subsequent runs of this function result in `error "Marker does not point anywhere"`. The full stacktrace reads
```
Debugger entered--Lisp error: (error "Marker does not point anywhere")
goto-char(#)
haskell-interactive-mode-goto-end-point()
(save-current-buffer (set-buffer (haskell-session-interactive-buffer session)) (haskell-interactive-mode-goto-end-point) (let ((mrk (point-marker))) (haskell-session-set session 'next-error-locus nil) (haskell-session-set session 'next-error-region (cons mrk (copy-marker mrk t)))) (goto-char (point-max)))
haskell-interactive-mode-reset-error(((name . "project-name") (next-error-region # . #) (next-error-locus) (interactive-buffer . #) (current-dir . "/home/dakling/Documents/programming/haskell/...") (target . "") (cabal-checksum . "fd8584f682f8bbf497c7bb4d7fbfb956") (cabal-dir . "/home/dakling/Documents/programming/haskell/...") (process (name . "dnschannel") (current-response-cursor . 0) (current-response . "") (command-queue) (inferior-process . #) (is-restarting) (current-command) (suggested-imported) (sent-stdin) (evaluating) (session . #1))))
haskell-process-load-file()
my/haskell-load-and-run()
funcall-interactively(my/haskell-load-and-run)
command-execute(my/haskell-load-and-run)
```
Annoyingly, this error also occurs when I try to restart the haskell process or close the corresponding buffer, forcing me to quit emacs altogether.
I found [this old issue](https://github.com/haskell/haskell-mode/issues/1004) describing a similar problem, but I am not sure if this is related, because 1) this issue seems to be fixed now and 2) my path does not contain any spaces.
My emacs version is 29.1.
Any ideas what is going on here?
Contributor guide
Assessment
This issue has not been assessed yet.