Skip to content
This repository was archived by the owner on Sep 26, 2023. It is now read-only.

If values contain spaces, treat them as values#38

Open
sethfitz wants to merge 1 commit intoharthur:masterfrom
sethfitz:options-with-spaces
Open

If values contain spaces, treat them as values#38
sethfitz wants to merge 1 commit intoharthur:masterfrom
sethfitz:options-with-spaces

Conversation

@sethfitz
Copy link
Copy Markdown

@sethfitz sethfitz commented May 27, 2014

Option names should never contain spaces; values might.

This (partially) works around #37, but still prevents individual negative values from being treated as values.

@sethfitz
If values contain spaces, treat them as values
39a68fd 
Option names should never contain spaces; values might.

This (partially) works around harthur#37, but still prevents individual
negative values from being treated as values.
@sethfitz
Copy link
Copy Markdown
Author

sethfitz commented Jun 5, 2014

Thoughts?

@harthur
Copy link
Copy Markdown
Owner

harthur commented Sep 19, 2014

You can use ' single quotes like --name 'foo bar'. I don't think I've seen behavior like what you're suggesting, but welcome to counterexamples. I want to stick to what would be familiar to people.

@eush77 eush77 mentioned this pull request Sep 21, 2014
Open
@sethfitz
Copy link
Copy Markdown
Author

sethfitz commented Oct 28, 2014

ogr2ogr is one the tools I was modeling behavior on (yes, it has weird options, but I wouldn't know how else to handle bounding box arguments).

E.g.

-spat xmin ymin xmax ymax

I've been using quotes in the meantime. Feel free to close this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@sethfitz @harthur