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

Variable highlighting in double quoted strings of Perl scripts (KOMODO IDE 9.3) #914

Closed
ko-ichi-h opened this Issue Nov 29, 2015 · 3 comments

Comments

Projects
None yet
3 participants
@ko-ichi-h

ko-ichi-h commented Nov 29, 2015

In KOMODO IDE 9.2, variable names in double quoted strings of Perl scripts like below are highlighted.

print "printing a $variable!\n";

But they are not highlighted in 9.3.1 anymore. It seems like 9.3 broke variable highlighting in strings, at least in Perl.

Thanks!

p.s.
I am heavily using KOMODO IDE to write Perl scripts. This is a very nice IDE and editor!

@mitchell-as

This comment has been minimized.

Member

mitchell-as commented Nov 30, 2015

Thanks for the report. We updated our editing component (Scintilla), which has a new Perl lexer that appears to not support the functionality you describe (but adds lots of new stuff). We'll try to address this in the future.

@mitchell-as mitchell-as added this to the Backlog milestone Nov 30, 2015

@mitchell-as mitchell-as self-assigned this Nov 30, 2015

@Naatan Naatan modified the milestones: 10.0, Backlog Nov 30, 2015

mitchell-as added a commit that referenced this issue Nov 30, 2015

fix: Fixed regression in Perl interpolated variable highlighting with…
… Scintilla upgrade - fixes #914

Also updated codeintel and other Perl facilities that depends on this.

rn=
@mitchell-as

This comment has been minimized.

Member

mitchell-as commented Nov 30, 2015

It turns out Scintilla's new Perl lexer did support interpolated variable highlighting, but we were not set up correctly to use it. This is fixed now.

@ko-ichi-h

This comment has been minimized.

ko-ichi-h commented Dec 1, 2015

Thank you!

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