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
Regression: C-c C-l keeps asking for a new session for different files within the same project #265
Comments
Hmm. It would be surprising if there's a regression here; nobody touches that session code, not since last year. Can you reduce it to a test-case of a few files that I can reproduce exactly locally? |
@ozataman I just pushed a change c8a72bd which fixes a bug where when picking a session for a file, if there is an incomplete session which doesn't have a cabal-dir assigned to it yet, it will prompt for a cabal dir—which would then assign that directory to that incomplete session, even though you already had another session next on the list which would've been the right candidate. This made it pretty hard to reproduce when it happened so it's taken me a while to both notice it and be in a position to investigate it. Maybe this is the behaviour you were experiencing here. |
Good to know, thank you. I'll pull and see if I see it again. I've On Monday, May 12, 2014, Chris Done notifications@github.com wrote:
Ozgun Ataman CEO Soostone Inc. +1 917 725 0849 (Office) |
There is also sometimes I think I've noticed a prompt for a project I was already in, but it's rare enough that I haven't noticed and am not sure it actually exists as a bug. If I see it again I'll pin it down and fix it. |
Oh, there it is! It's not quite as I described, but it's as I remembered. For some reason, calling |
Okay, fixed that. I wonder if this'll fix this issue. |
How is it possible to make |
If I understand correctly original issue is resolved. If not do not hessitate to leavea note here. As for the other request to simplify |
Even after starting a session called
project
forproject/Foo.hs
, C-c C-l keeps asking whether we should start a new project namedproject
for each newly introduced file under the same project.This broke only recently (unless it was done by design, in which case I would ask that we create a flag to enable/disable it).
The text was updated successfully, but these errors were encountered: