-
Notifications
You must be signed in to change notification settings - Fork 3
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
Comments are not added to a Java document if commented line too long #3
Comments
@may-bee: For Java we could check for the jdt preferences: org.eclipse.jdt.core.formatter.lineSplit gives us the maximal line length which we could use to adjust the tag location. Other languages use different formatters, so we would have to check for these as well :( |
I think that would be ok for me. You can also get the maximum line range for xml documents, but I think due to the non-existence of single line comments in xml, we can ignore this. As there has not been anybody who was experiencing this behavior, it might really be a less interesting topic. |
The latter experienced behavior:
looks a little bit strange to me. Did you reproduce it and found the cause? Why is the parser not adding anything to the document? |
Sounds reasonable. |
Hm, in my sample code it works just fine:
|
I think you have to add multiple maximum linesize comments |
Ok, broken, fine :) Weird stuff happening... |
I think so :) Until now I had no idea what's going on ... |
Precondition is a single ('//') commented line in a Java document which nearly reaches the automatic number or characters for an automatic line break done by the eclipse formatter. Then the hook is added and destroyed as the autmatic line break will do his job and forces a line break despite the '-' sign in front of the hook. :(
When adding a multi line comment on multiple lines---all commented by ('//')---no hooks will be added at all!!!
For now I do not know how to deal with this problem... but the user can work around this issue:
The text was updated successfully, but these errors were encountered: