Re: [ jEdit-users ] Turning off syntax highlighting for a file

[Edward D. <eld...@tr...>]

On 1/16/2021 7:35 AM, Robert Schwenn wrote:
> Hi,
> mainly there are two permanent background tasks: structure browsing in 
> sidekick and syntax highlighting. Both depend on edit mode. You could 
> quickly check if they're slowing down jedit by changing the edit mode to 
> "text" (means: no highlighting, no strucure) by ohne of them:
> 
> a) Utilities -> Buffer Options -> Edit Mode (only until next buffer load)
> b) permanent:  place ":mode=text:" in one of the first or last 10 lines 
> of the buffer

Thank you ! I do not have the Sidekick plugin installed so it must be 
because of syntax highlighting. The next time I experience a significant 
slowdown editing a C++ file I will change the buffer options edit mode 
to text and hopefully that will solve the problem. I assume that I can 
place ":mode=text:" anywhere in the first or last 10 lines, such as in a 
C++ comment, to have the file permanently be treated as text edit mode.

> 
> Robert
> 
> 
> Am 16.01.2021 um 06:43 schrieb Edward Diener:
>> JEdit sometimes slows to a crawl when editing certain complicated C++ 
>> files. By complicated I mean a C++ file which shows advanced C++ 
>> syntax features and which also may have temporarily incorrect C++ 
>> syntax as I work through some programming problem. By slowing to a 
>> crawl I mean that moving my cursor around in the file or placing my 
>> cursor somewhere in the file or scrolling through the file, is 
>> sometimes extremely slow, without JEdit taking a number of seconds, 
>> sometimes 5 or more, before I can continue editing.
>>
>> I believe this is happening because JEdit is trying in the background 
>> to parse the C++ constructs in the file, most probably because JEdit 
>> needs to understand the constructs in the file in order to do its 
>> syntax highlighting.
>>
>> I would like to defeat this occasional slowness somehow and the 
>> thought that I have is to do whatever is necessary to stop JEdit from 
>> parsing the C++ syntax elements in the file.
>>
>> Is Jedit parsing the C++ files in the background in order to 
>> understand its constructs ?
>>
>> Is Jedit trying to understand the constructs in order to provide 
>> syntax highlighting ?
>>
>> Is there a way to completely turn off syntax highlighting for a buffer 
>> ? Or for a file's edit mode ?
>>
>> Will turning off syntax highlighting ( I hope that is possible ) 
>> prevent JEdit from trying to parse the C++ constructs in the file ?
>>
>> The slowdown of course can be the result of some Plugin I have, but I 
>> do not see that any of my Plugins needs to parse the file for C++ 
>> constructs for any reason.
>>
>>
>>
> 
> 
>