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

Should \n be added to short output? #309

Closed
Odizinne opened this issue Oct 28, 2023 · 2 comments
Closed

Should \n be added to short output? #309

Odizinne opened this issue Oct 28, 2023 · 2 comments
Labels

Comments

@Odizinne
Copy link
Contributor

Description

Hello, not sure if this is wanted or not but:

flora@pop-os:~$ headsetcontrol -b -c
-2flora@pop-os:~$ 

This is what i get when shortening output.
Is this something intended?

I would expect something like this:

flora@pop-os:~$ headsetcontrol -b -c
-2
flora@pop-os:~$ 

On which OS does the problem happen?

Linux

@Odizinne Odizinne added the bug label Oct 28, 2023
@Sapd
Copy link
Owner

Sapd commented Oct 29, 2023

It probably was done this way to make it easier to directly parse. But I agree with you, normally a Linux command should always end with \n.

However, I wouldn't change it due to backwards compatibility. Also because -c will be probably deprecated in the future in favour of #271 (Feel free to participate in the discussion)

@Sapd
Copy link
Owner

Sapd commented Apr 12, 2024

Closed because short output is now deprecated in favour of JSON/YAML output

@Sapd Sapd closed this as completed Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants