Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: file directory problem in curl command
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Jeremy Nicoll via curl-users <curl-users_at_cool.haxx.se>
Date: Tue, 24 Aug 2021 11:11:52 +0100
On Mon, 23 Aug 2021, at 23:05, Bill Mercer via curl-users wrote:
>
> > > I was referring to this...
> > > "E:/NC Voter Files/address/NCaddresses1.csv"
> > >
> > > The error message references an invalid path, and that's an
> > > invalid path.
> > Why do you say that? Why then does this command work (in a
> > cmd terminal window under Win 8.1):
> I'm not here to debate.
So what are you here for? Just to hand-down pronouncements?
Would it not be better, if that's the case, if what you said was
unambiguously correct?
> I responded to that, and now you're presenting evidence to prove
> me wrong.
I don't think it's as clear cut as that. Whether curl regards a Windows
filepath as being incorrect if it has forward slashes in it might be partly
down to how curl interacts with Windows; I don't know. The point I was
making is that nearly everybody is unaware that at least some parts of
Windows support forward slashes in file paths.
I thought it was information that anyone unfamiliar with Windows' file
handling might not know, and might like to know.
> How is any of this even remotely helpful to Doug Hess?
Well it casts doubt on your statement that his supplied parameter
is invalid, doesn't it?
Date: Tue, 24 Aug 2021 11:11:52 +0100
On Mon, 23 Aug 2021, at 23:05, Bill Mercer via curl-users wrote:
>
> > > I was referring to this...
> > > "E:/NC Voter Files/address/NCaddresses1.csv"
> > >
> > > The error message references an invalid path, and that's an
> > > invalid path.
> > Why do you say that? Why then does this command work (in a
> > cmd terminal window under Win 8.1):
> I'm not here to debate.
So what are you here for? Just to hand-down pronouncements?
Would it not be better, if that's the case, if what you said was
unambiguously correct?
> I responded to that, and now you're presenting evidence to prove
> me wrong.
I don't think it's as clear cut as that. Whether curl regards a Windows
filepath as being incorrect if it has forward slashes in it might be partly
down to how curl interacts with Windows; I don't know. The point I was
making is that nearly everybody is unaware that at least some parts of
Windows support forward slashes in file paths.
I thought it was information that anyone unfamiliar with Windows' file
handling might not know, and might like to know.
> How is any of this even remotely helpful to Doug Hess?
Well it casts doubt on your statement that his supplied parameter
is invalid, doesn't it?
-- Jeremy Nicoll - my opinions are my own. ----------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-users Etiquette: https://curl.haxx.se/mail/etiquette.htmlReceived on 2021-08-24