-
Notifications
You must be signed in to change notification settings - Fork 345
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
Don't ask to 'create new project' with the same name #124
Comments
Is this a Cabal-based project? The only time I've had something like this occur is when I'm hacking on something that doesn't have a .cabal file... |
I confirm the bug, on emacs 23 and 24. I never once experienced automatic assignment to a project and it always first asks about creating a new project, only then about adding to an existing one. |
@ivan-m It is a cabalized project. |
Huh, interesting; it always seems to work for me. What have the two of you got in your haskell-mode configuration? |
That's the config for emacs 23: |
I can't see anything drastically different/wrong there compared to my own config; the main difference is is that I'm using Emacs-24... |
Here's mine; nothing out of the ordinary, I don't think. edit: weird, it seems to have fixed itself. |
I've just pulled newest haskell-mode and tried emacs 24.2.1. No luck. It asks me to start a new process for each file that I run C-cC-c for the first time on. I tried with and without 'make compile' for haskell mode. I can try with minimal emacs config if that's helpful. BTW, here are my extra changes for 24.2.1, though just a couple of them tweaks haskell-mode: Mikolaj/mydotflies@21e4e3e. Edit: also, it's the same on 3 different projects I tried (all with cabal files, I tried both cabal and cabal-dev). |
I wonder whether it's because of you saying you're running C-c C-c on it; does the same thing happen if you try to load the new file into ghci? Alternatively, does this issue happen if you use the example init.el file (i.e. Do you have a custom ~/.ghci file that could be doing something? Or maybe it's something to do with the project you're working on :/ |
I tried exactly the same sequence of module loads in various setups and here are the results.
Yes, it's the same when I do C-cC-l instead, if that's what you mean. Except that, additionally, I apparently need to load module in a proper order or I get things like
(No such problems with C-cC-c.)
Yes, no change here. When I do
and then C-cC-c (or C-cC-l) on files, it always asks me to start a new project. But when I just run emacs -Q --load examples/init.el and load files manually before C-cC-c it does not ask me to open a new project. It's a paradise. Except that I need to load dozens of files into buffers manually, that is.
I don't have any ~/.ghci.
Probably not, since it works OK if I don't load files in bulk via command line or emacs.desktop. The project above is just
with nothing very special in it. |
Ahhh, I think the issue is that you're opening the files all at once, Try this:
|
I tried what you proposed and it worked, but this gave me an idea and then it fixed itself altogether. It turns out I have some symbolic links in my home directory. Both my emacs.desktop file and the directory I used when loading files from the command line were behind symbolic links. I now use the unlinked paths and it works perfectly. Thank you very much. I'm now a very happy hacker. :) |
@lightquake if it seems to be working for you now, can you close the issue? |
Sure, I can't replicate it any more so I'll just close it. |
I keep getting prompted to create a new project or load an existing one for each file in my project, since it doesn't 'guess' that it should just use the existing one with the same name.
The text was updated successfully, but these errors were encountered: