I use JEdit to edit rtf documents.
Word 2010 that I use generates an error and headers and footers are marked with double rr - headerr/footerr. I have to search for these words and correct them.
Is it possible to configure the editor so that the winning words (headerr and footerr) are automatically colored right away?

Would it be possible to have a user selection to disable ErrorList debug logging for large error sets? I'm working on error checking SUO-KIF files (www.ontologyportal.org) via a SUMOjEdit plugin that uses the ErrorList and with a large set of errors, the ErrorList will hang up the UI for a bit while outputting many debug logs. Thanks for all help!

Would it be possible to have a user selection to disable ErrorList debug logging for large error sets? I'm working on error checking SUO-KIF files (www.ontologyportal.org) via a SUMOjEdit plugin that uses the ErrorList and with a large set of errors, the ErrorList will hang up the UI for a bit while outputting many debug logs. Thanks for all help!

I was puzzled, recently, over why Jedit could not access (see, read, write) most files on my Chromebook. Any experienced Linux user would know the answer instantly: "Your file permissions aren't set correctly." Here is some very rough guidance on how to access files stored locally on a Chromebook (in the "Chrome" and the Linux file systems) and on Google Drive. What follows assumes that you've turned on the Linux (Crostini) environment in your Chromebook. Again, this is rough:

** Do this once: In chromeos file manager: select a folder from left pane, share with linux or manage linux sharing. There is no such option for the Google Drive folder. File access there seems to be set file by file as you open to edit with jedit.
** Local files: In Jedit, navigate to /mnt/chromeos/MyFiles/
** Local linux files: In Jedit, navigate to /home/[username] OR in chrome file browser, go to Linux files (left pane), then select a file and open with Jedit.
** Google Drive files: In Drive, right click a file, select open with Jedit. (This grants permanent r/w permission to jedit, so later you can open the Jedit file browser, go to /mnt/chromeos/GoogleDrive/Computers/..., and open the previously edited file).

I was puzzled, recently, over why Jedit could not access (see, read, write) most files on my Chromebook. Any experienced Linux user would know the answer instantly: "Your file permissions aren't set correctly." Here is some very rough guidance on how to access files stored locally on a Chromebook (in the "Chrome" and the Linux file systems) and on Google Drive. What follows assumes that you've turned on the Linux (Crostini) environment in your Chromebook. Again, this is rough:

** Do this once: In chromeos file manager: select a folder from left pane, share with linux or manage linux sharing. There is no such option for the Google Drive folder. File access there seems to be set file by file as you open to edit with jedit.
** Local files: In Jedit, navigate to /mnt/chromeos/MyFiles/
** Local linux files: In Jedit, navigate to /home/[username] OR in chrome file browser, go to Linux files (left pane), then select a file and open with Jedit.
** Google Drive files: In Drive, right click a file, select open with Jedit. (This grants permanent r/w permission to jedit, so later you can open the Jedit file browser, go to /mnt/chromeos/GoogleDrive/Computers/..., and open the previously edited file).