Commit 6b17eced authored by André Simon's avatar André Simon

documentation updates

parent 7c3d0608
......@@ -3,7 +3,7 @@ CHANGELOG Highlight
highlight 3.37
xx.xx.2017
29.05.2017
-updated astyle code to release 3.0
-added examples/pandoc (thanks to Tristano Ajmone)
......
......@@ -20,8 +20,10 @@ Content
root of highlight-x.x
|
|-- examples # examples for highlight scripting
| |-- web_plugins # plugins for various web toolkits
| |-- json # Lua to JSON converters
| |-- pandoc # Pandoc macros
| |-- tcl # TCL extension
| |-- web_plugins # plugins for various web toolkits
| `-- swig # SWIG interface and sample code
|-- gui_files # supporting files for the optional GUI
| |-- ext # file open filter configuration
......@@ -209,3 +211,10 @@ mintsystem provides: /usr/local/bin/highlight
Calling this script with the true highlight command line options will have no effect.
See bug tracker items: https://bugs.launchpad.net/linuxmint/+bug/593583 and
https://bugs.launchpad.net/linuxmint/+bug/815005
OpenSUSE Leap 42.2
The lua-devel package installation causes error messages.
The Dependency conflict may be ignored.
-------------------------------------------------------------------------------
--- HIGHLIGHT MANUAL - Version 3.36 --------------------------- March 2017 ---
--- HIGHLIGHT MANUAL - Version 3.37 ----------------------------- May 2017 ---
-------------------------------------------------------------------------------
OSI Certified Open Source Software
......@@ -21,6 +21,7 @@ CONTENT
2.4 INPUT AND OUTPUT
2.5 GNU SOURCE-HIGHLIGHT COMPATIBILITY
2.6 ADVANCED OPTIONS
2.7 ENVIRONMENT VARIABLES
3. CONFIGURATION
3.1 FILE FORMAT
......@@ -439,6 +440,15 @@ Invoke highlight-gui.exe with the --portable switch to save its configuration
in text files instead of the registry.
2.7 ENVIRONMENT VARIABLES
-------------------------------------------------------------------------------
The command line versuin recognizes these variables:
HIGHLIGHT_DATADIR: sets the path to highlight's configuration scripts
HIGHLIGHT_OPTIONS: may contain command line options, but no input file paths
3. CONFIGURATION
-------------------------------------------------------------------------------
......@@ -801,9 +811,6 @@ These subdirectories are expected to contain the corresponding scripts:
A custom filetypes.conf may be placed directly in ~/.highlight/.
This search order enables you to enhance the installed scripts without the need
to copy preinstalled files somewhere else.
As the --plug-in option of older releases accepted absolute paths only, the
given plugin scripts will be searched in the directories above only if the
absolute file path access fails.
4. EMBEDDING HIGHLIGHT
......
-------------------------------------------------------------------------------
--- HIGHLIGHT MANUAL - Version 3.36 --------------------------- Maerz 2017 ---
--- HIGHLIGHT MANUAL - Version 3.37 ----------------------------- Mai 2017 ---
-------------------------------------------------------------------------------
OSI Certified Open Source Software
......@@ -21,6 +21,7 @@ INHALT
2.4 EIN- UND AUSGABE
2.5 GNU SOURCE-HIGHLIGHT KOMPATIBILITAET
2.6 FORTGESCHRITTENE OPTIONEN
2.7 UMGEBUNGSVARIABLEN
3. KONFIGURATION
3.1 DATEIFORMAT
......@@ -451,6 +452,15 @@ Portable GUI (Windows build)
Starten Sie highlight-gui.exe mit der --portable Option, damit die
Konfiguration in Textdateien und nicht in der Registry gespeichert wird.
2.7 ENVIRONMENT VARIABLES
-------------------------------------------------------------------------------
Die Kommandozeilenversion beruecksichtigt folgende Variablen:
HIGHLIGHT_DATADIR: setzt den Pfad zum Konfigurationsverzeichnis
HIGHLIGHT_OPTIONS: kann Kommandozeilenoptionen enthalten, aber keine Pfade zu
Eingabedateien
3. KONFIGURATION
-------------------------------------------------------------------------------
......@@ -824,9 +834,6 @@ enthalten:
Eine eigene filetypes.conf kann direkt in in ~/.highlight/ gespeichert werden.
Diese Suchreihenfolge vereinfacht die Erweiterung und Anpassung bestehender
Skripte, ohne vorinstallierte Dateien umkopieren zu muessen.
Da die plug-in Option aelterer Versionen nur absolute Pfade akzeptierte, werden
die angegebenen Skripte nur dann in den obigen Verzeichnissen gesucht wenn
der Zugriff auf den absoluten Pfad fehlschlaegt.
4. HIGHLIGHT EINBETTEN
......
......@@ -2,6 +2,7 @@
--
-- Add an entry for a language syntax which is occupied by multiple source file extensions.
-- If there is only one extension, just name the lang file accordingly and it will work.
-- The filetype entries in gui_files/ext/fileopenfilter.conf should also be updated.
--
-- Extensions can be configured for multiple languages (see "asm", which is assigned to assembler and fasm):
-- - CLI: the first association listed here will be used
......
......@@ -43,7 +43,7 @@ Clean (*.icl)
ClearBasic (*.cb)
Clipper (*.clipper)
Clips (*.clp)
Clojure (*.clojure)
Clojure (*.clojure *.clj)
COBOL (*.cob)
Coffeescript (*.coffee)
Coldfusion-MX (*.cfc *.cfm)
......@@ -70,7 +70,7 @@ Fortran90 (*.f95 *.f90)
Frink (*.frink)
Gambas (*.class)
GDB (*.gdb)
GithubMarkdown (*.md)
GithubMarkdown (*.md *.markdown)
Go (*.go)
GDScript (*.gd)
Graphviz (*.dot)
......
......@@ -70,7 +70,10 @@ install:
${DESTDIR}${examples_dir}web_plugins/dokuwiki \
${DESTDIR}${examples_dir}web_plugins/movabletype \
${DESTDIR}${examples_dir}web_plugins/wordpress \
${DESTDIR}${examples_dir}swig
${DESTDIR}${examples_dir}swig \
${DESTDIR}${examples_dir}pandoc \
${DESTDIR}${examples_dir}json \
${MKDIR} ${DESTDIR}${data_dir} \
${DESTDIR}${data_dir}themes \
${DESTDIR}${data_dir}langDefs \
......@@ -95,9 +98,9 @@ install:
${INSTALL_DATA} ./examples/web_plugins/dokuwiki/* ${DESTDIR}${examples_dir}web_plugins/dokuwiki/
${INSTALL_DATA} ./examples/web_plugins/movabletype/* ${DESTDIR}${examples_dir}web_plugins/movabletype/
${INSTALL_DATA} ./examples/web_plugins/wordpress/* ${DESTDIR}${examples_dir}web_plugins/wordpress/
${INSTALL_DATA} ./examples/swig/*.py ./examples/swig/*.pl ${DESTDIR}${examples_dir}swig
${INSTALL_DATA} ./examples/swig/*.i ./examples/swig/makefile ${DESTDIR}${examples_dir}swig
${INSTALL_DATA} ./examples/swig/README_SWIG ${DESTDIR}${doc_dir}
${INSTALL_DATA} ./examples/swig/* ${DESTDIR}${examples_dir}swig
${INSTALL_DATA} ./examples/pandoc/* ${DESTDIR}${examples_dir}pandoc
${INSTALL_DATA} ./examples/json/* ${DESTDIR}${examples_dir}json
${INSTALL_DATA} ./examples/highlight_pipe.* ${DESTDIR}${examples_dir}
${INSTALL_DATA} ./examples/*.py ${DESTDIR}${examples_dir}
${INSTALL_PROGRAM} ./src/highlight ${DESTDIR}${bin_dir}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment