[Github-comments] [geany/geany] TrueOS env/$PATH settings don't work for execution (#1887)

tracing-home notifications at xxxxx
Sat Jun 23 13:42:07 UTC 2018


FreeBSD bsd.local 12.0-CURRENT
Geany 1.32, de_DE.UTF-8

I am trying to run `context` inside the make configuration
`context  "%d/%f"`

`context -v "/usr/home/martin/Dokumente/hallo.tex" (im Verzeichnis: /usr/home/martin/Dokumente)
/bin/sh: context: not found
`
the same command works well in the regular terminal

I cannot figure out where geany gets the env/$PATH from, or actually fails to get it. What do I need to configure where to have geany evaluate the environment?

I found an old thread from 2014 having the same problem and it remained unsolved (leaving hacks aside)

[](https://www.linuxquestions.org/questions/linux-general-1/%24path-different-from-gui-terminal-and-from-application-geany-4175525583/)


What I have tried:

Running env as a make command does show a $PATH that misses the relevant path to the needed binary.
`
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/home/martin/bin
`

`
$ which context
/usr/home/martin/context/tex/texmf-freebsd-amd64/bin/context
`
PATH is set in .bashrc:
`
export PATH=$PATH:/usr/home/martin/context/tex/texmf-freebsd-amd64/bin
export MY_BASH=bashrc-greetings
`
.profile is not read at all, a similar MY_PROFILE never shows with env.

Using the inbuilt terminal of geany, I get the same env as from the regular terminal, ie, $PATH is set

My settings for terminal in VTE shell are, exactly what `which bash` gives
`/usr/local/bin/bash`


I tried changing settings/tools/terminal from:
`xterm -e "/bin/sh %c"`
to:
`xterm -e "/usr/local/bin/bash %c"`

That has no effect either. ` /bin/sh: context: not found` remains


-- 
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/1887
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20180623/8f776243/attachment.html>


More information about the Github-comments mailing list