On 29/12/2011 21:40, Rafael Kitover wrote:
> Some of my bash scripts, particularly ones that are #!/bin/bash --posix
> trigger a nasty warning when I have SHELLOPTS=igncr set in my ~/.zshrc:
>
> rkitover@eeebox ~/src/scala % echo $SHELLOPTS
> igncr
> rkitover@eeebox ~/src/scala % bash --posix
> ba
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 is a Windows gVim. That
said, I switched the bash
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
I made a perl to test some stuff with perlbrew, a 5.12.0.
I installed some CPAN modules into it, then I needed to rebase because
of mapping errors.
I made a copy of perlrebase and modified it thusly:
#!/bin/sh
baseaddr=0x5700
perl=`which perl`
dll=$(ldd $perl | $perl -anle 'print $F[2] if
Jeremy Bopp-3 wrote:
>
> Another option may be to hack a post-save action into gVim that uses
> Cygwin's chmod command to remove the execute bit from newly saved files:
>
> http://stackoverflow.com/questions/4627701/vim-how-to-execute-automatically-execute-a-shell-command-after-saving-a-file
>
Some of my bash scripts, particularly ones that are #!/bin/bash --posix
trigger a nasty warning when I have SHELLOPTS=igncr set in my ~/.zshrc:
rkitover@eeebox ~/src/scala % echo $SHELLOPTS
igncr
rkitover@eeebox ~/src/scala % bash --posix
bash: SHELLOPTS: readonly variable
this is rather unsightl
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
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 application(s) are they broken?
Here's what I
On Thu, 29 Dec 2011, [UTF-8] Róbert Kohányi wrote:
> Subject: GNU Guile 1.8.7 - readline is not provided
>
> Using a fresh installation of Cygwin with GNU Guile (during the
> install process I've only selected this latter package explicitly)
> I've tried to use Guile's readline support[1] unsucc
Using a fresh installation of Cygwin with GNU Guile (during the
install process I've only selected this latter package explicitly)
I've tried to use Guile's readline support[1] unsuccessfully.
As the documentation told me to, I've created a configuration file
(.guile) in my home directory and star
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
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 your hopes up. Hopefully, the Cygwin changes ar
12 matches
Mail list logo
