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 installation. >>> Q3 - at 1/8 the size of bash and sh,

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 reach of dash. Sh

Re: bash shell script: recently running, now failing

Coming from an enterprise and supercomputing background, we were able to control what shell was available, so bashisms weren't a problem any more than dashisms, fishisms, kornisms, perl or python versionisms, etc, might be. But, when I was in a commercial environment, everything - shell, perl, C,

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 the single character null \x00

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 > reach of dash. > Should the edit (dash

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 shell script i.e. first line > >

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 character null \x00 showing up in some editor

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 the recent past, > so I don't kno

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. This used to work in the rec

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\cygiconv-2

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't s

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: Cygwin git - Configuration Problem? [was Re: BASH Shell - Configuration Problem?]

On Tue, Dec 15, 2009 at 02:01, Eric Blake wrote: > The upstream git list may be a better list to complain at, since they are > the folks that implemented whitespace munging in the first place. Ok, I posed a question or two there: http://thread.gmane.org/gmane.comp.version-control.git/135305 I'm

Re: Cygwin git - Configuration Problem? [was Re: BASH Shell - Configuration Problem?]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to David Antliff on 12/13/2009 9:46 PM: > For the record, core.autocrlf=true on Cygwin is an absolute PITA ;) I personally haven't ever taken time to notice whether that is the upstream default (if so, it is wrong, IMNSHO), because I have a

Re: Cygwin git - Configuration Problem? [was Re: BASH Shell - Configuration Problem?]

On Mon, Dec 14, 2009 at 04:53, Dave Korn wrote: > David Antliff wrote: > >> I've set this in Cygwin.bat and used it successfully to allow users to >> run bash scripts that are in DOS text-file format. This turns out to >> be really important when using git with core.autocrlf=true... > >  Say, do y

Cygwin git - Configuration Problem? [was Re: BASH Shell - Configuration Problem?]

David Antliff wrote: > I've set this in Cygwin.bat and used it successfully to allow users to > run bash scripts that are in DOS text-file format. This turns out to > be really important when using git with core.autocrlf=true... Say, do you mean "This turns out to be really important when using

Re: BASH Shell - Configuration Problem?

On Sat, Dec 12, 2009 at 15:49, Gary Johnson wrote: > On 2009-12-11, rgc3679 wrote: >> Any ideas? > > Thanks for all the details.  That really helps.  It looks to me as > though your script file has CR-LF (DOS) line endings rather than LF > (Unix) line endings.  The current version of Cygwin's bash

Re: BASH Shell - Configuration Problem?

On 2009-12-11, rgc3679 wrote: > I haven't used cygwin or bash in 5 years, but I need to write a bash script > for my ISP to test JavaMail. I can't get simple things to work, so I'm > wondering if maybe I have a bash shell config issue. I did update cygwin to > the latest. [...] > Notice how the e

Re: bash shell interface broken after install on Vista

Christopher Faylor wrote: Did you try cygcheck ./bash.exe ? Good point. C:\cygwin\bin>cygcheck ./bash.exe .\bash.exe .\cygwin1.dll C:\Windows\system32\ADVAPI32.DLL C:\Windows\system32\ntdll.dll C:\Windows\system32\KERNEL32.dll C:\Windows\system32\RPCRT4.dll C:\Win

Re: bash shell interface broken after install on Vista

On Sun, Aug 03, 2008 at 08:24:00PM -0700, Barry Gold wrote: > Larry Hall (Cygwin) wrote: >> Barry Gold wrote: >>> Christopher Faylor wrote: Commands which exit silently are usually caused by missing DLLs. "cygcheck /bin/ls.exe" would tell you which DLL was missing and you could

Re: bash shell interface broken after install on Vista

Barry Gold wrote: Larry Hall (Cygwin) wrote: Barry Gold wrote: Christopher Faylor wrote: Commands which exit silently are usually caused by missing DLLs. "cygcheck /bin/ls.exe" would tell you which DLL was missing and you could install the missing packages. I tried that. But cygcheck d

Re: bash shell interface broken after install on Vista

Tim McDaniel wrote: > The original problem report mentioned it hanging during the download > or install, I forget which. I wondered whether it might have been > some odd networking problem with that particular mirror. (I've had > odd networking problems in the past, even in Linux.) It's also an

Re: bash shell interface broken after install on Vista

Larry Hall (Cygwin) wrote: Barry Gold wrote: Christopher Faylor wrote: Commands which exit silently are usually caused by missing DLLs. "cygcheck /bin/ls.exe" would tell you which DLL was missing and you could install the missing packages. I tried that. But cygcheck doesn't work either,

Re: bash shell interface broken after install on Vista

On Sun, 3 Aug 2008, Christopher Faylor <[EMAIL PROTECTED]> wrote: On Sun, Aug 03, 2008 at 02:36:49PM -0500, [EMAIL PROTECTED] wrote: Since you just installed Cygwin and didn't configure it much, have you considered just uninstalling and reinstalling from a new mirror? The mirror checking softw

Re: bash shell interface broken after install on Vista

Barry Gold wrote: Larry Hall (Cygwin) wrote: 'cygcheck' is a Win32 app which doesn't rely on 'cygwin1.dll' or any of Cygwin's added features. If it won't work, then something in your system is inhibiting it. Perhaps you have ? Wonderful. Norton AV is on t

Re: bash shell interface broken after install on Vista

Larry Hall (Cygwin) wrote: 'cygcheck' is a Win32 app which doesn't rely on 'cygwin1.dll' or any of Cygwin's added features. If it won't work, then something in your system is inhibiting it. Perhaps you have ? Wonderful. Norton AV is on the BLODA. Well...

Re: bash shell interface broken after install on Vista

On 08/03/2008, Larry Hall (Cygwin) wrote: That gain suggests BLODA. And 00ash.sh should come before 00bash.sh. again -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd.

Re: bash shell interface broken after install on Vista

Barry Gold wrote: Larry Hall (Cygwin) wrote: Barry Gold wrote: Christopher Faylor wrote: Commands which exit silently are usually caused by missing DLLs. "cygcheck /bin/ls.exe" would tell you which DLL was missing and you could install the missing packages. I tried that. But cygcheck d

Re: bash shell interface broken after install on Vista

Barry Gold wrote: Larry Hall (Cygwin) wrote: Barry Gold wrote: 'cygcheck' is a Win32 app which doesn't rely on 'cygwin1.dll' or any of Cygwin's added features. If it won't work, then something in your system is inhibiting it. Perhaps you have ? I have:

Re: bash shell interface broken after install on Vista

Larry Hall (Cygwin) wrote: Barry Gold wrote: Christopher Faylor wrote: Commands which exit silently are usually caused by missing DLLs. "cygcheck /bin/ls.exe" would tell you which DLL was missing and you could install the missing packages. I tried that. But cygcheck doesn't work either,

Re: bash shell interface broken after install on Vista

Larry Hall (Cygwin) wrote: Barry Gold wrote: 'cygcheck' is a Win32 app which doesn't rely on 'cygwin1.dll' or any of Cygwin's added features. If it won't work, then something in your system is inhibiting it. Perhaps you have ? I have: 1. Firefox 2. Thun

Re: bash shell interface broken after install on Vista

Barry Gold wrote: Christopher Faylor wrote: Commands which exit silently are usually caused by missing DLLs. "cygcheck /bin/ls.exe" would tell you which DLL was missing and you could install the missing packages. I tried that. But cygcheck doesn't work either, for the same reason. 'cygch

Re: bash shell interface broken after install on Vista

Christopher Faylor wrote: Commands which exit silently are usually caused by missing DLLs. "cygcheck /bin/ls.exe" would tell you which DLL was missing and you could install the missing packages. I tried that. But cygcheck doesn't work either, for the same reason. This is after a third down

Re: bash shell interface broken after install on Vista

On Sun, Aug 03, 2008 at 02:36:49PM -0500, [EMAIL PROTECTED] wrote: >On Sun, 3 Aug 2008, Barry Gold <[EMAIL PROTECTED]> wrote: >> 1. Nearly all commands appear to complete without doing anything. >> This includes "ls", "cat", "vi". >> The following commands work properly: >> echo >> true >> false

Re: bash shell interface broken after install on Vista

On Sun, 3 Aug 2008, Barry Gold <[EMAIL PROTECTED]> wrote: > 1. Nearly all commands appear to complete without doing anything. > This includes "ls", "cat", "vi". > The following commands work properly: > echo > true > false ($? == 1) > dirs > if...then.fi > test That I can address: they are sh

Re: bash shell globbing not working anymore

On 10/04/2006, Andy Telford wrote: I guess the current bash doesn't jive with cygwin 1.5.19(0.150/4/2) 2006-01-16 15:01 i686 Cygwin, Yes, I'm quite sure bash doesn't speak jive. ;-) -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 89

RE: bash shell globbing not working anymore

On 04 October 2006 18:41, Andy Telford wrote: > Eureka! I checked the cygcheck output and noticed that my cygwin dll was > old even though "setup" thought I was up to date. Maybe a previous cygwin > update failed to complete properly? I reinstalled the base cygwin package > using setup and now

Re: bash shell globbing not working anymore

rrent bash doesn't jive with cygwin 1.5.19(0.150/4/2) 2006-01-16 15:01 i686 Cygwin, Thanks everyone, Andrew - Original Message From: Dave Korn <[EMAIL PROTECTED]> To: cygwin mailing list Sent: Wednesday, October 4, 2006 1:13:22 PM Subject: RE: bash shell globbing not w

RE: bash shell globbing not working anymore

On 04 October 2006 18:08, Andy Telford wrote: > Nope. The directory was not empty, so * should have been expanded by the > shell according to the bash "pathname expansion" rules. I included the > SHELLOPTS variable in the first email to show that noglob is not set. > > $ mkdir newdir > $ cd ne

Re: bash shell globbing not working anymore

Nope. The directory was not empty, so * should have been expanded by the shell according to the bash "pathname expansion" rules. I included the SHELLOPTS variable in the first email to show that noglob is not set. $ mkdir newdir $ cd newdir $ touch newfile $ ls newfile $ ls * ls: *: No such fil

RE: bash shell globbing not working anymore

On 04 October 2006 16:47, Andy Telford wrote: > Has any experienced this? > > - "ls" works but "ls *" returns "ls: *: No such file or directory" > - same if I just use the shell builtin "echo *" just returns "*" You are in an empty directory. There is nothing for the '*' to match. As glob

Re: bash shell globbing not working anymore

Andy Telford wrote: > Has any experienced this? > > - "ls" works but "ls *" returns "ls: *: No such file or directory" > - same if I just use the shell builtin "echo *" just returns "*" I experience this every time when I issue those commands with an empty directory as cwd. That's simply the way

Re: bash shell

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to drkzs on 2/27/2006 11:41 AM: > It's ok too, i've just one "problem", the cygwin bash is now without any > colour (before it was) for example to list the files with ls, there is no > colours... > And sometimes it opens in the ms invite comm

Re: bash shell not responding

* Wayne Willcox (2005-11-15 19:57 +0100) You know that top-posting is evil? > What do you mean by open a batch file? He wrote "the batch file". Probably the cygwin.bat. "Make people's life more fun by letting them guess" is his motto... -- Unsubscribe info: http://cygwin.com/ml/#unsubscri

Re: bash shell not responding

Alexander wrote: > curiously, it actually worked once a > little while ago, i was able to execute commands and everything, and > now is back to not responding, it just opens a blank command prompt > window, the $ prompt doesn't appear, and it's unresponsive. > > What I mean by the batch file is t

Re: bash shell not responding

curiously, it actually worked once a little while ago, i was able to execute commands and everything, and now is back to not responding, it just opens a blank command prompt window, the $ prompt doesn't appear, and it's unresponsive. What I mean by the batch file is the shortcut in the root direct

Re: bash shell not responding

Alexander wrote: > alright... i admit it, i'm a hopeless newbie, but this is really frustrating > me... I've succesfully installed cygwin and the supporting files, but when I > try > to open the batch file, it opens a single cmd-like window that doesn't respond > to anything. is it possible that

Re: bash shell not responding

What do you mean by open a batch file? You trying to edit it and if so what editor are you using? Your steps for reproducing the problem would be helpful. On Tue, Nov 15, 2005 at 06:34:54PM +, Alexander wrote: > alright... i admit it, i'm a hopeless newbie, but this is really frustrating > m

Re: bash shell just flash and disappear

On Mon, Oct 04, 2004 at 05:02:24PM +0200, [EMAIL PROTECTED] wrote: >I think you try to execute direct bash.exe without the interactive >parameter, like proposed in the cygwin.bat : bash --login -i -i >indicate "echo a prompt and wait for command" -login "indicate, first >time bash in executed, pars

Re: bash shell just flash and disappear

I think you try to execute direct bash.exe without the interactive parameter, like proposed in the cygwin.bat : bash --login -i -i indicate "echo a prompt and wait for command" -login "indicate, first time bash in executed, parse the .profile"

Re: Bash shell on Zip disk/ CDROM

On Thu, 15 Apr 2004, Leonard Williams wrote: > Intro--I'm not much of computer wiz--I just follow instructions (a > little like the dumb box itself, I guess!). I could not find relevant > answers in the cygwin archives. > > I have been using the bash shell for compiling programs in c > si

RE: Bash shell

Hmm... reply/follow-up-to: is not set to cygwin ML... :-7 May I guess that you occasionally get personal mail? ;-) > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf > Of Randall R Schulz -- 8< -- here and there... > I don't know Pico, > but I gave it a try (running in a Cygwin cons

RE: Bash shell

Hannu, At 08:05 2003-02-16, Hannu E K Nevalainen (garbage mail) wrote: >> I use the bash shell a LOT and was wondering how do I get it so that I can >> copy and paste something from a windows window (such as an IP address) into >> the bash shell window. For example I want to use the whois fu

RE: Bash shell

I have been very happy with the cut and paste and other features with RXVT. Its been a while since I set mine up, but I got the directions from the forum, a search should turn them up. Its cool having the same feel of the Unix three button mouse on my PCs. Wayne -- Unsubscribe info: http

RE: Bash shell

> > I use the bash shell a LOT and was wondering how do I get it so that I can > > copy and paste something from a windows window (such as an IP address) into > > the bash shell window. For example I want to use the whois functionality of > > the bash shell for an IP I have in a windows window. I

Re: Bash shell

Thorsten, At 13:01 2003-02-14, Thorsten Kampe wrote: * Randall R Schulz (03-02-14 18:28 +0100) > I think we're really getting the tag-team meanness down to a fine art, > aren't we? > > Or is it "good cop / bad cop?" I don't see your point. I stated that there is no Linux nor Cygwin nor Windows

Re: Bash shell

* Randall R Schulz (03-02-14 18:28 +0100) > I think we're really getting the tag-team meanness down to a fine art, > aren't we? > > Or is it "good cop / bad cop?" I don't see your point. I stated that there is no Linux nor Cygwin nor Windows nor BSD bash. It's just GNU bash and if you have a "

Re: Bash shell

> Elfyn McBratney wrote: > >>Randall R Schulz wrote: > >> > >>>Hello, Fellow Curmudgeons, > >>> > >>>I think we're really getting the tag-team meanness down to a fine art, > >>>aren't we? > >>> > >>>Or is it "good cop / bad cop?" > >>> > >>>It has recently come to my attention that some people thin

Re: bash shell

[EMAIL PROTECTED] wrote: [EMAIL PROTECTED] on 02/14/2003 03:14:39 PM To: [EMAIL PROTECTED] cc:(bcc: Fred Smith/Computrition) Subject: cygwin Digest 14 Feb 2003 20:14:39 - Issue 2563 It has recently come to my attention that some people think the Cygwin list is exceptionally un

Re: Bash shell

Elfyn McBratney wrote: Randall R Schulz wrote: Hello, Fellow Curmudgeons, I think we're really getting the tag-team meanness down to a fine art, aren't we? Or is it "good cop / bad cop?" It has recently come to my attention that some people think the Cygwin list is exceptionally unfriendly to

Re: bash shell

[EMAIL PROTECTED] on 02/14/2003 03:14:39 PM To: [EMAIL PROTECTED] cc:(bcc: Fred Smith/Computrition) Subject: cygwin Digest 14 Feb 2003 20:14:39 - Issue 2563 > > It has recently come to my attention that some people think the Cygwin > > list is exceptionally unfriendly to the uni

Re: Bash shell

> Randall R Schulz wrote: > > Hello, Fellow Curmudgeons, > > > > I think we're really getting the tag-team meanness down to a fine art, > > aren't we? > > > > Or is it "good cop / bad cop?" > > > > It has recently come to my attention that some people think the Cygwin > > list is exceptionally unfr

Re: Bash shell

Randall R Schulz wrote: Hello, Fellow Curmudgeons, I think we're really getting the tag-team meanness down to a fine art, aren't we? Or is it "good cop / bad cop?" It has recently come to my attention that some people think the Cygwin list is exceptionally unfriendly to the uninitiated. Of co

Re: Bash shell

Hello, Fellow Curmudgeons, I think we're really getting the tag-team meanness down to a fine art, aren't we? Or is it "good cop / bad cop?" It has recently come to my attention that some people think the Cygwin list is exceptionally unfriendly to the uninitiated. Of course, I'd just like to t

Re: Bash shell

* Tom Dager (03-02-14 17:37 +0100) > I am VERY new to Cygwin, though not to Linux. bash has nothing to do with Linux, it's a GNU thing. > I [...] was wondering how do I get it so that I can copy and paste something > from a windows window [...] into the bash shell window. This is a FAQ and has

Re: Bash shell

Tom, Welcome. If you have a console window as produced by launching the desktop or Start Menu Cygwin icon (as opposed to an RXVT terminal emulator window), then access the window's properties dialog by activating the window menu from the icon in the upper-left of the window's title bar and c

Re: Bash shell

Tom Dager wrote: Hello everyone! I am VERY new to Cygwin, though not to Linux. I use the bash shell a LOT and was wondering how do I get it so that I can copy and paste something from a windows window (such as an IP address) into the bash shell window. For example I want to use the whois functi

Re: Bash shell extension ?

Well, I don't use Network Neighborhood, so this problem doesn't affect me much .. However, I have been helping friends set up this extension as well, and I'm sure they'd like for this problem to be addressed .. If someone manages to write an executable that handles all possible cases, please let m

Re: Bash shell extension ?

Andrew DeFaria wrote: > Donald MacVicar wrote: > surely you could just have @="rxvt -ls -e bash -c \"cd '%1'; exec bash --login\"" and then all the startup scripts would be run properly? >>> >>> Nope! Because --login runs /etc/profile and /etc/profile cd's to $HOME! >> >> Realis

Re: Bash shell extension ?

"Adam" <[EMAIL PROTECTED]> wrote; > Ah-hah! This reg file works perfectly! Thanks Sam! LOL. Glad I could help. Unfortunately there are still problems. First off, you don't get the menu item for network shares in the Network Neighbourhood so you can't get a bash prompt in the root of a share.

Re: Bash shell extension ?

I tried that, it didn't work .. As stupid as it sounds, Windows doesn't seem to send the full path to the program unless you specify the FULL PATH to the bash.exe executable .. This is the only thing that I changed, and this is what makes it work properly .. (Thanks Sam for the advice) .. -Adam

Re: Bash shell extension ?

Ignore this, Sam already sent a .reg file to the list that works perfectly :) -Adam *** REPLY SEPARATOR *** On 4/12/2002 at 5:13 PM Adam wrote: >Thanks for the tips Andrew .. >The one thing I have yet to figure out is a way to prevent the long folder >names from being truncate

Re: Bash shell extension ?

Ah-hah! This reg file works perfectly! Thanks Sam! -Adam *** REPLY SEPARATOR *** On 4/12/2002 at 10:02 PM Sam Edge wrote: >"Adam" <[EMAIL PROTECTED]> wrote; > > >> [HKEY_CLASSES_ROOT\Directory\shell\Bash\command] >> @="bash.exe -c 'cd \"%1\"; exec /bin/bash.exe'" > >As I said,

Re: Bash shell extension ?

> Thanks for the tips Andrew .. > The one thing I have yet to figure out is a way to prevent the long folder > names from being truncated (eg, Progra~1) .. Any ideas on this? try using cygpath? > -Adam -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: htt

Re: Bash shell extension ?

Thanks for the tips Andrew .. The one thing I have yet to figure out is a way to prevent the long folder names from being truncated (eg, Progra~1) .. Any ideas on this? -Adam *** REPLY SEPARATOR *** On 4/12/2002 at 9:34 AM Andrew DeFaria wrote: >Sam Edge wrote: > >> [HKEY_CLAS

Re: Bash shell extension ?

"Adam" <[EMAIL PROTECTED]> wrote; > [HKEY_CLASSES_ROOT\Directory\shell\Bash\command] > @="bash.exe -c 'cd \"%1\"; exec /bin/bash.exe'" As I said, if you use double-quotes around the %1 then it won't work for Drive because the trailing backslash will escape the closing quote. You may also get o

Not Delivered: RE: Bash shell extension ?

An error occurred sending a message to: [EMAIL PROTECTED] Relay host reported error: (127.0.0.1) 550 ... Recipient is unknown Original Message Follows: = Reporting-MTA: dns; avacado.atomice.net Remote-MTA: dns; 127.0.0.1 Final-Recipient: rfc822;[EMAIL PROTECTED] Actio

Re: Bash shell extension ?

Donald MacVicar wrote: >>> surely you could just have @="rxvt -ls -e bash -c \"cd '%1'; exec >>> bash --login\"" and then all the startup scripts would be run properly? >> >> Nope! Because --login runs /etc/profile and /etc/profile cd's to $HOME! > > > Realised that about 10 secs after I sent t

Re: Bash shell extension ?

Andrew DeFaria wrote: > Donald MacVicar wrote: > >> Andrew DeFaria wrote: >> >>> Sam Edge wrote: >>> [HKEY_CLASSES_ROOT\Directory\shell\BashHere] @="&Bash Prompt Here" [HKEY_CLASSES_ROOT\Directory\shell\BashHere\command] @="c:\\cygwin\\bin\\bash.exe -c \"cd '%1' ; exec /bin/ba

Re: Bash shell extension ?

Donald MacVicar wrote: > Andrew DeFaria wrote: > >> Sam Edge wrote: >> >>> [HKEY_CLASSES_ROOT\Directory\shell\BashHere] >>> @="&Bash Prompt Here" >>> [HKEY_CLASSES_ROOT\Directory\shell\BashHere\command] >>> @="c:\\cygwin\\bin\\bash.exe -c \"cd '%1' ; exec /bin/bash\"" >>> [HKEY_CLASSES_ROOT\Drive

Re: Bash shell extension ?

Andrew DeFaria wrote: > Sam Edge wrote: > >> [HKEY_CLASSES_ROOT\Directory\shell\BashHere] >> @="&Bash Prompt Here" >> [HKEY_CLASSES_ROOT\Directory\shell\BashHere\command] >> @="c:\\cygwin\\bin\\bash.exe -c \"cd '%1' ; exec /bin/bash\"" >> [HKEY_CLASSES_ROOT\Drive\shell\BashHere] >> @="&Bash Promp

Re: Bash shell extension ?

Sam Edge wrote: > [HKEY_CLASSES_ROOT\Directory\shell\BashHere] > @="&Bash Prompt Here" > [HKEY_CLASSES_ROOT\Directory\shell\BashHere\command] > @="c:\\cygwin\\bin\\bash.exe -c \"cd '%1' ; exec /bin/bash\"" > [HKEY_CLASSES_ROOT\Drive\shell\BashHere] > @="&Bash Prompt Here" > [HKEY_CLASSES_ROOT\Dri

Re: Bash shell extension ?

Can you give an example batch file? (This topic is going to be made an FAQ once we've completed it, so the more info the better) .. -Adam *** REPLY SEPARATOR *** On 4/12/2002 at 11:49 AM Chris January wrote: >> Ok, I have made the changes you suggested, but there are some prob

Re: Bash shell extension ?

In case you need to know, this is what my registry currently looks like this: [HKEY_CLASSES_ROOT\Directory\shell\Bash] @="Bash Prompt" [HKEY_CLASSES_ROOT\Directory\shell\Bash\command] @="bash.exe -c 'cd \"%1\"; exec /bin/bash.exe'" Using this it works fine, with the exception of grossly truncati

  1   2   >