Op 12/01/2016 om 04:49 PM schreef Stefan Salewski:
> My Nim editor https://github.com/ngtk3/NEd can be launced from the
> directory with the binary by typing
>
> ./ned file.nim
>
> For testing that is fine. But to make it work from an arbitrary
> directory something like
>
> # And for making gsettings available system wide one method is, as root
> # https://developer.gnome.org/gio/stable/glib-compile-schemas.html
> # echo $XDG_DATA_DIRS
> # /usr/share/gnome:/usr/local/share:/usr/share:/usr/share/gdm
> # cd /usr/local/share/glib-2.0/schemas
> # cp org.gtk.ned.gschema.xml .
> # glib-compile-schemas .
> #
>
> # as root
> cp nimdark1.xml /usr/share/gtksourceview-3.0/styles/
> cp nim.lang /usr/share/gtksourceview-3.0/language-specs/
>
> is necessary as described in the doc. That is fine for myself, but I
> can understand that other people fear to damage their system when doing
> root actions.

For GSettings you can keep them local (but do compile) and export
GSETTINGS_SCHEMA_DIR [1] to where you have stored them. Unfortunately
the api docs make no reference to [1] so very few will actually find it.

For the language definition you can copy them to
|~/.local/share/gtksourceview-3.0/language-specs/| and it should get
picked up automatically, see [2].

With that you should be able to keep root out :-).

~infirit

[1] https://developer.gnome.org/gio/stable/running-gio-apps.html
[2] https://developer.gnome.org/gtksourceview/stable/lang-reference.html


_______________________________________________
gtk-list mailing list
gtk-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-list

Reply via email to