Hi,

( Forwarding from https://sourceforge.net/p/joe-editor/bugs/396/ )

Please see the attached test file.

Inside backticks everything is displayed literally in Markdown. Still, an opening bracket present there screws up the rest of the highlighting, in particular, the subsequent list items are not colored in blue in the test file.

Backslash-escaping the bracket fixes joe's highlighting, but breaks the file since it'll show up as a backspace in the rendered version.

joemarkdown.md.txt

Could you comment a bit about the differences between ini.jsf and properties.jsf? From what I've read, "properties files" are mostly a rebranding of "ini files". I'm considering some changes to ini.jsf, particularly in how it deals with errors. (it seems to handle correct .ini files just fine.) Before I start working on it, I'd like to make sure I understand the contexts of these two .jsf files, as they seem to cover largely the same problem space. Thanks.

The syntax highlighting of the JSON document

[1.23, 1.2e3]

marks 3 and e3 with error coloring (white on red), but both numbers are valid JSON.
The error is in the following rule:

:integer Number
        *                       end             noeat
        "0-9"                   integer
        "."                     decimalpoint
        "eE"                    exponentpart

The target decimalpoint should be replaced by decimalpart:

:integer Number
        *                       end             noeat
        "0-9"                   integer
        "."                     decimalpart
        "eE"                    exponentpart

I have this also reported upstream, see ticket #376.

I know it's a joke, but still. :)

A number of ideas here:

1. Bold + italics doesn't quite work. IF I do this, the last * is unbolded. (Um, I escaped that avoid Github's own markdown parsing -- I mean three *s in a row)
2. Bold or colorize headers -- either lines immediately followed by a line with --- or === (any number), or lines that begin with #.
3. But three or more -, *, or _ on a line which isn't a headline should be a horizontal rule. I think this might be nicely represented by inverse-color for the whole line.
4. Color quoted text (lines start with >). Yellow, maybe.
5. Properly color automatic links like http://example.org/ (maybe just all http:// occurrences, with or without angle brackets?)

Anonymous functions displays as a function when writing "fun(bla, bla)" and a keyword when writing "fun (bla, bla)".

...and somewhat broke old syntax files. Sorry.

In order to support a wide variety of languages with a wide variety of color schemes, syntax files had to be overhauled so that classes could be made more consistent.

Here's an overview of how color schemes and syntaxes interact, and here's a list of the common classes used by both the schemes and the syntax files.

All is not lost, however. Version 4.5 will allow syntax files to specify the 16 basic terminal colors, and map them into the scheme if the scheme supports it. It will not respect any of the extended xterm-256 colors. This was done for backwards compatibility. However, forwards compatibility is impossible; 4.4 and below will fail to read a newer syntax file.

Since we merged many of your syntaxes a few years back, I can provide backports for those changes in the form of a PR. I am also willing to help with upgrading any newer ones. But I thought first I'd open the issue to see what you'd like to do about the issue, especially given the forwards-compatibility problem.

Cheers~

Hi,
Impossible for me to get the coloration of any syntax with Joe on Mac OS Maverick.
I have put the syntax as you explained here ;
/usr/local/Cellar/joe/3.7/share/joe/syntax

I'm using ** Joe's Own Editor v3.7 ** so happy to get it on my mac os after using it since 15 years on Linux in the past ... but unfortunatly impossible to get any result with syntax coloration ... how to know where my version of joe really look for the syntax ? Is possible to set the path somewhere ? Not found any answer about this on Internet, and conscient that is not also the right place to ask the question ... but may be someone could help me.

Regards,