'" . expand("") . "'`\" 2>> ~/.vim/error"
Since my .vim folder is under source control, I'll see if the error file
pops up.
--
View this message in context:
http://old.nabble.com/Distributed-Git-not-compiled-under-Cygwin--tp33047124p33084760.htm
On 12/29/2011 04:31 PM, cxira wrote:
>
>
> Jeremy Bopp-3 wrote:
>>
>> Good stuff. You can avoid the window that pops up by using the run.exe
>> program to kick off your chmod command rather than bash. It's available
>> in the run package.
>>
> I think the window is actually cmd.exe since this i
quot;, "/cygdrive/\\1/", "") . "'"
--
View this message in context:
http://old.nabble.com/Distributed-Git-not-compiled-under-Cygwin--tp33047124p33052477.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Problem reports: http://cy
On 12/29/2011 03:44 PM, cxira wrote:
> I moved away from msysgit because it wasn't displaying colors properly in
> mintty. As for a vim script, I put together something that executes `chmod
> 0644` when saving new files only:
>
> " Change permissions on new files to be 0644 in cygwin
> augroup fil
quot;, "") . "'\""
endfunction
There's a very brief appearance of the command prompt when I save a new
file, but I think it's a suitable and portable solution. Thanks for the
help.
--
View this message in context:
http://old.nabble.com/Distributed-Git-not-compi
On 12/29/2011 02:28 PM, cxira wrote:
>
>
> Jeremy Bopp-3 wrote:
>> I never had a problem with the native gVim cooperating with Cygwin's Git
>> (more accurately file permissions) either. Can you provide more detail
>> about your situation? How exactly are the permissions broken, and for
>> which
iew this message in context:
http://old.nabble.com/Distributed-Git-not-compiled-under-Cygwin--tp33047124p33052021.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation
On 12/29/2011 04:38 AM, cxira wrote:
>
>
> Jeremy Bopp-3 wrote:
>>
>> I don't see any way around this except to either build your own Git that
>> doesn't include the Cygwin changes or run a git config command to set
>> core.filemode after cloning or initializing a repository. Sorry if I
>> got y
can tweak gVim so that it will save files with the
correct permissions.
--
View this message in context:
http://old.nabble.com/Distributed-Git-not-compiled-under-Cygwin--tp33047124p33049604.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Problem reports:
On 12/28/2011 03:53 PM, Jeremy Bopp wrote:
> I also remember reading somewhere once that you should be able create a
> configuration template that would be used by new repositories created by
> git init or git clone that can set the property as you need. I can't
> find any links for that at the mo
On 12/28/2011 03:14 PM, cxira wrote:
>
> I noticed when using the Git that is distributed under the Cygwin setup (Git
> v1.7.5.1-1) that, when creating a new repository, the core.filemode local
> setting is set to true. Being under Windows, this should be false because of
> how file permissions ar
hat should be included,
as I'm not a fan of installing 20 dependencies just to build Git correctly
on every system I use Cygwin on.
--
View this message in context:
http://old.nabble.com/Distributed-Git-not-compiled-under-Cygwin--tp33047124p33047124.html
Sent from the Cygwin list mailing list
12 matches
Mail list logo
