Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add clarity to "The filename syntax must be only /vsistdin/" #9626

Closed
jidanni opened this issue Apr 5, 2024 · 1 comment
Closed

Add clarity to "The filename syntax must be only /vsistdin/" #9626

jidanni opened this issue Apr 5, 2024 · 1 comment

Comments

@jidanni
Copy link
Contributor

jidanni commented Apr 5, 2024

Feature description

In https://gdal.org/user/virtual_file_systems.html

we see

The filename syntax must be only /vsistdin/.

It would be great if it instead said

The filename syntax must be only /vsistdin/, not e.g.,
/vsistdin/path/to/f.csv .

But maybe that's not what it is trying to say. Hard to tell! Thus I
have no PR to submit.

And, a little further down it goes on to say,

The "/vsistdin?buffer_limit=value" syntax can also be used.

which rather undermines what it first said.

Later in the page it would also be nice if

The filename syntax must be only /vsistdout/.

said

The filename syntax must be only /vsistdout/. Not e.g., .....

@rouault
Copy link
Member

rouault commented Apr 5, 2024

The filename syntax must be only /vsistdin/, not e.g.,
/vsistdin/path/to/f.csv .

yes, that's what it is meant. But that should be kind of obvious for anyone a bit familiar with the concept of standard input.

And, a little further down it goes on to say, The "/vsistdin?buffer_limit=value" syntax can also be used.

That's a later addition to the original "/vsistdin/" only syntax. This is a rather advanced mode, that said

Feel free to submit an enhancement reflecting that if you wish.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants