Skip to content

Conversation

@big-andy-coates
Copy link

...to avoid additional output in processes picking up the JAVA_TOOL_OPTIONS.

Without quiet mode the process will output something like line below as its first line to stdout, which can cause problems in some situations, i.e. where the output is being consumed by another process.

Listening for transport dt_socket at address: 53880

fixes: #11

...to avoid additional output in processes picking up the `JAVA_TOOL_OPTIONS`.

Without quiet mode the process will output something like line below as its first line to stdout, which can cause problems in some situations, i.e. where the output is being consumed by another process.

```
Listening for transport dt_socket at address: 53880
```

fixes: JetBrains#11
@big-andy-coates
Copy link
Author

@jastice when you have a moment, could you take a look at this PR please?

@big-andy-coates
Copy link
Author

@uriariel any thoughts?

@uriariel
Copy link
Contributor

@big-andy-coates I don't think its a good idea to change it to quiet=y by default, not to mention in examples.

just add it locally to your ~/.attachme/conf.sh

@big-andy-coates
Copy link
Author

Hey @uriariel,

Thanks for getting back to me.

Can I ask what you see as the downside of turning on quiet mode by default?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Can't debug Gradle process

2 participants