public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: DynV Montrealer <dynvec@gmail.com>
To: Cygwin Project mailing list <cygwin@cygwin.com>
Subject: Re: Re: shell script giving error message "No such file or directory" on cygwin 3.0.7-1
Date: Sun, 29 Sep 2019 20:05:00 -0000	[thread overview]
Message-ID: <CAGYhDoOJmSasKdkXFaEL78AB6FeC+g+KjDL+7tBL6c+gASJ-tQ@mail.gmail.com> (raw)

> On Thu, Sep 26, 2019 at 10:43 PM DynV Montrealer <dynvec@gmail.com> 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.) ?
>>
>> Thank you kindly,
>> DynV

On Thu, Sep 26, 2019 at 11:38 PM Brian Inglis <
Brian.Inglis@systematicsw.ab.ca> wrote:
> Shell scripts must be in Unix text format (only \n newlines - no \r CRs)
and executable.

On Fri, Sep 27, 2019 at 07:18 AM Eliot Moss <moss@cs.umass.edu> wrote:
> 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.

By doing the 2 former recommendations, it works; I've tried them separately
and it fail doing so.

Again, thank you.
DynV

--
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

                 reply	other threads:[~2019-09-27 23:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAGYhDoOJmSasKdkXFaEL78AB6FeC+g+KjDL+7tBL6c+gASJ-tQ@mail.gmail.com \
    --to=dynvec@gmail.com \
    --cc=cygwin@cygwin.com \
    /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).