My first thought is ... WHY Json??... dh
On 9/28/20 5:49 PM, Boris Faure wrote:
billiob pushed a commit to branch master. http://git.enlightenment.org/apps/terminology.git/commit/?id=0dc4e1014f7010bd049e5650a942ef1127a1e7f6 commit 0dc4e1014f7010bd049e5650a942ef1127a1e7f6 Author: Boris Faure <bill...@gmail.com> Date: Mon Sep 28 23:24:07 2020 +0200 colorschemes: input files are JSON now --- data/colorschemes/builder.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/colorschemes/builder.sh b/data/colorschemes/builder.sh index 36994f6..1483e54 100755 --- a/data/colorschemes/builder.sh +++ b/data/colorschemes/builder.sh @@ -18,7 +18,7 @@ trap 'rm -f "$TMPFILE"' INT TERM HUP EXIT for JSON in "$@" do # use the name, without extension as key in eet - KEY=$(basename "$JSON" ".desc") + KEY=$(basename "$JSON" ".json") DESC="${KEY}.desc" $JSON2DESC "$JSON" "$DESC" $EET -e "$TMP_EET" "$KEY" "$DESC" "$COMPRESS"
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
