Skip to content

Conversation

ivan-m
Copy link
Contributor

@ivan-m ivan-m commented Mar 13, 2015

I didn't think about the case that find-file was called to create a new file in an as-yet-nonexistent directory.

@ivan-m
Copy link
Contributor Author

ivan-m commented Mar 13, 2015

Actually, that probably isn't a bad idea.

What I was thinking of doing was adding in support of being able to automatically traverse non-existent path components (I use haskell-cabal-guess-setting to create a module skeleton, and the skeleton is inserted before I can call make-directory, hence how I found this issue). The problem with that is that haskell-cabal-find-file currently tries to ensure that the cabal file is owned by the same user as the directory that starting directory, but the starting directory doesn't actually exist yet.

Any suggestions on how to do that?

@gracjan
Copy link
Contributor

gracjan commented Mar 13, 2015

(Can you change the name of haskell-guess-setting to haskell-cabal-guess-setting while you are at it?)

I know that haskell-cabal-find-file should return nil if the .cabal file is not available for some reason instead of causing issues.

I do not think I understood what you try to achieve so I cannot comment on that, sorry.

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

Successfully merging this pull request may close these issues.

2 participants