aboutsummaryrefslogtreecommitdiffhomepage
path: root/lexicon_filter.in
Commit message (Collapse)AuthorAge
* more doxygen lexicon changes to eliminate errorsGravatar Kurtis Rader2016-04-24
| | | | | | I noticed that Doxygen was also complaining about the "<asis>" and "<bs>" tags. So convert those to the backslash form like we did for "<outp>" in the previous commit.
* replace <outp> command with \outp in docsGravatar Kurtis Rader2016-04-23
| | | | | | | | | | Doxygen has been warning that `<outp>` and `</outp>` are not valid XML/HTML commands since commit cb6d5d76 on 20016-04-04. That's primarily because there is at present no way to tell Doxygen to recognize new XML/HTML tags. The actual errors look like this: ``` .../string.doxygen:187: warning: Unsupported xml/html tag </outp> found ``` I hate build errors since they a) cause needless concern, and b) make it harder to notice when I've introduced a new error. So switch from XML/C## style markup to Doxygen style markup for the "outp" annotation.
* update lexicon for latest docsGravatar Mark Griffiths2016-04-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | Closes #2699 Fixes issues with: * 'string' function synopsis * Redirection display issues * Better file & path detection * Rendering of % & @ chars in both html and man * @ symbol in tutorial Improves robustness by implementing an @EOL marker to prevent hold buffer dumping extra chars after the end of an expression. Added new '{{' and '}}' meta-chars for when you want curly braces in a regexp that was previously tripping up the lexicon. Improve man/html presentation consistency for * string * printf * prompt_pwd * type Use cli-styling for 'practical' examples. Add <bs> tag for presenting content with preceding backslash. Signed-off-by: Mark Griffiths <mark@thebespokepixel.com>
* fix several build warningsGravatar Kurtis Rader2016-01-28
| | | | | | | | | | | | | | | | | | This fixes all but one of the warnings documented in issue #2685. The sole remaining warning is from the string split '' abc example in doc_src/string.txt. That example results in the man page displaying string split {} abc I leave it to someone else to fix that problem (I'll open an issue specifically for it since it took some effort to track down the source of the warning). Resolves issue #2685.
* Tweak lexicon_filter.in for GNU sedGravatar Kevin Ballard2014-10-01
|
* lexicon_filter fix for escaped optionsGravatar Mark Griffiths2014-09-23
| | | | | Fixes #1703. Also fixes short and long options markup in synopsis when directly following a '(' or '[' character.
* Updated license in lexicon_fiter.inGravatar Mark Griffiths2014-09-19
|
* Portable range fixGravatar Mark Griffiths2014-09-04
|
* Fix comment collision in lexiconGravatar Mark Griffiths2014-09-04
|
* Rebase documentation changesGravatar Mark Griffiths2014-09-03
|
* Formatting updatesGravatar Mark Griffiths2014-09-03
|
* Addition of 'ascii fish' logoGravatar Mark Griffiths2014-09-03
| | | | + small fixes
* Various additions and fixesGravatar Mark Griffiths2014-09-03
|
* Consistency fixesGravatar Mark Griffiths2014-09-03
|
* Fixed a few more edge casesGravatar Mark Griffiths2014-09-03
|
* Fix trailing backslash after complex optionsGravatar Mark Griffiths2014-09-03
|
* Fix ampersand redirectorGravatar Mark Griffiths2014-09-03
|
* Tutorial auto colouring, Man page and Make fixesGravatar Mark Griffiths2014-09-03
Completely fixes #1557 and the underlying Doxygen changes that caused it. Should make fish docs simpler and more robust, more consistent and generally prettier. todo: - trap unmarked text as arguments in context - test & fix sed portability - see in particular. (so far tested on BSD (Mac) and GNU sed). - test Makefile changes - last round of aesthetic changes and getting that ascii fish in thereā€¦