From: "Brian S. Wilson" <wilson96@comcast.net>
To: cygwin@cygwin.com
Subject: Re: shell script giving error message "No such file or directory" on cygwin 3.0.7-1
Date: Fri, 27 Sep 2019 11:42:00 -0000 [thread overview]
Message-ID: <6470ae9e-933e-8553-58b4-1c32776e22bb@comcast.net> (raw)
In-Reply-To: <1b8c44f1-3165-72f7-ee34-4277cea9f585@cs.umass.edu>
[-- Attachment #1.1.1: Type: text/plain, Size: 1662 bytes --]
On 09/27/2019 07:18, Eliot Moss wrote:
> On 9/26/2019 10:43 PM, DynV Montrealer wrote:
>> I've tried updating Cygwin a few days ago, hopefully I did it right
>> and it
>> seems its version cygwin 3.0.7-1, with its kernel version
>> 3.0.7(0.338/5/3).
>> If you did not realize it, I'm unfamiliar with Cygwin, as well as with
>> GNU/Linux.
>> I managed to do a command that give the result I wanted (I've tested it
>> successfully) ; its censored version is "sed -e 'WORKING_REGEX' -i
>> /cygdrive/REGEX_FILE_FULL_PATH". I then copy-pasted it (from Cygwin64
>> Terminal) into a file I saved with the extension .sh hoping to have that
>> work as a shell script. I then input in the terminal the uncensored
>> "./cygdrive/SHELL_SCRIPT_FULL_PATH" and got the uncensored version of
>> "-bash: ./cygdrive/SHELL_SCRIPT_FULL_PATH: No such file or
>> directory". Oh!
>> And it likely is the right path as when I do the command "ls
>> /cygdrive/SHELL_SCRIPT_FULL_PATH" it gives the output
>> "/cygdrive/SHELL_SCRIPT_FULL_PATH".
>>
>> Is there a way to make a Cygwin shell script with the command? Or do
>> I have
>> to make a text file giving instructions (copy-paste, etc.) ?
>
> I am confused by your ./cygdrive/SHELL_SCRIPT_FULL_PATH. I would think
> you should omit the leading dot. cygdrive hangs off the root of the
> cygwin
> file system. Or maybe you meant . <space> filename? That would source
> a file.
Rather than continue to recommend the old ". <space> filename" syntax
for sourcing a file, I'd recommend using the "source filename" option.
It works the same way and is less likely to be confused.
Brian Wilson
[-- Attachment #1.1.2: 0x0E6E241A34F9D685.asc --]
[-- Type: application/pgp-keys, Size: 3167 bytes --]
[-- Attachment #1.1.3: 0x0E6E241A34F9D685.asc --]
[-- Type: application/pgp-keys, Size: 3165 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2019-09-27 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 2:50 DynV Montrealer
2019-09-27 11:18 ` Brian Inglis
2019-09-27 11:42 ` Eliot Moss
2019-09-27 11:42 ` Brian S. Wilson [this message]
2019-09-27 13:37 ` Brian S. Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6470ae9e-933e-8553-58b4-1c32776e22bb@comcast.net \
--to=wilson96@comcast.net \
--cc=cygwin@cygwin.com \
--cc=wilson@ds.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).