×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 2019-03-14 3:03 PM, Booth Martin wrote:
When editing source there are times when I do not want every key stroke
flying off with 20 error messages. Yet most of the time the feature is
really helpful
So, can I suspend the feature in some way?
Try having the errors shown as annotations instead of the pink lines. I
find it much easier to ignore the wiggly underlines and the marks in the
margins. When I think the statement is fine, it's easy to hover over the
wiggly line or the mark in the margin and see what it's still
complaining about.
Remote Systems > Remote Systems Lpex Editor > IBM i Parsers
- "Display syntax errors as annotations"
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.