Please find attached an improved version of the macro to create a bug report. It now not only includes the activity log but also system, jEdit and Look and Feel properties as well as the list of the running plug-ins, a section for the bug description and a table of content
I like the ideas here, but I think the list of running plugins should come up first.
Do you really think a list of the jedit properties is necessary to make a bug report? I think that can make the file unnecessarily big.
The system properties is a good idea though.
Finally, perhaps there should be explicit folds around the secitons so that we can use the Outline plugin to navigate.
Last edit: Alan Ezust 2015-02-03
I am not sure what pending->rejected means. However, I am not much in Java programming and not at all in jEdit core or plugin programming. So I am very happy to get feedback and adapt my macro to the wishes. Only it will take a little time.
Please find attached a new version.
I included explicit folding markers and I changed the order according to the proposal. However, I left all the information parts in it. I feel that, if they are not needed, they can be ignored easily either by folding or sidekick navigation. Therefore I set the editing mode to outline and tried to set the folding mode to explicit. Strangely, the folding is effective by markers but the buffer properties still shows "indent". I am not sure whether this is a bug.
I do not know how to set the sidekick parser to outline from within the macro.
I fixed the table of content.
ok I will take a pass at it myself and add some enhancements too.