There should be a list of Logo operators with priorities, inside Logo help screen. This is useful for beginners.
There are examples with some operators, like > or ==, but a complete list would be good, specially because of conditional commands and mathematical expressions.
Please provide a screenshot and reproducible steps.
Marking as NEEDINFO - once you provide steps that others can reproduce and can understand what they are looking for mark as UNCONFIRMED. Do not assume others are familiar with the tools you use within the project (simply too many tools for QA to be familiar with all of them). Thanks!
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.
For more information about our NEEDINFO policy please read the wiki located here:
If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Message generated on: 10/01/2015
This is just a suggestion to make LibreLogo operators become clear to beginners. What could be done is just to include LibreLogo operators in some part of the LibreLogo help screen.
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):
a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue.
Please do not:
a) respond via email
b) update the version field in the bug or any of the other details on the top section of FDO
Message generated on: 2015-02-11