[Github-comments] [geany/geany] Please implement way to alter path to geany.glade at runtime (#1702)

krisjace notifications at xxxxx
Fri Dec 1 20:57:50 UTC 2017


related to this old issue: https://github.com/geany/geany/issues/788
I have stated my rationale there, repeating here:
--------------------------------------------------------------------------------------
dear all, this original post really is about a not so well thought design of geany. I want to tell you a bit specific sitation. I am running Geany on my phone (Ubuntu Touch), you can see here: neither it does on other Linux machines by default

Now, on the phone, the most of the filesystem except ~/, is read-only. Also, is very limitted in space. Installing geany's files into /usr or anywhere outside of ~/ would be considered very expensive. So me, I installed it locally under my home. Should geany be a bit more flexible, that'd be not a problem at all. Even desktop launcher can be added to ~/.local/usr/share/applications/ instead of /usr/share/applications, and so on, HOWEVER, I had to manually ln -s my home based installation back to /usr/share/geany.

Sure, I can do this, just as I can install with a prefix to my home, but that is not convenient. That is not allowing for there to be a way of convenient automated installation to user's home directory. And basically, the ONLY portion which makes it hard, is that path containing the glider.

Just imagine how much more flexible and convenient the Geany would become if you could simply supply the path via environmental var or a command line switch.

Again, I can help myself, but I wanted to point out that in deed, Geany has a small part that limits it without clear reason for it to be that way.

Best Regards,
Kris


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1702
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20171201/949cd3f1/attachment.html>


More information about the Github-comments mailing list