I'm using AkelPAD from a couple of days, and I like it very much.
Nonetheless, I have a (small) problem: using AkelPad as the default editor for the GIT commits, it does not open the correct commit file; it opens a blnk file, asking the user the permission to create it (??!)
Any idea on how to fix this?
Thank you in advance!
Posted: Wed Sep 30, 2015 6:43 pm
by Skif_off
Nova
Maybe length of full name (path/filename) is more MAX_PATH (260 characters)?
Actually, GIT creates a COMMIT_EDITMSG file inside its ".git" folder, and tries to open that one....
Posted: Thu Oct 01, 2015 8:40 am
by DV
What is the full path name to the file COMMIT_EDITMSG?
And, if you look at the system properties of the folder which contains this file, are you sure that you (your user) have "Full control" and "Modify" allowed under the Security tab?
Posted: Thu Oct 01, 2015 8:52 am
by Nova
The path to the file is:
<MyProject>\.git\COMMIT_EDITMSG
In my situation, for testing, I'm using this:
D:\Tmp\TEST\.git\COMMIT_EDITMSG
I noticed I did NOT had full permissions on the folder, but I tried granting full control and modify, and nothing changed.
In particular, I get an error like this:
Create new file "D:\Tmp\TEST"?
Posted: Thu Oct 01, 2015 10:57 am
by Skif_off
Nova
Show file C:\Users\%USERNAME%\.gitconfig please.
Posted: Thu Oct 01, 2015 11:43 am
by Skif_off
Huh, Git uses slash "/", but AkelPad waits backslash "\" in commandline.
Parameter /x solves problem, but I don't know how to add its in commandline.