Ticket #153 (closed enhancement: fixed)

Opened 10 years ago

Last modified 8 years ago

syntax file format needs doc

Reported by: slyfox Owned by:
Priority: minor Milestone: 4.7
Component: documentation Version: master
Keywords: Cc: zaytsev
Blocked By: Blocking:
Branch state: Votes for changeset:

Description

I'd like /usr/share/mc/syntax/ would have README file.
I think this README must contain:

  • syntax file format description
    • something, like BNF would be great (at least i will know where i can use regular expression and where i can't :])
    • explain every keyword a little
  • complete regular expressions format (and/or link to it's description if it's not special)
    • notes on performance of constructs (maybe, list and describe some common inefficient regexp patterns)

Change History

comment:1 Changed 10 years ago by winnie

  • Priority changed from major to minor
  • Keywords syntax, doc, feature removed
  • Milestone changed from 4.6.2 to 4.7

As this is an enhancement and now bugfix I put it into the 4.7 release.. as the 4.6.x series should only contain bugfixes.

Furthermore I removed the keywords as we use the keywords field for setting vote-<name> approved etc. tags

comment:2 Changed 10 years ago by angel_il

  • Milestone changed from 4.7 to future releases

comment:3 Changed 9 years ago by styx

  • Version changed from 4.6.1 to master
  • Component changed from mcedit to documentation
  • severity set to no branch

comment:4 Changed 9 years ago by andrew_b

Syntax file format is described in mcedit.1.

comment:5 Changed 9 years ago by styx

A part of cooledit man page translated into russian, which describes syntax coloring rules:
http://translated.by/you/syntax-highlighting-in-cooledit/into-ru/.txt

comment:7 Changed 8 years ago by zaytsev

  • Status changed from new to closed
  • Resolution set to fixed
  • Milestone changed from Future Releases to 4.7

comment:8 Changed 8 years ago by zaytsev

  • Cc zaytsev added

Documented in the man pages, translated in the wiki. Closing.

Note: See TracTickets for help on using tickets.