-
Notifications
You must be signed in to change notification settings - Fork 266
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
Better output on first start #136
base: master
Are you sure you want to change the base?
Conversation
Adding last changes
What do you mean by "not properly displayed"? it works just fine on Fedora 24:
Second, please rebase your pull request to remove the merge commit. |
oh ok, I've not the same behavior on my side, mine is :
but using
Works correctly. With my PR, the output of
and for
I'll just add an empty line before I'm running Linux Mate 18 Sarah (Based on Ubuntu 16.04). |
Just to mark a proper separation before the execution of the main process
I'm reading about the rebase, please, give me some time to understand how to do what you've requested. I've tested this on my repository Feel free to take the code on your side and delete this pull request. I'm not sure I can do what you've requested, I'm still trying to learn it and do it correctly... Thank you very much for your help |
|
we could just redirect the echo output to stderr, then it won't be cached and will show up together with git output, add regarding rebase:
In general, I would suggest not to develop on |
Thanks @tomato42 for your help. I've created a new branch named |
Well... very lately, I'm back. I've forked again this repository and will do I've tested your suggestion to use First run
Second run
|
I just got bitten by this today, since cscan outputs extra characters on first run even in JSON mode. I'm very much in favor of removing the extra verbosity, particularly when the user asked for JSON only. |
for the script to not output stuff in json mode, the shell script would have to parse the command line options |
Ok, so should I close this pull request then create a one based on the proper changes I've made with the help of @tomato42 ? |
no, it's fine to edit the commits and then update the pull request |
Hi, I know we've already discussed about this earlier but when I tested again, I've found that the text was not properly displayed (I mean not as I wanted it to be) and I think this PR is better than the previous one.