PrestoSoft Community

We are talking about the same thing. We'd have to implement the whole COBOL parser (this is how EDP does syntax highlighting) in order to color keywords, detect comments etc.

When you say "untyped" files, do you mean those with no extension?

It means files with extensions not defined in Options | Doc Types and Default/Plain Text files.

When you say "user-defined parsers", do you mean loading Tree-sitter parsers /if/ someone had managed to create one themselves? I mean any kind of a parser library we end up switching to (if and when this is going to happen). I'd have thought the effort involved in allowing users to suppl...

Yes, we are well aware of these limitations and are constantly looking for alternatives to the parser engine we use. Tree-sitter is one alternative we are considering. As for user-defined parsers and language detectors, this is something we don't foresee in the immediate future.

While we don't plan on implementing COBOL syntax highlighting, you can define a custom document type for COBOL, as described at https://blog.prestosoft.com/2012/09/com ... f-pro.html . Unfortunately, the syntax highlighting library we use does not support COBOL.

The latest build of 14.0 Beta contains the requested changes. Please give it a try.

Thanks, will update.

Thanks. The structure I tested has multiple folder levels but maybe there is something else that is different.

Thanks for the instructions. The end result is different from yours: no errors comparing two folders from WSL, with full file comparison and plug-ins enabled. This is both in 13 and 14 Beta. There must be something different about either your setup or, less likely, with your EDP options.

Thanks for confirming! BTW, we will most likely stop supporting XP with the next version.

I believe we tested it. What error do you get?

We don't use WSL in house. Is the any way to reproduce it in Windows 10?

The following have been included in the latest Beta 14.0 build:

• New: Ability to switch between different code pages to display byte codes in binary comparison

• Improvement: The width of the address column in binary comparison views is based on file sizes

Currently, as you said, the only way to deal with these use cases is to start a new instance externally. We'll look into these scenarios more closely a bit later, and perhaps will make dealing with them easier.

Open a comparison of 2 files Select "New Comparison" Check "Run in new instance" Click on "Empty files" Bug: Current instance is closed This is not new in 14.0. "Run in new instance" only applies to real comparison while "Empty files" is a shortcut ...