On 2023-10-01 22:49, Cedric Blancher via Cygwin wrote:
Where (URL!!) can I find the package config for the Cygwin bash package?
On the Cygwin site, go to Search Packages, enter the package name, select a link
to the package, select the package link at the top of that file list, select the
Good morning!
Where (URL!!) can I find the package config for the Cygwin bash package?
Ced
--
Cedric Blancher
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation
the original
GNU bash source package against the copy included verbatim in the Cygwin source
package as the build base; the hashes of the downloaded Cygwin bash source and
binary packages against those in your latest downloaded setup.ini or the
x86{,_64}/release/bash/sha512.sum file on your local mirror
Marco Atzeri wrote:
> Am 07.01.2020 um 21:58 schrieb LMH:
>> Hello,
>>
>>
>> This is the version of bash,
>>
>> GNU bash, version 4.3.42(4)-release (i686-pc-cygwin)
>>
>> it would be very helpful as a first step if I could find a verified digital
>> signature
>> for this version of bash. The index
Am 07.01.2020 um 21:58 schrieb LMH:
Hello,
This is the version of bash,
GNU bash, version 4.3.42(4)-release (i686-pc-cygwin)
it would be very helpful as a first step if I could find a verified digital
signature
for this version of bash. The index here,
https://ftp.gnu.org/gnu/bash/
gives a
Hello,
Every single time run bash in a terminal, I get the following firewall alerts,
C:\cygwin\bin\bash.exe
An attempt to communicate a foreign process has been detected.
Target PID: 1616
Image Name: svchost.exe
C:\cygwin\bin\bash.exe
A potential threat to network traffic interception or inject
Am 25.04.2019 um 18:11 schrieb Peter Palaparthy:
> Cygwin bash script is removing equals sign from command call.
On what basis did you conclude it was bash doing that, and not, say, make?
> *Here is the relevant command in my makefile.*
> *$(elabcmd) = $(XELAB_DEFAULT) \-generic VERSI
On 4/25/2019 12:11 PM, Peter Palaparthy wrote:
Cygwin bash script is removing equals sign from command call. How do I
escape it so that = is sent to command?
I tried different things like escaping = with \ and enclosing it with ""
and '' but none of them worked.
*Here is
Cygwin bash script is removing equals sign from command call. How do I
escape it so that = is sent to command?
I tried different things like escaping = with \ and enclosing it with ""
and '' but none of them worked.
*Here is the relevant command in my makefile.*
*$(elabcm
On Thu 2018-03-29 (22:21), Marco Atzeri wrote:
> as it seems you have not done so, likely you have another
> ssh server than cygwin one running on your pc.
Late feedback: this was the case!
Thanks for the hint!
I have now disabled the foreign sshd, reinstalled cygwin openssh server,
opened port 2
On Thu, Mar 29, 2018 at 4:17 PM, Brian Inglis wrote:
>> I would actually like to know how you managed this, as I have a couple
>> use cases where this is what I do need...
>
> W10 Developer mode installs and enables minimal MS SSH server for Settings
> "Device discovery" mDNS service "SSDP Discover
On 2018-03-29 13:35, Ulli Horlacher wrote:
> On Thu 2018-03-29 (13:00), Erik Soderquist wrote:
>> On Thu, Mar 29, 2018 at 10:24 AM, Ulli Horlacher wrote:
>>> I have installed cygwin openssh and the sshd is running.
>>> When I log in, I get a "DOS shell":
>>> ~: uname -a
>>> CYGWIN_NT-6.1 WIN-LS0QDO
On 29/03/2018 21:35, Ulli Horlacher wrote:
On Thu 2018-03-29 (13:00), Erik Soderquist wrote:
On Thu, Mar 29, 2018 at 10:24 AM, Ulli Horlacher wrote:
I have installed cygwin openssh and the sshd is running.
When I log in, I get a "DOS shell":
~: uname -a
CYGWIN_NT-6.1 WIN-LS0QDOSDIBL 2.10.0(0
On 2018-03-29 11:00, Erik Soderquist wrote:
> On Thu, Mar 29, 2018 at 10:24 AM, Ulli Horlacher wrote:
>>
>> I have installed cygwin openssh and the sshd is running.
>> When I log in, I get a "DOS shell":
>>
>> ~: uname -a
>> CYGWIN_NT-6.1 WIN-LS0QDOSDIBL 2.10.0(0.325/5/3) 2018-02-02 15:21 i686 Cygw
On Thu 2018-03-29 (13:00), Erik Soderquist wrote:
> On Thu, Mar 29, 2018 at 10:24 AM, Ulli Horlacher wrote:
>
> >
> > I have installed cygwin openssh and the sshd is running.
> > When I log in, I get a "DOS shell":
> >
> > ~: uname -a
> > CYGWIN_NT-6.1 WIN-LS0QDOSDIBL 2.10.0(0.325/5/3) 2018-02-02
Greetings, Ulli Horlacher!
> I have installed cygwin openssh and the sshd is running.
> When I log in, I get a "DOS shell":
> ~: uname -a
> CYGWIN_NT-6.1 WIN-LS0QDOSDIBL 2.10.0(0.325/5/3) 2018-02-02 15:21 i686 Cygwin
> ~: ssh localhost
> admin@localhost's password:
> C:\users\admin>
> But I wa
On Thu, Mar 29, 2018 at 10:24 AM, Ulli Horlacher wrote:
>
> I have installed cygwin openssh and the sshd is running.
> When I log in, I get a "DOS shell":
>
> ~: uname -a
> CYGWIN_NT-6.1 WIN-LS0QDOSDIBL 2.10.0(0.325/5/3) 2018-02-02 15:21 i686 Cygwin
> ~: ssh localhost
> admin@localhost's password:
I have installed cygwin openssh and the sshd is running.
When I log in, I get a "DOS shell":
~: uname -a
CYGWIN_NT-6.1 WIN-LS0QDOSDIBL 2.10.0(0.325/5/3) 2018-02-02 15:21 i686 Cygwin
~: ssh localhost
admin@localhost's password:
C:\users\admin>
But I want bash as login shell. How can I configure
On 9/30/2015 3:27 PM, Andrey Repin wrote:
> Greetings, Eliot Moss!
>
>> Dealing with "odd" characters like \ and such can be a pain, huh?
>> Perhaps it will help you to know that bash will expand variables
>> inside double-quoted arguments, i.e., "${src}". (You can write
>> "$src" if you want, bu
Hi Paul,
I also get Bad File Descriptor errors, though in a quite different situation,
see my recent topic "gawk: Bad File Descriptor error with concurrent readonly
access to a network file" on Sep 25. There seems to be some issue in some file
opening process that occurs with parallel processes
Greetings, Eliot Moss!
> Dealing with "odd" characters like \ and such can be a pain, huh?
> Perhaps it will help you to know that bash will expand variables
> inside double-quoted arguments, i.e., "${src}". (You can write
> "$src" if you want, but over the years I am finding it clearer /
> bette
Dealing with "odd" characters like \ and such can be a pain, huh?
Perhaps it will help you to know that bash will expand variables
inside double-quoted arguments, i.e., "${src}". (You can write
"$src" if you want, but over the years I am finding it clearer /
better to use the { } to make clear th
I sent this once and it did not appear in the list. Maybe I typed the
list name wrong?
I apologize if this appears twice.
I think the following code below should work (unfortunately, my email
program wants to wrap the code). The results of the echo
statement look fine! When I cut and paste the
> It seems a race problem, due to the repetitive fork of grep
> for every line of some-file
So why does it fail? Seems like a bug to me!
Regards,
Paul
>>>
>>> As does not fail on my computer, I suspect is a race between your AV and
>>> cygwin and sometimes cygwin wi
On 24/09/2015 11:51, lit...@null.net wrote:
.> On 23/09/2015 17:03, lit...@null.net wrote:
It seems a race problem, due to the repetitive fork of grep
for every line of some-file
So why does it fail? Seems like a bug to me!
Regards,
Paul
As does not fail on my computer, I suspect is a race
.> On 23/09/2015 17:03, lit...@null.net wrote:
>>> It seems a race problem, due to the repetitive fork of grep
>>> for every line of some-file
>>
>> So why does it fail? Seems like a bug to me!
>>
>> Regards,
>> Paul
>
> As does not fail on my computer, I suspect is a race between your AV and
> c
On 23/09/2015 17:03, lit...@null.net wrote:
It seems a race problem, due to the repetitive fork of grep
for every line of some-file
So why does it fail? Seems like a bug to me!
Regards,
Paul
As does not fail on my computer, I suspect is a race between your AV and
cygwin and sometimes cygwin
> It seems a race problem, due to the repetitive fork of grep
> for every line of some-file
So why does it fail? Seems like a bug to me!
Regards,
Paul
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/
On 23/09/2015 09:52, lit...@null.net wrote:
Hi all,
On a Windows XP 32 bit machine with latest Cygwin installed
(CYGWIN_NT-5.1 2.2.1(0.289/5/3) 2015-08-20 11:40 i686 Cygwin)
I frequently encounter errors which break bash while loops, making it
practically unusable
e.g.
cat some-file | while
Hi all,
On a Windows XP 32 bit machine with latest Cygwin installed
(CYGWIN_NT-5.1 2.2.1(0.289/5/3) 2015-08-20 11:40 i686 Cygwin)
I frequently encounter errors which break bash while loops, making it
practically unusable
e.g.
cat some-file | while read i;do grep text $i;done
results in
2 [main
Dear Andrey,
> -Original Message-
> From: Andrey Repin [mailto:anrdae...@yandex.ru]
> Sent: Saturday, February 14, 2015 12:40 AM
>
> Greetings, Klemm, Michael!
Yeah, "Lastname, Firstname" is the default for our little company :-).
> > After the last restart (and maybe also after an upd
Greetings, Klemm, Michael!
> After the last restart (and maybe also after an update of Cygwin last
> week), the first start of bash takes hideously long (about 2 minutes). The
> same happens to programs like latexmk:
> $ time latexmk --help
> Latexmk: This is Latexmk, John Collins, 10 January 20
Dear all,
After the last restart (and maybe also after an update of Cygwin last week),
the first start of bash takes hideously long (about 2 minutes). The same
happens to programs like latexmk:
$ time latexmk --help
Latexmk: This is Latexmk, John Collins, 10 January 2015, version: 4.42.
[... m
Greetings, Kal Sze!
> In general, is there anything that can go wrong or not work if I
> invoke regular Windows/.NET executables (not compiled with any cygwin
> header or linked with any cygwin dll) from a cygwin bash terminal or
> script?
Speaking veeery-veeery generally, no. A
Hello,
In general, is there anything that can go wrong or not work if I
invoke regular Windows/.NET executables (not compiled with any cygwin
header or linked with any cygwin dll) from a cygwin bash terminal or
script?
I am planning to write a bash script to call rsync and then a command
line
On Tue, Oct 14, 2014 at 10:54 PM, LMH wrote:
> Thorsten Kampe wrote:
>> * LMH (Sat, 11 Oct 2014 20:30:07 -0400)
>>> Good Lord, I guess I wasn't thinking very clearly trying to use
>>> PATH as
>>> a variable for something else. I changed to,
>>>
>>> FILE_DIR=$(ls -d './'$SET'/'$FOLD'/'$FOLD'_anneal
Thorsten Kampe wrote:
> * LMH (Sat, 11 Oct 2014 20:30:07 -0400)
>> Good Lord, I guess I wasn't thinking very clearly trying to use
>> PATH as
>> a variable for something else. I changed to,
>>
>> FILE_DIR=$(ls -d './'$SET'/'$FOLD'/'$FOLD'_anneal/'$PARAM_SET'/'$AN_SET)
>> echo $FILE_DIR
>>
>> FILE_L
Achim Gratz wrote:
> LMH writes:
>> Good Lord, I guess I wasn't thinking very clearly trying to use PATH as
>> a variable for something else. I changed to,
>>
>> FILE_DIR=$(ls -d './'$SET'/'$FOLD'/'$FOLD'_anneal/'$PARAM_SET'/'$AN_SET)
>> echo $FILE_DIR
>>
>> FILE_LIST=($(ls $FILE_DIR'/'*'out.txt' )
* LMH (Sat, 11 Oct 2014 20:30:07 -0400)
> Good Lord, I guess I wasn't thinking very clearly trying to use
> PATH as
> a variable for something else. I changed to,
>
> FILE_DIR=$(ls -d './'$SET'/'$FOLD'/'$FOLD'_anneal/'$PARAM_SET'/'$AN_SET)
> echo $FILE_DIR
>
> FILE_LIST=($(ls $FILE_DIR'/'*'out.tx
LMH writes:
> Good Lord, I guess I wasn't thinking very clearly trying to use PATH as
> a variable for something else. I changed to,
>
> FILE_DIR=$(ls -d './'$SET'/'$FOLD'/'$FOLD'_anneal/'$PARAM_SET'/'$AN_SET)
> echo $FILE_DIR
>
> FILE_LIST=($(ls $FILE_DIR'/'*'out.txt' ))
> echo ${FILE_LIST[@]}
>
>
Ken Brown wrote:
> On 10/11/2014 8:04 PM, LMH wrote:
>> Hello,
>>
>> I have been working on a bash script and suddenly I started getting an
>> error that ls could not be found,
>>
>> ./remove_rows.sh: line 27: ls: command not found
>>
>> I can run ls from the command line just fine. There is also
On 10/11/2014 8:04 PM, LMH wrote:
Hello,
I have been working on a bash script and suddenly I started getting an
error that ls could not be found,
./remove_rows.sh: line 27: ls: command not found
I can run ls from the command line just fine. There is also an ls
command before line 27 that runs
Hello,
I have been working on a bash script and suddenly I started getting an
error that ls could not be found,
./remove_rows.sh: line 27: ls: command not found
I can run ls from the command line just fine. There is also an ls
command before line 27 that runs fine. This is the part of the script
On 09/26/2014 01:33 PM, Richard DeFuria wrote:
> Hello,
>
> I downloaded the latest setup and installed the latest packages on my Win8.1
> x64 box.
>
> It seems as though my cygwin bash shell has been patched against
> CVE-2014-6271 as per:
> $ env x='() {
On 26/09/2014 21:33, Richard DeFuria wrote:
Hello,
I downloaded the latest setup and installed the latest packages on my Win8.1
x64 box.
It seems as though my cygwin bash shell has been patched against
CVE-2014-6271 as per:
$ env x='() { :;}; echo vulnerable' bash -c "
Hello,
I downloaded the latest setup and installed the latest packages on my Win8.1
x64 box.
It seems as though my cygwin bash shell has been patched against
CVE-2014-6271 as per:
$ env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
bash:
Eric Blake wrote:
On 05/01/2014 04:11 PM, Linda Walsh wrote:
The reason the above fails... (I got it to work).. is that if there is a
space
on the line after the "-u", that also fails.
I didn't deliberately put one there, but that it no longer handles
separate options is an evolution of softwa
Eric Blake wrote:
So why doesn't a single argument work (-u?)
Because you didn't pass a single argument, but left trailing space ...
---
But looking at the file, I didn't notice that until
I recreated the file w/o using cut/paste (i.e. happened
in another script that had -u at the top, and I
On 05/01/2014 04:11 PM, Linda Walsh wrote:
> The reason the above fails... (I got it to work).. is that if there is a
> space
> on the line after the "-u", that also fails.
>
> I didn't deliberately put one there, but that it no longer handles
> separate options is an evolution of software devolu
Bob McGowan wrote:
>> Because you weren't running /bin/bash at that point in time, but
>> /usr/bin/bash. Again, you snipped the relevant portion of your original
>
> No...I was... the output at the top was from "t.sh", which had
> #!/bin/bash.
>
> But the error message says /usr/bin/bash.
On 05/01/2014 12:11 PM, Linda Walsh wrote:
>
> On linux, (and, thus on cygwin?), "#!/bin/bash -u -x -a -b -c"
> is passed as 1 argument to bash. I.e. the spaces don't break things
> into separate arguments on linux.
Correct. So follow it through to it's logical conclusion:
/bin/bash "-u -x -a
Eric Blake wrote:
On 04/30/2014 11:57 PM, Linda Walsh wrote:
Eric Blake wrote:
On 04/28/2014 02:43 PM, Linda Walsh wrote:
cat bin/t.sh
#!/bin/bash -u
Um... it doesn't work with 1 argument either.
Your context quoting is hard to follow. Here, you are complaining about
a she-bang with only
On 04/30/2014 11:57 PM, Linda Walsh wrote:
> Eric Blake wrote:
>> On 04/28/2014 02:43 PM, Linda Walsh wrote:
>>
>> >> cat bin/t.sh
>> > #!/bin/bash -u
> Um... it doesn't work with 1 argument either.
Your context quoting is hard to follow. Here, you are complaining about
a she-bang with only one a
Eric Blake wrote:
On 04/28/2014 02:43 PM, Linda Walsh wrote:
>> cat bin/t.sh
> #!/bin/bash -u
Um... it doesn't work with 1 argument either.
This is an invalid shebang line. Historically, you are allowed at most
ONE argument to the program that you will be executing.
?!?
Historically?.. sin
On 04/28/2014 02:43 PM, Linda Walsh wrote:
>> cat bin/t.sh
> #!/bin/bash -u -x
This is an invalid shebang line. Historically, you are allowed at most
ONE argument to the program that you will be executing.
#!/bin/bash -ux
is valid,
#!/bin/bash -u -x
is not.
> If I run it via:
>> bash t.sh
ne the switches (-ux), it works -- but I only
added the '-x' to debug why '-u' didn't work.
uname -a
CYGWIN_NT-6.1 Athenae 1.7.29(0.272/5/3) 2014-04-07 13:46 x86_64 Cygwin
bash --version
GNU bash, version 4.1.11(2)-release (x86_64-unknown-cygwin)
---
This, also, doesn't
On 2013-12-16, Chris Wolf wrote:
> On Mon, Dec 16, 2013 at 4:58 PM, Chris Wolf wrote:
> > I just installed a recent release of Cygwin and notice that it now
> > features syntax highlighting. Is there a way to totally disable this?
> > All I want is be able to set the foreground/background colors
I was able to come up with something, though not sure it's the best or
what I had before. Sorry if this is obvious to most people, but to
get rid of colorized output, I added to my .bashrc:
export LS_COLORS=''
If $PS1 has terminal color escape codes, then replace that also with
something else, e
I just installed a recent release of Cygwin and notice that it now
features syntax highlighting. Is there a way to totally disable this?
All I want is be able to set the foreground/background colors via the
Windoze way of right clicking on the frame and I don't want the out of
"ls" colorized nor
On Wed, Feb 13, 2013 at 05:47:19PM +, Adam Dinwoodie wrote:
>The UG states
>
>> Cygwin programs expand their arguments starting with "@" in a special way. If
>> a file pathname exists, the argument @pathname expands recursively to the
>> content of pathname.
>-- http://cygwin.com/cygwin-ug-net/
The UG states
> Cygwin programs expand their arguments starting with "@" in a special way. If
> a file pathname exists, the argument @pathname expands recursively to the
> content of pathname.
-- http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-at
It then contrasts "the behaviors
Date: Wed, 17 Oct 2012 13:04:02 -0400
Subject: Re: Bold color in "cygwin bash shell"
Found this nice tip but haven't tried it myself.
http://linuxtidbits.wordpress.com/2009/03/23/less-colors-for-man-pages/
--
Earnie
--
Thanks for all the help. Earnie's suggestio
On 10/17/2012 12:15 PM, Christopher Faylor wrote:
On Wed, Oct 17, 2012 at 01:04:02PM -0400, Earnie Boyd wrote:
On Wed, Oct 17, 2012 at 12:36 PM, Saurabh T wrote:
For various reasons, I cannot switch to rxvt or similar, and am stuck
using the cygwin bash shell (which runs on top of the dos cmd
On Wed, Oct 17, 2012 at 01:04:02PM -0400, Earnie Boyd wrote:
>On Wed, Oct 17, 2012 at 12:36 PM, Saurabh T wrote:
>>For various reasons, I cannot switch to rxvt or similar, and am stuck
>>using the cygwin bash shell (which runs on top of the dos cmd window).
>>
>>Here, th
On Wed, Oct 17, 2012 at 12:36 PM, Saurabh T wrote:
>
> Hi,
>
> For various reasons, I cannot switch to rxvt or similar, and am stuck
> using the cygwin bash shell (which runs on top of the dos cmd window).
>
> Here, the background color defaults to black and foreground to lig
On 10/17/2012 9:36 AM, Saurabh T wrote:
Hi,
For various reasons, I cannot switch to rxvt or similar, and am stuck
using the cygwin bash shell (which runs on top of the dos cmd window).
Might we ask what are the reasons you can't use mintty? If it's because
of other problems perhaps w
On Wed, Oct 17, 2012 at 12:39:27PM -0400, Robert Pendell wrote:
>On Wed, Oct 17, 2012 at 12:36 PM, Saurabh T <...> wrote:
>>For various reasons, I cannot switch to rxvt or similar, and am stuck
>>using the cygwin bash shell (which runs on top of the dos cmd window).
>
&g
On Wed, Oct 17, 2012 at 12:36 PM, Saurabh T <...> wrote:
>
> Hi,
>
> For various reasons, I cannot switch to rxvt or similar, and am stuck
> using the cygwin bash shell (which runs on top of the dos cmd window).
>
> Here, the background color defaults to black and foregr
Hi,
For various reasons, I cannot switch to rxvt or similar, and am stuck
using the cygwin bash shell (which runs on top of the dos cmd window).
Here, the background color defaults to black and foreground to light.
I reversed this using the dos window -> Properties -> Colors.
However th
Sorry, what I posted was completely lacking in context. The shell
option has to be set in such a way that bash sources .bashrc and picks
up the aliases, function definitions, and most importantly, the PATH.
To maintain common vimrc files for Windows & Cygwin installs of vim
across multiple compu
This problem dogged me for many years, and I finally hunkered down to
chase it down.
Here is the solution that I found works for me:
"set shell=c:\cygwin\bin\bash.exe\ -i
"Won't always find ~/.bashrc cuz depending on how vim is launched,
"~ doesn't always resolve to c:/cygwin/home/$USERNAME
Example:
[Start cygwin bash in a terminal]
$ asdfghjkl
asdfghjkl
bash: asdfghjkl: command not found
[enter ^rghj]
[enter left-arrow]
[result after redisplay of the line is:]
$ asdf[Dghjkl
Similar result for right-arror (shows ...[C... )
Doesn't always happen. Load/Timing depe
On Mar 26 05:24, John Fairhall wrote:
> The pipe is definitely the problem.
>
> If I have this:
>
> bash mainScript.sh 2>&1
> bash mailBuild.sh %ERRORLEVEL% %LOGFILE%
>
> When I gimmick mainScript to exit with any non-zero value I get an ERRORLEVEL
> of 255.
>
> However, when I do this:
>
> b
The pipe is definitely the problem.
If I have this:
bash mainScript.sh 2>&1
bash mailBuild.sh %ERRORLEVEL% %LOGFILE%
When I gimmick mainScript to exit with any non-zero value I get an ERRORLEVEL
of 255.
However, when I do this:
bash -o pipefail mainScript.sh 2>&1 | tee $LOGFILE bash mailBuild
John Fairhall wrote:
Hi,
I have a cygwin bash script running on 32 bit XP.
I have a windows BAT script calling bash, like so:
---
bash mainScript.sh 2>&1 | tee %LOGFILE%
bash mailBuild.sh %ERRORLEVEL% %LOGFILE%
---
What I was hoping was that bas
Hi,
I have a cygwin bash script running on 32 bit XP.
I have a windows BAT script calling bash, like so:
---
bash mainScript.sh 2>&1 | tee %LOGFILE%
bash mailBuild.sh %ERRORLEVEL% %LOGFILE%
---
What I was hoping was that bash would propagate the shell s
xt:
http://old.nabble.com/1.7.9-cygwin-bash-completion-doesn%27t-response-tp32688677p32702678.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: http://c
ow in directories with large number of files.
If anything of that does not hep, try following the rules from
http://cygwin.com/problems.html.
Output of ' cygcheck -s -v -r > cygcheck.out 2>&1 ' and OS version might
give some information.
--
View this message in context:
h
hi all,
I got the bash completion problem which is very upset me, following is
an example:
in my home directory, there is a file : pkf
if I want to vi the file and I type :
vi pk(press tab)
but there is no response or it's very slow, but in some cases like say
when I vi the *.cpp files the tab
On 6/20/2011 2:43 PM, Josh Gilmour wrote:
Hi All -
I have been seeing a weird issue with the AMI (ami-1cbd4475) - Windows
2008 R2 SP1. The issue is when I run the command 'if [ -e "file" ];
then echo "test"; fi' from the cygwin command prompt.
When this command is run, the shell closes with no
On 02/08/2011 12:15 PM, Kimbo Mundy wrote:
>> I have not seen that issue, and you're the first to report it, but I'll
>> see if I can reproduce it.
I was able to reproduce this, but not on my machine (thanks Corinna for
getting me set up); and the odd thing was that the problem disappears
when com
On Wed, 02 Feb 2011 12:47:00 -0700, Eric Blake wrote:
> On 02/02/2011 09:38 AM, Philipp Wiendl wrote:
> > Hello,
> >
> > today i installed cygwin v1.7 with the new v4 bash package.
> > I tried to run ssh-host-config and got following error:
> >
> > $ ssh-host-config -y
> > *** Query: Overwrite exis
[adding the list: http://cygwin.com/acronyms/#PPIOSPE]
On 02/02/2011 09:38 AM, Philipp Wiendl wrote:
> Hello,
>
> today i installed cygwin v1.7 with the new v4 bash package.
> I tried to run ssh-host-config and got following error:
>
> $ ssh-host-config -y
> *** Query: Overwrite existing /etc/ss
On 9/26/2010 9:30 AM, MikeS wrote:
Larry Hall (Cygwin cygwin.com> writes:
On 5/27/2010 10:11 AM, RISINGP1 nationwide.com wrote:
I was having trouble with the backspace key, but it was with pdksh, so I
don't know if this will work for you, but it is worth a try...
Andy Koppe gmail.com>
Larry Hall (Cygwin cygwin.com> writes:
>
> On 5/27/2010 10:11 AM, RISINGP1 nationwide.com wrote:
> > I was having trouble with the backspace key, but it was with pdksh, so I
> > don't know if this will work for you, but it is worth a try...
> >
> > Andy Koppe gmail.com> wrote:
> >
> >> From th
On 5/27/2010 10:11 AM, risin...@nationwide.com wrote:
I was having trouble with the backspace key, but it was with pdksh, so I
don't know if this will work for you, but it is worth a try...
Andy Koppe wrote:
From the cygwin-1.7.5 release announcement:
- Support DEC Backarrow Key Mode escape
Windows console.
(The first one switches to ^H. You'll need to set stty erase accordingly.)
- Phil
From:
Christopher Faylor
To:
cygwin@cygwin.com
Date:
05/27/2010 10:03 AM
Subject:
Re: cygwin : bash doesn't recognize BackSpace
Sent by:
cygwin-ow...@cygwin.com
On Thu, May 27, 2010 a
On Thu, May 27, 2010 at 05:49:53PM +0400, Andrei Dmitriev wrote:
>Dave Korn wrote:
>>On 27/05/2010 11:48, Andrei Dmitriev wrote:
>>>after I installed the cygwin on May 19 the bash console don't recognize
>>>*BACKSPACE* and continue to follow to the right each time I
>>>press BACKSPACE.
Eliot Moss wrote:
On 5/27/2010 6:48 AM, Andrei Dmitriev wrote:
** Hello,
after I installed the cygwin on May 19 the bash console don't recognize
*BACKSPACE* and continue to follow to the right each time I
press BACKSPACE.
Although, seem it actually erases the chars from the left (EN
Dave Korn wrote:
On 27/05/2010 11:48, Andrei Dmitriev wrote:
** Hello,
after I installed the cygwin on May 19 the bash console don't recognize
*BACKSPACE* and continue to follow to the right each time I
press BACKSPACE.
Although, seem it actually erases the chars from the left (
On 27/05/2010 11:48, Andrei Dmitriev wrote:
> ** Hello,
>
> after I installed the cygwin on May 19 the bash console don't recognize
> *BACKSPACE* and continue to follow to the right each time I
> press BACKSPACE.
> Although, seem it actually erases the chars from the left (ENTER says
>
** Hello,
after I installed the cygwin on May 19 the bash console don't recognize
*BACKSPACE* and continue to follow to the right each time I
press BACKSPACE.
Although, seem it actually erases the chars from the left (ENTER says
nothing - so I concluded the command is empty).
Tha
On Wed, Nov 25, 2009 at 10:33:53AM -0500, Buchbinder, Barry (NIH/NIAID) [E]
wrote:
>aputerguy sent the following at Tuesday, November 24, 2009 5:10 PM
>>Seriously, there are times to use Perl and times not to... But
>>launching perl seems a bit of overkill when I just have to do a simple
>>match
aputerguy sent the following at Tuesday, November 24, 2009 5:10 PM
>
> Seriously, there are times to use Perl and times not to... But launching
> perl seems a bit of overkill when I just have to do a simple match in a
>.bashrc script or when I need a small shell script wrapper.
Looking at the man
On Nov 24 17:23, Christopher Faylor wrote:
> On Tue, Nov 24, 2009 at 10:18:27PM +, Eric Blake wrote:
> >So, in true open source fashion, why not write a patch that teaches cygwin's
> >regex(3) implementation that \b is a synonym to [[:<:][:>:]]?
> >[...]
> If anyone does this they should remem
Dave Korn googlemail.com> writes:
>
> $ [[ "foo" =~ [[:\<:]]foo[[:\>:]] ]]; echo $?
> 0
>
> (Note that I had to backslash-escape the < and > there. In other contexts
> that might not be needed.)
But here's something weird with how bash manages quoting inside [[ ]]. If you
add a subexpress
aputerguy schrieb:
Hugh Myers:
This might come across as slightly smart-assed, but if you wrote your
script in Perl, you wouldn't have the platform problem, nor the
word-boundary problem. True you would have a Perl problem, but that
would still be several orders of magnitude easier than tryi
On Tue, Nov 24, 2009 at 10:18:27PM +, Eric Blake wrote:
>aputerguy kosowsky.org> writes:
>
>> HOWEVER, this solution while sweet for cygwin-bash, has the CONVERSE
>> PROBLEM.
>> Apparently, the special strings [[:<:]] and [[:>:]] are not recognized under
>
aputerguy kosowsky.org> writes:
> HOWEVER, this solution while sweet for cygwin-bash, has the CONVERSE
> PROBLEM.
> Apparently, the special strings [[:<:]] and [[:>:]] are not recognized under
> Linux regex(7) - they give return code 2.
And why is that surprising?
What I have often done in a case like this is:
Add the separator (space in this case) at each end of the list.
So, if the initial string is "101 203 455" I turn that into
" 101 203 455 ".
LIST=" ${LIST} "
Then I match the desired string, also surrounded by spaces,
like this:
[ -z "${LIST##* ${
1 - 100 of 395 matches
Mail list logo
