-
Notifications
You must be signed in to change notification settings - Fork 52
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
cygwin provided emacs and pathing #144
Comments
I think we should have the elisp account for it rather than forcing jar file to have to deal with it. Are you using cygwin.el or some other cygwin support for emacs? |
Just the stock cygwin emacs install - if there's some package i should add, I will. FWIW, all the paths look unixish (/cygdrive/c/) from emacs' point of view. I'm running gradle under a cygwin console, but java of course is just making calls straight to windows, so it seems to need the c:/ style pathing in that one case. Not to hijack the issue but, under cygwin, i checked out the jar project and do gradle run. I added (setq malabar-server-port 4429) to my init.el. I'm going to set malabar up on a mac this weekend - i'll try to document that and get you a pull request for the readme, but was hoping to verify that's the "right" way. |
Cygwin: I used to use the cygwin emacs but it crashed too much so I switched. There are some calls it provides for converting file names. I will get back to you. Port 4429: It has been my plan to allow a person to do that very thing but I have not tried it myself. I would be very interested in knowing that it works :) |
If you look at the malabar-util.el there is a function commented out:
We should add this function back in with a new variable Then calls to the http service should use This will allow people to further customize the file name processing to get it into something java understands. If you want to do that, feel free to create a pull request or I will get it taken care of soon. |
I'll dig in to that! I'm not promising today, but i'll try to get you something this weekend. Thanks very much. |
MavenProjectsCreator in MavenProjectHandler.groovy dosn't seem to be happy with paths like /cygdrive/c/work/...
I'm not sure if it's better handled in the mode or in the supporting jar.
Locally, I added this cheesy hack right in MavenProjectsCreator.create, which seemed to work.
pom = pom.replace("/cygdrive/c", "c:")
I haven't dug into predicates for determining the environment - if you have some pointers for what to check, and where you want the code, I'd be willing to spend a couple hours putting together a patch, for the jar. I'm not as familiar with elisp, but if you outline the changes if it should happen on the mode side, i'm willing to take a crack at it.
The text was updated successfully, but these errors were encountered: