Re: Modify bash shell script so it runs in elevated admin mode on Win explorer double click?

Greetings, Jeremy Drake! > On Fri, 11 Apr 2025, Andrey Repin via Cygwin wrote: >> Though, I'm using takecommand's free runtime (TCC-RT), which has an explicit >> START /ELEVATED command, and I'm using a wrapper for such tasks. > cygutils' > cygstart -a runas /bin/bash ... ? runas is not necessa

Re: Modify bash shell script so it runs in elevated admin mode on Win explorer double click?

On Fri, 11 Apr 2025, Andrey Repin via Cygwin wrote: > Though, I'm using takecommand's free runtime (TCC-RT), which has an explicit > START /ELEVATED command, and I'm using a wrapper for such tasks. cygutils' cygstart -a runas /bin/bash ... ? -- Problem reports: https://cygwin.com/problems.

Re: Modify bash shell script so it runs in elevated admin mode on Win explorer double click?

On 2025-04-11 14:11, Backwoods BC wrote: On Fri, Apr 11, 2025 at 9:32 AM Brian Inglis via Cygwin wrote: On 2025-04-11 10:21, Mark Liam Brown via Cygwin wrote: Greetings! How can I modify a Cygwin bash script so it runs in elevated Administrator mode when someone double-clicks it in Windows E

Re: Modify bash shell script so it runs in elevated admin mode on Win explorer double click?

On 2025-04-11 10:46, Mark Liam Brown via Cygwin wrote: On Fri, Apr 11, 2025 at 6:32 PM Brian Inglis via Cygwin wrote: On 2025-04-11 10:21, Mark Liam Brown via Cygwin wrote: Greetings! How can I modify a Cygwin bash script so it runs in elevated Administrator mode when someone double-clicks i

Re: Modify bash shell script so it runs in elevated admin mode on Win explorer double click?

On Fri, Apr 11, 2025 at 9:32 AM Brian Inglis via Cygwin wrote: > > On 2025-04-11 10:21, Mark Liam Brown via Cygwin wrote: > > Greetings! > > > > How can I modify a Cygwin bash script so it runs in elevated > > Administrator mode when someone double-clicks it in Windows Explorer? > > Use a Run as a

Re: Modify bash shell script so it runs in elevated admin mode on Win explorer double click?

Greetings, Mark Liam Brown! > How can I modify a Cygwin bash script so it runs in elevated > Administrator mode when someone double-clicks it in Windows Explorer? Add a block that runs an admin only command and check for exit code. The `net session` or `openfiles` commands are a good candidate fo

Re: Modify bash shell script so it runs in elevated admin mode on Win explorer double click?

On Fri, Apr 11, 2025 at 6:32 PM Brian Inglis via Cygwin wrote: > > On 2025-04-11 10:21, Mark Liam Brown via Cygwin wrote: > > Greetings! > > > > How can I modify a Cygwin bash script so it runs in elevated > > Administrator mode when someone double-clicks it in Windows Explorer? > > Use a Run as a

Re: Modify bash shell script so it runs in elevated admin mode on Win explorer double click?

On 2025-04-11 10:21, Mark Liam Brown via Cygwin wrote: Greetings! How can I modify a Cygwin bash script so it runs in elevated Administrator mode when someone double-clicks it in Windows Explorer? Use a Run as admin shortcut? -- Take care. Thanks, Brian Inglis Calgary, Alberta, C

Modify bash shell script so it runs in elevated admin mode on Win explorer double click?

Greetings! How can I modify a Cygwin bash script so it runs in elevated Administrator mode when someone double-clicks it in Windows Explorer? Mark -- IT Infrastructure Consultant Windows, Linux -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/f

cygport check log tee bash shell > 100MB > 2600 threads

Hi folks, Running cygport under Cygwin 3.6 for coreutils 9.6, during the post-build check/Testing stage the bash shell spawning the check log tee job is showing > 100MB memory SZ > 28000 pages used > 2600 threads spawned! Has anyone else noticed this or anything similar recently?

Re: bash shell script: recently running, now failing

Greetings, Brian Inglis via Cygwin! > On 2023-04-06 06:21, Andrey Repin via Cygwin wrote: >>> I have a "hash bang" bash shell script i.e. first line >>> #! /bin/sh >>> or equivalently >>> #! /bin/bash >> By default, sh is bash in base Cygwin

Re: bash shell script: recently running, now failing

On 2023-04-06 06:21, Andrey Repin via Cygwin wrote: I have a "hash bang" bash shell script i.e. first line #! /bin/sh or equivalently #! /bin/bash By default, sh is bash in base Cygwin installation. Q3 - at 1/8 the size of bash and sh, I am not at all sure of the role and reac

Re: bash shell script: recently running, now failing

gt; On Thu, Apr 06, 2023 at 04:43:51AM +, Fergus Daly via Cygwin wrote: > > I have a "hash bang" bash shell script i.e. first line > > #! /bin/sh > > or equivalently > > #! /bin/bash > > For various reasons I want this file to be identified as binary so its

Re: bash shell script: recently running, now failing

On Thu, Apr 06, 2023 at 04:43:51AM +, Fergus Daly via Cygwin wrote: > I have a "hash bang" bash shell script i.e. first line > #! /bin/sh > or equivalently > #! /bin/bash > For various reasons I want this file to be identified as binary so its second > line > is

Re: bash shell script: recently running, now failing

Greetings, Fergus Daly! > I have a "hash bang" bash shell script i.e. first line > #! /bin/sh > or equivalently > #! /bin/bash By default, sh is bash in base Cygwin installation. > Q3 - at 1/8 the size of bash and sh, I am not at all sure of the role and > reac

Re: bash shell script: recently running, now failing

Place the nul on the third line. For example: #!/bin/bash # # ^@ identify as a binary file ... On Thu, Apr 6, 2023 at 4:03 AM Corinna Vinschen via Cygwin < cygwin@cygwin.com> wrote: > On Apr 6 04:43, Fergus Daly via Cygwin wrote: > > I have a "hash bang" bash she

Re: bash shell script: recently running, now failing

On Apr 6 04:43, Fergus Daly via Cygwin wrote: > I have a "hash bang" bash shell script i.e. first line > #! /bin/sh > or equivalently > #! /bin/bash > For various reasons I want this file to be identified as binary so its second > line > is the single charact

bash shell script: recently running, now failing

I have a "hash bang" bash shell script i.e. first line #! /bin/sh or equivalently #! /bin/bash For various reasons I want this file to be identified as binary so its second line is the single character null \x00 showing up in some editors e.g. nano as ^@ This does not prevent the s

RE: Starting CMD from a bash shell with current directory on a mounted/network drive results in an incorrect current directory

Cool, thanks. -Original Message- From: Cygwin On Behalf Of Corinna Vinschen Sent: 13 December 2021 15:06 To: cygwin@cygwin.com Subject: Re: Starting CMD from a bash shell with current directory on a mounted/network drive results in an incorrect current directory On Dec 13 20:06, Takashi

Re: Starting CMD from a bash shell with current directory on a mounted/network drive results in an incorrect current directory

On Dec 13 20:06, Takashi Yano wrote: > On Mon, 13 Dec 2021 10:53:41 - > "john daintree" wrote: > > I've just upgraded a machine from Windows 10 to Windows 11. Part of my work > > process is now broken because when starting cmd from Cygwin with the current > > directory on a mounted drive I get

RE: Starting CMD from a bash shell with current directory on a mounted/network drive results in an incorrect current directory

Excellent news, thank you. I apologise if I should have seen that somewhere. /John -Original Message- From: Cygwin On Behalf Of Takashi Yano Sent: 13 December 2021 11:06 To: cygwin@cygwin.com Subject: Re: Starting CMD from a bash shell with current directory on a mounted/network drive

Re: Starting CMD from a bash shell with current directory on a mounted/network drive results in an incorrect current directory

On Mon, 13 Dec 2021 10:53:41 - "john daintree" wrote: > I've just upgraded a machine from Windows 10 to Windows 11. Part of my work > process is now broken because when starting cmd from Cygwin with the current > directory on a mounted drive I get the following error/warning/issue: > > > >

Starting CMD from a bash shell with current directory on a mounted/network drive results in an incorrect current directory

Hello All, I've just upgraded a machine from Windows 10 to Windows 11. Part of my work process is now broken because when starting cmd from Cygwin with the current directory on a mounted drive I get the following error/warning/issue: /cygdrive/j$ cmd '\\nas00.\devt\users\johnd' CMD.EXE

Re: ESC followed by UP-arrow cause bash shell to hang

On Sat, Jan 6, 2018 at 4:49 PM, Jim Reisert wrote: > [...] ESC followed by UP-arrow. This seems to lock up the > bash shell for about 30 seconds before control returns. Your up-arrow is probably a character sequence that starts with an Esc (you can verify that by typing a Ctrl+V followed b

Re: ESC followed by UP-arrow cause bash shell to hang

something else. Ctrl + W also works: $ bind -q unix-word-rubout unix-word-rubout can be invoked via "\C-w". Occasionally I type these two keys out-of-order, ESC followed by UP-arrow. This seems to lock up the bash shell for about 30 seconds before control returns. not for me - it

ESC followed by UP-arrow cause bash shell to hang

-order, ESC followed by UP-arrow. This seems to lock up the bash shell for about 30 seconds before control returns. What's going on here? Is there something I'm doing wrong, or is there a way to prevent this, other than being a better typist? -- Jim Reisert AD1C, , http://www.ad1c.us

Re: How to repeat a bash shell script until success

On July 14, 2017 9:06:02 AM EDT, cyg Simple <> wrote: >On 7/14/2017 1:27 AM, Gary Johnson wrote: >> On 2017-07-12, Bryan Dunphy wrote: >>> I have a shell script, originally created for Mac OS X. that waits >>> for an external drive to be mounted (by . >> > >In reality the OP script appears to be e

Re: How to repeat a bash shell script until success

On 7/15/2017 2:56 AM, Sorin Adrian Savu wrote: > On Fri, Jul 14, 2017 at 4:06 PM, cyg Simple wrote: >> >> On 7/14/2017 1:27 AM, Gary Johnson wrote: >>> On 2017-07-12, Bryan Dunphy wrote: I have a shell script, originally created for Mac OS X. that waits for an external drive to be mounte

Re: How to repeat a bash shell script until success

On Fri, Jul 14, 2017 at 4:06 PM, cyg Simple wrote: > > On 7/14/2017 1:27 AM, Gary Johnson wrote: > > On 2017-07-12, Bryan Dunphy wrote: > >> I have a shell script, originally created for Mac OS X. that waits > >> for an external drive to be mounted (by testing an “ls” of the > >> volume’s root dir

Re: How to repeat a bash shell script until success

On 14.07.2017 10:34, Brian Inglis wrote: On 2017-07-14 11:07, Kaz Kylheku wrote: while ! program args ... ; do sleep 1 done Has everyone forgotten there is also an until loop, supported by at least sh, dash, bash, [m]ksh: I've forgotten that at least twice. (I don't remember the ex

Re: How to repeat a bash shell script until success

On 2017-07-14 11:07, Kaz Kylheku wrote: > On 12.07.2017 08:35, Bryan Dunphy wrote: >> I have a shell script, originally created for Mac OS X. that waits for >> an external drive to be mounted (by testing an “ls” of the volume’s >> root directory for success) then runs an “rsync” >> command. How do

Re: How to repeat a bash shell script until success

On 12.07.2017 08:35, Bryan Dunphy wrote: I have a shell script, originally created for Mac OS X. that waits for an external drive to be mounted (by testing an “ls” of the volume’s root directory for success) then runs an “rsync” command. How do I get the script to be run repeatedly until success

Re: How to repeat a bash shell script until success

On 7/14/2017 1:27 AM, Gary Johnson wrote: > On 2017-07-12, Bryan Dunphy wrote: >> I have a shell script, originally created for Mac OS X. that waits >> for an external drive to be mounted (by testing an “ls” of the >> volume’s root directory for success) then runs an “rsync” command. >> How do I ge

Re: How to repeat a bash shell script until success

On 2017-07-12, Bryan Dunphy wrote: > I have a shell script, originally created for Mac OS X. that waits > for an external drive to be mounted (by testing an “ls” of the > volume’s root directory for success) then runs an “rsync” command. > How do I get the script to be run repeatedly until successf

Re: How to repeat a bash shell script until success

On 2017-07-12 09:35, Bryan Dunphy wrote: > I have a shell script, originally created for Mac OS X. that waits for an > external drive to be mounted (by testing an “ls” of the volume’s root > directory for success) then runs an “rsync” command. How do I get the script > to be run repeatedly until

How to repeat a bash shell script until success

I have a shell script, originally created for Mac OS X. that waits for an external drive to be mounted (by testing an “ls” of the volume’s root directory for success) then runs an “rsync” command. How do I get the script to be run repeatedly until successful exit under Cygwin? Here is the unmo

Re: Bash shell inside JPSOFT Take Command does not respond to input

The problem was the Windows 10 Insider build I was using at the time: Version 6.3.16193 It seems to work again in Build 16226, both in JPSoft Take Command as well as Windows 10 "cmd". -- Jim Reisert AD1C, , http://www.ad1c.us -- Problem reports: http://cygwin.com/problems.html FAQ:

Re: Bash shell inside JPSOFT Take Command does not respond to input

On 2017-05-14 19:45, Jim Reisert AD1C wrote: > I can't seem to get a bash shell to run inside of JP Software's Take > Command: >www.jpsoft.com > Behavior is the same in both TC and TCC - a shell starts, but I > can't type anything into it. This used to work in

Re: Bash shell inside JPSOFT Take Command does not respond to input

Greetings, Jim Reisert AD1C! > I can't seem to get a bash shell to run inside of JP Software's Take Command: >www.jpsoft.com They have their own support forum, BTW. > Behavior is the same in both TC and TCC - a shell starts, but I can't > type anything into it

Re: bash shell gets aborts under latest Windows 10 updates as of 4/2/17

Greetings, Fran Litterio! > On 5/5/2017 7:30 AM, Andrey Repin wrote: >>> You can rebase all the DLLs as follows: >> >> That's not how to do it. >> >> 1. Run >> >>rebase-trigger full >> >> 2. Shutdown all Cygwin processes. >> 3. Run setup utility to the end. > Thanks, Andrey. I have seen

Re: bash shell gets aborts under latest Windows 10 updates as of 4/2/17

On 5/5/2017 7:30 AM, Andrey Repin wrote: You can rebase all the DLLs as follows: That's not how to do it. 1. Run rebase-trigger full 2. Shutdown all Cygwin processes. 3. Run setup utility to the end. Thanks, Andrey. I have seen those instructions, but the rebaseall command itself says

Re: bash shell gets aborts under latest Windows 10 updates as of 4/2/17

Greetings, Fran Litterio! > You can rebase all the DLLs as follows: That's not how to do it. 1. Run rebase-trigger full 2. Shutdown all Cygwin processes. 3. Run setup utility to the end. -- With best regards, Andrey Repin Friday, May 5, 2017 14:28:08 Sorry for my terrible english... --

Re: bash shell gets aborts under latest Windows 10 updates as of 4/2/17

On 4/2/2017 2:53 PM, gavin bowlby via cygwin wrote: I see the following when trying to open a Cygwin bash shell on my Win10 PC after applying updates today, 4/2/2017; I didn't see this before the latest Win10 update: 0 [main] bash 11884 child_info_fork::abort: C:\cygwin\bin\cyg

Re: bash shell gets aborts under latest Windows 10 updates as of 4/2/17

All: I reinstalled Cygwin on my Win10 PC, and now the problem has disappeared. Regards, Gavin Bowlby On Sunday, April 2, 2017 11:53 AM, gavin bowlby wrote: All: I see the following when trying to open a Cygwin bash shell on my Win10 PC after applying updates today, 4/2/2017; I didn&#

bash shell gets aborts under latest Windows 10 updates as of 4/2/17

All: I see the following when trying to open a Cygwin bash shell on my Win10 PC after applying updates today, 4/2/2017; I didn't see this before the latest Win10 update: 0 [main] bash 11884 child_info_fork::abort: C:\cygwin\bin\cygiconv-2.dll: Loaded to different address: p

Re: Bash shell script issue

On 7 September 2016 at 21:27, Eric Blake wrote: >>> project_root=$PWD >> >> Still bad. > > No, that one's good. Quotes are only REQUIRED when you want to ensure > that there is no word splitting or globbing going on, and assignment > context has neither of those. However, although the quotes are

Re: Bash shell script issue

On 2016-09-07 10:08, Kipton Moravec wrote: From: Eric Blake On 09/06/2016 05:36 PM, Kipton Moravec wrote: I this is the script: #!/bin/bash echo $PWD Insufficient quoting. This does not do the right thing if $PWD contains spaces. But not necessarily related to your problem at hand. project_ro

Re: Bash shell script issue

On 09/07/2016 12:27 PM, Andrey Repin wrote: >> 243d707b6f72656a7463725f6f6f7d74 >> 120 / t o o l s \r \n e c h o $ x \r ^^^^^ > >> Shows there is not "careless edit

Re: Bash shell script issue

On 9/7/2016 2:12 PM, wilson wrote: > >> On 2016-09-06 18:36, Kipton Moravec wrote: I am relatively new to shell scripts, but this works on >> linux and I do not know why it does not work for me in cygwin. ... What am I doing wrong or is >> this an error? Where do the carriage returns (^M) come f

Re: Bash shell script issue

On 9/7/2016 1:27 PM, Andrey Repin wrote: So "Insufficient quoting" means nothing to me. How should it be? Put quotes around any variable expansion you are not in control of. I was taking the example from a shell script I found. So I added quoting on the echo: #!/bin/bash echo "$PWD"

Re: Bash shell script issue

On 2016-09-06 18:36, Kipton Moravec wrote: I am relatively new to shell scripts, but this works on linux and I do not know why it does not work for me in cygwin. ... What am I doing wrong or is this an error? Where do the carriage returns (^M) come from, and how do I get rid of them? The (^M

Re: Bash shell script issue

On Wed, Sep 7, 2016 at 11:48 AM, Marco Atzeri wrote: >> I have been using notepad++ for my windows editor. > > \r = Carriage Return > \n = New Line / Line Feed > > so Notepad++ produced a file with CRLF as line termination and you need > to convert it with d2u. Notepad++ can also do unix line term

Re: Bash shell script issue

Greetings, Kipton Moravec! > dalkmora@DALM0048 ~/walnut/dp2b_walnut_customer_flextronics/walnut > $ od -cx testconvert1.sh > 000 # ! / b i n / b a s h \r \n e c h > 2123622f6e69622f73610d68650a6863 > 020 o $ P W D

Re: Bash shell script issue

the middle from od command. Kip - Original Message - From: Eric Blake To: cygwin@cygwin.com; kipton_mora...@yahoo.com Sent: Tuesday, September 6, 2016 8:21 PM Subject: Re: Bash shell script issue On 09/06/2016 05:36 PM, Kipton Moravec wrote: > I this is the script: > #

Re: Bash shell script issue

Greetings, Kipton Moravec! > Something else I did not know. > dalkmora@DALM0048 ~/walnut/dp2b_walnut_customer_flextronics/walnut > $ od -cx testconvert1.sh > 000 # ! / b i n / b a s h \r \n e c h > 2123622f6e69622f73610d68650a6863

Re: Bash shell script issue

please reply on the bottom On 07/09/2016 17:32, Kipton Moravec wrote: Something else I did not know. dalkmora@DALM0048 ~/walnut/dp2b_walnut_customer_flextronics/walnut $ od -cx testconvert1.sh 000 # ! / b i n / b a s h \r \n e c h 2123622f6e69622f

RE: Bash shell script issue

September-06-16 9:21 PM > To: cygwin@cygwin.com; kipton_mora...@yahoo.com > Subject: Re: Bash shell script issue > > On 09/06/2016 05:36 PM, Kipton Moravec wrote: > > > I this is the script: > > #!/bin/bash > > echo $PWD > > Insufficient quoting. This do

Re: Bash shell script issue

On 09/06/2016 05:36 PM, Kipton Moravec wrote: > I this is the script: > #!/bin/bash > echo $PWD Insufficient quoting. This does not do the right thing if $PWD contains spaces. But not necessarily related to your problem at hand. > project_root=$PWD > echo $project_root Again, insufficient

Re: pass arguments enclosed with double quotes from bash shell to windows program

On 2.4.2016 20:59, Cary Lewis wrote: I need to start acrobat from a bash shell. Acrobat needs some of its parameters to be enclosed with double quotes. This is needed to automatically open and print a pdf. When I try to do that directly from a bash shell, I can't get it to pass argu

Re: pass arguments enclosed with double quotes from bash shell to windows program

On 4/2/2016 2:19 PM, Eliot Moss wrote: > Have you tried: '"arg"' ? bash should strip the ' ' and leave the " ". > Also, what about "\"foo\"" ? > > My experiments with this suggest that they work. I tried invoked a .bat > file that echoes its first argument, and it did show "\"foo\"", but I > su

Re: pass arguments enclosed with double quotes from bash shell to windows program

On 4/2/2016 2:59 PM, Cary Lewis wrote: I need to start acrobat from a bash shell. Acrobat needs some of its parameters to be enclosed with double quotes. This is needed to automatically open and print a pdf. When I try to do that directly from a bash shell, I can't get it to pass argu

Re: pass arguments enclosed with double quotes from bash shell to windows program

On Sat, Apr 2, 2016 at 11:59 AM, Cary Lewis wrote: > I need to start acrobat from a bash shell. > > Acrobat needs some of its parameters to be enclosed with double > quotes. This is needed to automatically open and print a pdf. > > > If I try to do a \", then it passes

pass arguments enclosed with double quotes from bash shell to windows program

I need to start acrobat from a bash shell. Acrobat needs some of its parameters to be enclosed with double quotes. This is needed to automatically open and print a pdf. When I try to do that directly from a bash shell, I can't get it to pass arguments enclosed with the double quotes. It wi

Re: Weird launch Cygwin terminal bash shell error

On 2/19/2014 6:16 PM, Gerry Reno wrote: On 02/19/2014 06:10 PM, Larry Hall (Cygwin) wrote: On 2/19/2014 5:55 PM, Gerry Reno wrote: Running latest cygwin. Does anyone recognize this error? /etc/profile: fork: retry: Resource temporarily unavailable 0 [main] bash 2520 child_info_fork::abort C:

Re: Weird launch Cygwin terminal bash shell error

On 02/19/2014 06:10 PM, Larry Hall (Cygwin) wrote: > On 2/19/2014 5:55 PM, Gerry Reno wrote: >> Running latest cygwin. >> >> Does anyone recognize this error? >> >> /etc/profile: fork: retry: Resource temporarily unavailable 0 [main] bash >> 2520 child_info_fork::abort >> C:\cygwin\bin\cygiconv-2.

Re: Weird launch Cygwin terminal bash shell error

On 2/19/2014 5:55 PM, Gerry Reno wrote: Running latest cygwin. Does anyone recognize this error? /etc/profile: fork: retry: Resource temporarily unavailable 0 [main] bash 2520 child_info_fork::abort C:\cygwin\bin\cygiconv-2.dll: loaded to different address: (parent 0x49) != child(0x5A

Weird launch Cygwin terminal bash shell error

Running latest cygwin. Does anyone recognize this error? /etc/profile: fork: retry: Resource temporarily unavailable 0 [main] bash 2520 child_info_fork::abort C:\cygwin\bin\cygiconv-2.dll: loaded to different address: (parent 0x49) != child(0x5A) Every once in a while I am getting this

Re: /dev/tcp support in bash shell

On Fri, Apr 12, 2013 at 09:12:01PM -0400, Larry Hall (Cygwin) wrote: > On 4/12/2013 7:49 PM, Andrey Repin wrote: > >Greetings, Cary Lewis! > > > >>Are there any plans to add /dev/tcp/... support in Cygwin? > > > >Any use cases for that? > > Here's one: > >

Re: /dev/tcp support in bash shell

On 4/12/2013 7:49 PM, Andrey Repin wrote: Greetings, Cary Lewis! Are there any plans to add /dev/tcp/... support in Cygwin? Any use cases for that? Here's one: Bye, bye Chrome. ;-) -- Larry _

Re: /dev/tcp support in bash shell

Greetings, Cary Lewis! > Are there any plans to add /dev/tcp/... support in Cygwin? Any use cases for that? -- WBR, Andrey Repin (anrdae...@freemail.ru) 13.04.2013, <03:48> Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http:

/dev/tcp support in bash shell

Are there any plans to add /dev/tcp/... support in Cygwin? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple

Re: Bold color in "cygwin bash shell"

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

Re: Bold color in "cygwin bash shell"

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

Re: Bold color in "cygwin bash shell"

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

Re: Bold color in "cygwin bash shell"

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

Re: Bold color in "cygwin bash shell"

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

Re: Bold color in "cygwin bash shell"

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

Re: Bold color in "cygwin bash shell"

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

Bold color in "cygwin bash shell"

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

Perplexing message on bash shell start up

This is not a major problem, but I thought I’d report it for the curiosity value.   On starting a bash shell (in xterm which is probably not relevant) I got the following message: “”” cygwin warning:   MS-DOS style path detected: /cygdrive/c/Users/.../Repos/scripts/Home/.bashrc   Preferred POSIX

Re: 1.7.11: Ctrl-C does not work in bash shell (Win7)

On Tue, Apr 17, 2012 at 12:14:47AM -0700, Linda Walsh wrote: >Buchbinder, Barry (NIH/NIAID) [E] wrote: > >> Spackmann, Richard M. sent the following at Tuesday, April 03, 2012 2:18 PM >>> When I open up a cygwin command line bash shell and I notice now that >>> Ctr

Re: 1.7.11: Ctrl-C does not work in bash shell (Win7)

Buchbinder, Barry (NIH/NIAID) [E] wrote: Spackmann, Richard M. sent the following at Tuesday, April 03, 2012 2:18 PM When I open up a cygwin command line bash shell and I notice now that Ctrl-C does not exit out from the current command prompt to start a new one. Ctrl-C will however exit a

RE: 1.7.11: Ctrl-C does not work in bash shell (Win7)

Spackmann, Richard M. sent the following at Tuesday, April 03, 2012 2:18 PM >When I open up a cygwin command line bash shell and I notice now that >Ctrl-C does not exit out from the current command prompt to start a new >one. > >Ctrl-C will however exit a running process. >

Re: How to run bash shell script in cygwin?

Greetings, Marc Girod! >> Hey, why not plug our own faq while we're at it? >> >> http://cygwin.com/faq/faq.using.html#faq.using.not-found >> > One minor comment I have about point 12 in the FAQ, now that I went reading. > The following advice is given: > You should rather install sshd and use

Re: 1.7.11: Ctrl-C does not work in bash shell (Win7)

On 2012-04-03 18:17Z, Spackmann, Richard M. wrote: [...Ctrl-C handling...] > If so, when is the next cygwin bug release due out? > > I am running Windows 7 and just upgraded to 1.7.11 1.7.12 was released today, and the announcement: http://cygwin.com/ml/cygwin/2012-04/msg00082.html mentions a c

RE: How to run bash shell script in cygwin?

: http://old.nabble.com/How-to-run-bash-shell-script-in-cygwin--tp11690723p33545030.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://cygwin.com/do

Re: How to run bash shell script in cygwin?

sible? > -- View this message in context: http://old.nabble.com/How-to-run-bash-shell-script-in-cygwin--tp11690723p33544909.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.

Re: Cygwin bash shell force closes on Amazon EC2 m2.xlarge Windows 2008 instances

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

Running vssadmin in a bash shell?

Sorry, I forgot: using Windows 7 64bit but I got similar problems with Windows XP and 2003. I also tried VSHADOW.EXE to create a snapshot and I get: VSHADOW.EXE 3.0 - Volume Shadow Copy sample client. Copyright (C) 2005 Microsoft Corporation. All rights reserved. (Option: Create shadow copy se

Running vssadmin in a bash shell?

Can you run the vssadmin tool in a cygwin bash shell? It seems not. I get an error saying something like "unexpected error: the interface is unregistered" (sorry translated from Italian I currently don't have an English version of Windows at hand). Thanks, PB -- Problem repo

Re: How to run bash shell script in cygwin?

` Other people may prefer a .bashrc or similar .bash_profile files. I found this post on google when searching for executing bash files in apache. http://old.nabble.com/How-to-run-bash-shell-script-in-cygwin--to11690723.html#a11690723 Regards, Jose Torres :working: :music: myuser01 wrote: >

Bug: second bash shell can't find mount points.

CONTEXT: Running cygwin 1.7 on Windows XP cygcheck output here: http://wdv.com/cygcheck.txt BACKGROUND: Checked cygwin FAQ, Googled, etc. Have installed and updated mount points using /bin/copy-user-registry-fstab. BUG: First bash shell started using

Re: gitk kills bash shell

On Thu, Dec 23, 2010 at 08:57:25AM -0700, Jeremy Ramer wrote: >So the snapshot fixes the issue, but breaks a bunch of other cygwin >apps (like ssh server). Any idea when this fix is going to make it >into the released cygwin1.dll? Don't know what you mean by "the snapshot" but current snapshots wo

Re: gitk kills bash shell

w to go about >>>> debugging it.  I follow this process. >>>> >>>> 1) Start an rxvt bash shell >>>> 2) Go to a git repo folder >>>> 3) Start gitk >>>> gitk --all& >>>> 4) Go back to bash and press any key except

RE: 1.7.7: Open BASH Shell Here goes to wrong location

> > 'mintty -' invokes your shell as a login shell. The default > /etc/profile will cd to your home directory, but presumably you've > changed that, as that's not what you're seeing. Hence you'll end up in > whatever directory Explorer decided to start mintty, so it seems > Explorer doesn't necess

Re: 1.7.7: Open BASH Shell Here goes to wrong location

On 29 November 2010 19:11, Roe, Kevin L. wrote: > I have set up a registry entry: > > [HKEY_CLASSES_ROOT\Directory\shell\bashrxvt] > @="&Open BASH Shell Here" > [HKEY_CLASSES_ROOT\Directory\shell\bashrxvt\command] > @="C:\\cygwin\\bin\\mintty.exe -"

RE: 1.7.7: Open BASH Shell Here goes to wrong location

Well, you may have noticed that my registry entries look remarkably like what chere produces. I used "chere -i -p -c -t minty" to find my working solution (with the hoops). I built my "BASH shell here" context menu before "chere" existed. I based it on the

Re: 1.7.7: Open BASH Shell Here goes to wrong location

eating_a_folder_context_menu _entry_for_mintty > -Original Message- > Behalf Of Roe, Kevin L. > Sent: Monday, November 29, 2010 11:12 AM > Subject: 1.7.7: Open BASH Shell Here goes to wrong location > > > > I have set up a registry entry: > > [HKEY_CLASSES

RE: 1.7.7: Open BASH Shell Here goes to wrong location

I have determined that modifying the registry entry to: [HKEY_CLASSES_ROOT\Directory\shell\bashrxvt] @="&Open BASH Shell Here" [HKEY_CLASSES_ROOT\Directory\shell\bashrxvt\command] @="C:\\cygwin\\bin\\mintty.exe -e /bin/xhere /bin/bash.exe \"%L\"" [HKEY_CLASSES_R

Re: gitk kills bash shell

On Tue, Sep 28, 2010 at 9:59 PM, Christopher Faylor wrote: > On Tue, Sep 28, 2010 at 09:01:51PM +0200, Ryan Johnson wrote: >>  Jeremy Ramer said: >>> I have a very repeatable issue, but I'm not sure how to go about >>> debugging it.  I follow this process. >

  1   2   3   4   5   >