From: Chris DiTrani <cditrani@livedata.com>
To: calin <calin_cosma@mymail.ro>
Cc: linux-admin@vger.kernel.org
Subject: Re: Stupid spaces
Date: Mon, 19 Jul 2004 09:56:14 -0400 [thread overview]
Message-ID: <1090245374.17698.49.camel@chris.livedata.com> (raw)
In-Reply-To: <1090243761.12913.8.camel@LinuxMobile>
file_path='test foo'
cd "$file_path"
On Mon, 2004-07-19 at 09:29, calin wrote:
> Hello all.
>
> I know the following question is a dumb one, but I've tried to make a
> script working and I'm stuck.
>
> I'll try to isolate the problem as follows.
>
> I have a script which at some moment during the execution, needs to cd.
> So I assumed that the following would work:
>
>
> file_path='"/some/where/Test Folder/"'
> echo "$file_path"
> cd "$file_path"
>
> But surprise: it didn't. Every time I try to run it it gives me
> something like:
>
>
> $ ./cding.sh
> "/some/where/Test Folder/"
> ./cding.sh: line 5: cd: "/some/where/Test Folder/": No such file or
> directory
> $
>
> although the Test Folder exist, is in the right path (/some/where/Test
> Folder) and it's permissions are 777.
>
> Any idea?
>
> TIA
>
> Calin Cosma
>
>
>
> ---------------------------------------------------------------
> Incearca acum noul sistem de dating oferit de portalul acasa.ro
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2004-07-19 13:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 13:29 Stupid spaces calin
2004-07-19 13:56 ` Chris DiTrani [this message]
2004-07-19 14:59 ` calin
2004-07-19 14:45 ` Scott Taylor
2004-07-19 14:52 ` Scott Taylor
2004-07-20 17:48 ` scohen
2004-07-20 18:22 ` Adam Lang
2004-07-20 17:55 ` scohen
2004-07-20 18:20 ` Chris DiTrani
2004-07-20 18:37 ` Adam Lang
2004-07-21 2:28 ` Glynn Clements
2004-07-21 7:11 ` calin
-- strict thread matches above, loose matches on Subject: below --
2004-02-13 19:13 urgrue
2004-02-12 21:08 Scott Taylor
2004-02-12 21:23 ` Alok K. Dhir
2004-02-12 22:19 ` Scott Taylor
2004-02-12 21:39 ` Yu Chen
2004-02-12 22:18 ` Scott Taylor
2004-02-13 2:15 ` rich+ml
2004-02-13 4:07 ` Emiliano Castagnari
2004-02-13 16:56 ` Scott Taylor
2004-02-13 6:51 ` Agus Budy Wuysang
2004-02-13 17:15 ` Scott Taylor
[not found] ` <Pine.LNX.4.44.0402121811240.3031-100000@deadrat.localdomai n>
2004-02-13 16:33 ` Scott Taylor
2004-02-13 17:26 ` rich+ml
[not found] ` <Pine.LNX.4.44.0402130907370.3031-100000@deadrat.localdomai n>
2004-02-13 17:33 ` Scott Taylor
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=1090245374.17698.49.camel@chris.livedata.com \
--to=cditrani@livedata.com \
--cc=calin_cosma@mymail.ro \
--cc=linux-admin@vger.kernel.org \
/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 NNTP newsgroup(s).