Bug 36541 - Wrong syntax highlighting in BASIC IDE
Summary: Wrong syntax highlighting in BASIC IDE
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version: unspecified
Hardware: Other All
: medium minor
Assignee: Andreas Becker
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-24 06:11 UTC by Andreas Becker
Modified: 2015-01-05 17:51 UTC (History)
4 users (show)

See Also:
i915 platform:
i915 features:


Attachments
screenshot of the IDE with wrong highlighting (27.55 KB, image/png)
2011-04-24 06:11 UTC, Andreas Becker
Details
patch that fixes the wrong highlighting (5.90 KB, patch)
2011-04-25 16:13 UTC, Andreas Becker
Details | Splinter Review

Description Andreas Becker 2011-04-24 06:11:48 UTC
Created attachment 46017 [details]
screenshot of the IDE with wrong highlighting

Two slashes make the rest of the line in the BASIC IDE to be displayed grey like a comment. However, two slashes are invalid syntax and a "General Error" message appears when the code is run.

The highlighting should be normal instead of grey.
Comment 1 Andreas Becker 2011-04-25 16:13:35 UTC
Created attachment 46070 [details] [review]
patch that fixes the wrong highlighting

And here is the patch for it!
Comment 2 clio 2011-05-23 02:56:44 UTC
Please, can you Noel review/push the patch?
Comment 3 clio 2011-05-23 14:26:35 UTC
I tested the patch with libreoffice-3.4.0.1 branch and haven't noticed any regressions. This patch also changes color of operators. Before this patch for most of them it was blue (+&^*.%&), and dark grey for the rest (/-\#). After the patch they are blue (except \ which is a integer division symbol used very rarely, ISTM). Question mark and semicolon were light-blue, became blue.
Comment 4 Thorsten Behrens 2012-07-25 18:50:47 UTC
(In reply to comment #2)
> Please, can you Noel review/push the patch?
>
Noel, any insight? Or has this been merged or implemented somehow, meanwhile?
Comment 5 Noel Power 2012-07-25 19:16:41 UTC
(In reply to comment #4)
> (In reply to comment #2)
> > Please, can you Noel review/push the patch?
> >
> Noel, any insight? Or has this been merged or implemented somehow, meanwhile?

sure, awaiting license info see
http://thread.gmane.org/gmane.comp.documentfoundation.libreoffice.devel/29370/focus=29481
Comment 6 QA Administrators 2015-01-05 17:51:12 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice (4.3.5 or later): https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)

Thank you for your help!

-- The LibreOffice QA Team


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.