Skip to content

Feature request: guess project from path and save somewhere #118

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
Mikolaj opened this issue Jan 27, 2013 · 6 comments
Closed

Feature request: guess project from path and save somewhere #118

Mikolaj opened this issue Jan 27, 2013 · 6 comments

Comments

@Mikolaj
Copy link
Member

Mikolaj commented Jan 27, 2013

A feature request (unless it's bug that only affects me): I'd like to avoid answering questions for each of the dozens of files in my project whether I like the file to be included in the current project. I suppose this can be guessed from the path or the cabal file. Alternatively or in addition, this information could be saved somewhere for future session, e.g, in the desktop file, if that makes sense.

@nurpax
Copy link
Contributor

nurpax commented Jan 27, 2013

Yes, +1! The same thing happens to me with haskell-interactive-mode and this is painful. It breaks the editing flow when suddenly Emacs starts asking questions when I'm saving a file. I tend to re-start Emacs often and get these questions very frequently.

I would favor that the Haskell mode would simply guess which project a file belongs to by searching for a .cabal file upwards from the file hierarchy from the loaded file until it finds a .cabal file.

I'm not so keen on trying to cache this information in session files. Better to try to guess this well enough so that no cached information is necessary.

I usually only ever have a single active cabal session active. I think in this case, guessing the right active project should be easier.

@Mikolaj
Copy link
Member Author

Mikolaj commented Feb 21, 2013

Apparently the feature works for others, see #124. Also, it now works for me if I load files into emacs manually, one at a time.

@Mikolaj
Copy link
Member Author

Mikolaj commented Feb 21, 2013

Could everybody interested verify that the problem persists if you use no symbolic links in the paths of the files edited with emacs? I can't reproduce it any more when I use direct paths, with no links, see #124. If that's the same for everybody, I guess we can try to improve the code to cope with symbolic links, but we can alternatively write this down in a FAQ or other docs and I'd be happy to close the issue then.

@chrisdone
Copy link
Member

Moving to 13.7 milestone.

@gracjan
Copy link
Contributor

gracjan commented Apr 14, 2015

This issue has not seen activity for a very long time. Is this still something we should be concerned about?

@Mikolaj
Copy link
Member Author

Mikolaj commented Apr 14, 2015

Oh, I'm sorry, it's long ago fixed. thank you!

@Mikolaj Mikolaj closed this as completed Apr 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants