-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Remove extra line return on custom one-line formatting #496
Comments
I see several options here. One of them is to add a symbol, that means that you don't want a new line,
it is a trivial fix, and can be done in matter of minutes. It would simulate Python 2 syntax for There are several other options if this one is bad. |
I don't really know how to feel with adding a character that would represent "not a newline", since It would add the need for escaping in case you want to use this given character (e.g. the Would adding |
Other options that we have:
|
Makes sense. I would be more favorable for the python-3-style added parameter, imho. Since right now, newline's the default behaviour, maybe keep yes as default if none provided |
Or we can combine it with |
Hhm, having two options feel a bit clunky and ambigous, imho. Better stay with one, I'd say |
Currently, just to test, I've enabled
|
Works as expected. I did try using
|
It seems to be a bug, I'll check it, but could you please test the |
conky uses the |
The problem is not with curl itself, but with the programs that call it, because it is possible, that these programs just interpret |
I've fixed the bug + changed the default behavior. |
thanks! |
Right now, by fetching output using a custom one-line formatting (e.g.
http://wttr.in/Nice?format=%C+%t
), it adds a new line character at end of output, which makes it pretty annoying to use in tools like Conky, as it'll always add an empty line, e.g.${curl http://wttr.in/Nice?format=%C+%t}
.Wouldn't it be possible to avoid this newline, or make it opt-in/opt-out?
The text was updated successfully, but these errors were encountered: