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

RIDE Log should get messages written to STDOUT and STDERR #1179

Closed
yanne opened this issue Jun 3, 2015 · 3 comments
Closed

RIDE Log should get messages written to STDOUT and STDERR #1179

yanne opened this issue Jun 3, 2015 · 3 comments
Labels
enhancement Request for improvement: either for an existing feature or a new one fixed Issues that have been fixed and can be closed already prio-medium Behaving incorrectly, but still somewhat usable
Milestone

Comments

@yanne
Copy link
Member

yanne commented Jun 3, 2015

Originally submitted to Google Code by @mkorpela on 28 Nov 2012

Things to remember:

  • --debugconsole
  • log_to_console option
@yanne
Copy link
Member Author

yanne commented Jun 3, 2015

Originally submitted to Google Code by @pekkaklarck on 17 Dec 2012

Unfortunately no time to get this done for 1.0. The original description is a bit brief so the motivation behind this enhancement is explained below:

  1. Currently errors can end up to the console (stdout/stderr) or into RIDE's log. It would be good to have all errors in one place and RIDE's log is definitely better place.

  2. When starting RIDE using the desktop shortcut on Windows, errors written to stdout/stderr are not visible anywhere. If they were written into RIDE's log, debugging problems would be easier.

  3. In general it would be better to have no extra outputs on console.

The original idea was to just intercept stdout and stderr unconditionally, but when we looked at this a little more we noticed that there are some cases, listed in the original description, when that is not a good idea. Need to still think should we intercept std streams automatically in other cases or should we perhaps make that configurable with a command line option. In the latter case the Windows shortcut should obviously enable intercepting automatically.

@yanne yanne added enhancement Request for improvement: either for an existing feature or a new one prio-medium Behaving incorrectly, but still somewhat usable labels Jun 3, 2015
@yanne yanne added this to the Future milestone Jun 7, 2015
@HelioGuilherme66
Copy link
Member

@jnhyperion Do you agree this will be solved?

@jnhyperion
Copy link
Collaborator

@HelioGuilherme66 Agree.

@jnhyperion jnhyperion added the fixed Issues that have been fixed and can be closed already label Aug 12, 2020
@HelioGuilherme66 HelioGuilherme66 modified the milestones: Future, v2.0 Aug 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Request for improvement: either for an existing feature or a new one fixed Issues that have been fixed and can be closed already prio-medium Behaving incorrectly, but still somewhat usable
Projects
None yet
Development

No branches or pull requests

3 participants