We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
hello, when I log into a log file I have a problem with special char at the begining.
How to remove them ?
===== ============================== ======= ======= ====== ====== ===== PID Name CurHeap MaxHeap CurRAM MaxRAM %_CPU ===== ============================== ======= ======= ====== ====== ===== 10724 org.eclipse.osgi_3.9.1.v201401 36 36 60 60 0 ^[[1A10724 org.eclipse.osgi_3.9.1.v201401 36 36 60 60 0 ^[[1A10724 org.eclipse.osgi_3.9.1.v201401 36 36 60 60 0 ^[[1A10724 org.eclipse.osgi_3.9.1.v201401 36 36 60 60 0 ^[[1A10724 org.eclipse.osgi_3.9.1.v201401 36 36 60 60 0 ^[[1A10724 org.eclipse.osgi_3.9.1.v201401 36 36 60 60 0
best bruno
The text was updated successfully, but these errors were encountered:
That special char at beginning is because of tput.
tput
To solve this, we can have an option to write directly to a file and do not write tput in that. This will fix the illegal char.
Sorry, something went wrong.
No branches or pull requests
hello, when I log into a log file I have a problem with special char at the begining.
How to remove them ?
===== ============================== ======= ======= ====== ====== =====
PID Name CurHeap MaxHeap CurRAM MaxRAM %_CPU
===== ============================== ======= ======= ====== ====== =====
10724 org.eclipse.osgi_3.9.1.v201401 36 36 60 60 0
^[[1A10724 org.eclipse.osgi_3.9.1.v201401 36 36 60 60 0
^[[1A10724 org.eclipse.osgi_3.9.1.v201401 36 36 60 60 0
^[[1A10724 org.eclipse.osgi_3.9.1.v201401 36 36 60 60 0
^[[1A10724 org.eclipse.osgi_3.9.1.v201401 36 36 60 60 0
^[[1A10724 org.eclipse.osgi_3.9.1.v201401 36 36 60 60 0
best
bruno
The text was updated successfully, but these errors were encountered: