Doug, here's the data... The diff to fix some previously unsupported spaced variants: http://algol68.gridbug.de/2026-04-15_algol68.vim.diff (Note: the line numbers may not match your actual version.)
The remaining issues are based on the fact that some prefixes (bits, exp, real, system, blank, newline) are already used on their own; here I'd need your assistance how to best fix that: http://algol68.gridbug.de/2026-04-15_blank_issues.txt (Note: it probably could be fixed by reordering of lines, but then the semantic grouping would get lost, so that's not advisable if there's another cleaner solution existing. - I will have a look at it myself, but that may need some time and an acceptable outcome is not sure.) Thanks. Janis ________________________________________ Von: [email protected] <[email protected]> im Auftrag von Janis Papanagnou <[email protected]> Gesendet: Mittwoch, 15. April 2026 10:53 An: [email protected] Betreff: AW: [vim/vim] runtime(algol68): Add new syntax file and filetype detection (PR #19818) To identify problems with spaces in identifiers as reported in my previous mail I extended the test-file I had sent by a variant with spaces in identifiers added. It can be retrieved here: http://algol68.gridbug.de/all_preludes_w_sp.txt With that test-file we can see that there's some issues of the sort reported below (cf. 'bits' vs 'bits width'); as said, I'm not sure how to best fix these. (I will provide a list of these identifiers soon as a followup.) I also found some yet unsupported spaced versions that I intend to fix soon. (I will send a proposed update soon.) Thanks. Janis ________________________________________ Von: [email protected] <[email protected]> im Auftrag von Janis Papanagnou <[email protected]> Gesendet: Mittwoch, 15. April 2026 03:37 An: [email protected] Betreff: AW: [vim/vim] runtime(algol68): Add new syntax file and filetype detection (PR #19818) Doug, I noticed an issue but could not sensibly resolve it. - Maybe you have an idea? The problem is as follows... In these testcases bitswidth bits width maxbits max bits all but the second one are correctly highlighted as predefined (yellow), where the second one is blue (first word) and non-highlighted (second word) respectively. The rule that should cover the first two entries is syn match algol68Predefined "\<\%(\%(long\s*\)\?long\s*\)\?\%(bits\|bytes\|exp\|int\|real\)\s*width\>" And according to the (later appearing!) rule syn match algol68Function "\<\%(bits\|whole\|fixed\|float\|real\)\>" the function 'bits' is highlighted (blue). - For a standalone 'bits' that's as desired! So for 'bits width' the first rule seems to be overwritten/invalidated by the second. And moving the latter rule above the former will "fix" the observable behavior. But that's IMO not as it should be. (Apparently there's no return "longest match" principle between different rules.) A cleaner solution might need to formulate some context dependency? But I'm not familiar enough with Vim's syntax rules to suggest something here. Do you have an idea for a clean/cleaner solution to fix that? Thanks! Janis -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/vim_dev/DU0PR02MB10422086D75D3FB2C22DC2E27F3222%40DU0PR02MB10422.eurprd02.prod.outlook.com. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/vim_dev/DU0PR02MB104223DE4CD3CDDCD2618F23EF3222%40DU0PR02MB10422.eurprd02.prod.outlook.com. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/vim_dev/DU0PR02MB10422305E0C5DFABA41DE0701F3222%40DU0PR02MB10422.eurprd02.prod.outlook.com.
