Custom Query (95 matches)

If we install a gtksourceview-3.0 language file to /usr/share/gtksourceview-3.0/language-specs, gedit and other GtkSourceView?-based editors will get syntax highlighting. This will be particularly useful on the Expo laptop.

I’ve written a language file and will attach it to this ticket. I lack the enthusiasm to get it installed via autotools at the moment though.

The language file follows the documentation here: https://survex.com/docs/manual/datafile.htm. There seem to be some differences between the documentation and common usage wrt *team and *instrument commands. I’ve stuck with what the documentation specifies.

The reference for the GtkSourceView? language-spec format is here: ​https://developer.gnome.org/gtksourceview/stable/lang-reference.html.

*date 1993.07.17 ; trip 1993-161-15 in logbook

in Loser\caves-1623\161\lhr\arrow.svx

Survex 1.2.42

/mnt/d/CUCC-Expo/t37/loser/kataster/../caves-1623/161/lhr/arrow.svx:75:18: error: Expecting numeric field, found “in”
trip 1993-161-15 in logbook
                  ^~
/mnt/d/CUCC-Expo/t37/loser/kataster/../caves-1623/161/lhr/arrow.svx:75:21: error: Expecting numeric field, found “logbook”
 trip 1993-161-15 in logbook
                     ^~~~~~~

Hey!

I'm use a lot of Export function to get cave surveys positions and found out that JSON format exported by Survex isn't correct.

This is file exported as JSON from Survex:

var p = [0.00,0.00,0.00,10.00,10.00,10.00]
var groups = [
[[0.00,0.00,0.00],[0.00,0.00,10.00]],
[[0.00,0.00,0.00],[0.00,10.00,0.00]],
[[0.00,0.00,10.00],[10.00,0.00,10.00]],
[[10.00,0.00,10.00],[10.00,0.00,0.00]],
[[10.00,0.00,0.00],[0.00,0.00,0.00]],
[[10.00,10.00,0.00],[0.00,10.00,0.00]],
[[10.00,10.00,0.00],[10.00,0.00,0.00]],
[[10.00,10.00,10.00],[10.00,10.00,0.00]],
[[10.00,10.00,10.00],[10.00,0.00,10.00]],
[[0.00,10.00,10.00],[10.00,10.00,10.00]],
[[0.00,10.00,10.00],[0.00,0.00,10.00]],
[[0.00,10.00,0.00],[0.00,10.00,10.00]]
]}

You can use simple site checking format validation: ​https://jsonformatter.curiousconcept.com/#

Trying to parse that file as JSON without additional pre-processing will always fail.