Re: I sent in a bug report and never heard anything back

2016-08-27 Thread Brian Inglis
On 2016-08-27 10:27, jeff wrote: Brian Inglis wrote: Apparently it's a mobile Broadwell without AVX or AVX2, which might be assumed present in gcc as compiled, requiring a custom gcc build to run on that cpu. My reply: You are correct. The gcc people replied to my bug report with: "So the problem

Re: Script broken after updating bash to 4.3.46-7?

2016-08-27 Thread Gene Pavlovsky
Andrey, That's what I personally think, none of the scripts I use have CRs, and this is why I'd prefer not using the `igncr` option. However the recent change to how `read` works makes it necessary to modify existing scripts which interoperate with Windows console programs (in my case, Windows buil

Re: Proposal for new cygwin.bat which is independent from install directory

2016-08-27 Thread Andrey Repin
Greetings, Christian Franke! > Andrey Repin wrote: >>> Hmm... therefore it is also better to change the last line to: >>> .\bash --login -i >> "%~dp0bin\bash.exe" --login -i > Changing the directory before bash is run is a security measure because > the current directory may be in DLL search

Re: Proposal for new cygwin.bat which is independent from install directory

2016-08-27 Thread Christian Franke
Andrey Repin wrote: Hmm... therefore it is also better to change the last line to: .\bash --login -i "%~dp0bin\bash.exe" --login -i Changing the directory before bash is run is a security measure because the current directory may be in DLL search path. I guess this is one reason why the

Re: bash: igncr shell option breaks my PS1 prompt

2016-08-27 Thread Andrey Repin
Greetings, Gene Pavlovsky! > # PS1='\e[1;30m\D{%T}\e[m$(test \j -ne 0 && echo "\e[1;37mj:\j\e[m")${STY:+ > \e[1;32m${STY%%.*}\e[m} \e[1;33m\w\e[m\n# ' > 14:32:22 /usr/local/bin > # set -o igncr > bash: command substitution: line 1: syntax error near unexpected token `)' > bash: command substituti

Re: I sent in a bug report and never heard anything back

2016-08-27 Thread jeff
Brian Inglis wrote: Apparently it's a mobile Broadwell without AVX or AVX2, which might be assumed present in gcc as compiled, requiring a custom gcc build to run on that cpu. My reply: You are correct. The gcc people replied to my bug report with: "So the problem is your GMP/MPFR are compiled

Re: Script broken after updating bash to 4.3.46-7?

2016-08-27 Thread Andrey Repin
Greetings, Gene Pavlovsky! > Looks like it's related to a recent change in bash, which is `read` > now honors Cygwin-specific `igncr` shell option (`set -o igncr`), > which I didn't enable. > Adding `set -o igncr` to the top of the script does the job, however > I'd like to know how many more scri

Re: Proposal for new cygwin.bat which is independent from install directory

2016-08-27 Thread Andrey Repin
Greetings, Christian Franke! >> Also don't see why so complicated. While staying in the console, how >> about: >> - >> @echo off >> >> cd /d "%~dp0\bin" >> >> bash --login -i >> - > An errorlevel check is IMO mandatory after a cd command. Absolutely unnecessary. --login will change the C

Re: Proposal for new cygwin.bat which is independent from install directory

2016-08-27 Thread Andrey Repin
Greetings, Christian Franke! > Andrey Repin wrote: >> ... >> Why so complicated? >> >> @START "" /B "%~dp0bin\mintty.exe" - >> >> Done. > Possibly not. This does not run bash in current console. It starts a new > mintty Window. Who in their right mind would want a bogus native console? You? Ok,

Re: Proposal for new cygwin.bat which is independent from install directory

2016-08-27 Thread Bengt Larsson
Christian Franke wrote: >Bengt Larsson wrote: >> - >> @echo off >> >> cd /d "%~dp0\bin" >> >> bash --login -i >> - > >An errorlevel check is IMO mandatory after a cd command. Otherwise >another bash in the PATH might be started if the directory does not exist. >Hmm... therefore it is also

Re: Proposal for new cygwin.bat which is independent from install directory

2016-08-27 Thread Thomas Wolff
Am 27.08.2016 um 13:24 schrieb Christian Franke: Bengt Larsson wrote: Andrey Repin wrote: The following should work since WinXP regardless of install directory: - @echo off cd /d %~dp0 if errorlevel 1 exit /b 1 cd bin if errorlevel 1 exit /b 1 bash --login -i - Why so complicated? A

bash: igncr shell option breaks my PS1 prompt

2016-08-27 Thread Gene Pavlovsky
Apparently the latest bash in Cygwin modified the read builtin to use Cygwin-specific shell option igncr to control ignoring \r characters in the input (still not clear if that ignores \r\n sequences, or \r followed by anything else will be also ignored). This broke a mysql database backup script I

Re: Proposal for new cygwin.bat which is independent from install directory

2016-08-27 Thread Christian Franke
Andrey Repin wrote: ... Why so complicated? @START "" /B "%~dp0bin\mintty.exe" - Done. Possibly not. This does not run bash in current console. It starts a new mintty Window. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentat

Re: Proposal for new cygwin.bat which is independent from install directory

2016-08-27 Thread Christian Franke
Bengt Larsson wrote: Andrey Repin wrote: The following should work since WinXP regardless of install directory: - @echo off cd /d %~dp0 if errorlevel 1 exit /b 1 cd bin if errorlevel 1 exit /b 1 bash --login -i - Why so complicated? Also don't see why so complicated. While staying in

Re: Proposal for new cygwin.bat which is independent from install directory

2016-08-27 Thread Bengt Larsson
Andrey Repin wrote: >Greetings, Christian Franke! > >> Traditionally setup.exe creates the /cygwin.bat file as follows if >> C:\cygwin is the install directory: >> - >> @echo off > >> C: >> chdir C:\cygwin\bin > >> bash --login -i >> - > > >> The following should work since WinXP regardles