I thought it might be that the library needed to be updated. But (assuming
I did the upgrade right) it's still broken. So either there's something
wrong with the plugin, or there's something wrong with the highlight
library.
This might be a small consolation, but you could stop the run-on by putting
a comment followed by an apostrophe at the end of the lines where it
occurs. Or, since you appear to be just logging, you could break the key
words a little (e.g. "com-mit").
Good luck,
Mark
On Tuesday, September 26, 2017 at 8:59:16 AM UTC-7, Captain Packers wrote:
>
> I'm running into a situation where I'm using reserved words withing quoted
> strings for output messages in PL/SQL, and the reserved words are messing
> up the syntax highlighting.
>
> For example:
>
> dbms_output.put_line('update_stf03_academicyear: commit not executed');
>
> has this affect on the rest of the code block:
>
> if j = 0 then
> if G_COMMIT then commit; end if;
> dbms_output.put_line('updatestf03: ' || i || ' records ' ||
> 'updated with academicyear');
> else
> dbms_output.put_line('updatestf03: WARNING: an ' ||
> 'unanticipated result has occurred.');
> dbms_output.put_line('updatestf03: commit not executed');
> end if;
>
> else
> dbms_output.put_line('updatestf03: nothing to update');
> end if;
>
>
> Does anyone know of a work around for this?
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/51cc70ba-48b4-42a1-831f-1fcade13adba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
