> Yes, I now know how Geany works as I have been fighting this for a whole
> day. I don't know what it doesnt like. I may just do another installation of
> it.
>
> I have another issue trying to create filetypes for *.ino files (arduino)
> but that
> doesnt seem to work. I have been ALL OVER the manual and I dont know
> what I am doing wrong.

What version of Geany are you using?  The current release (1.33) comes
with an Arduino filetype that .ino maps to.

>
> I will start another topic though and not include it in this.
>
> Thanks for your help. I had just installed linux and got rid of windows so
> thats
> another hurdle I am working with. Way different than Windows. Windows is
> like a
> personnal computer linux is like working at a terminal and there's a main
> frame
> somewhere on campus ; )

Well, thats what it was when Unix was first conceived :)

>
>
> Cheers
> Lex
>
>> Cheers
>> Lex
>>
>> On 23 May 2018 at 12:01, Joe McCarron via Users <users@lists.geany.org>
>> wrote:
>>>
>>>
>>> On Tuesday, May 22, 2018, 9:34:41 PM EDT, Lex Trotman <elextr@gmail.com>
>>> wrote:
>>> pythonbuild.py  is in /home/joe
>>>
>>>
>>>
>>> What directory is 'pythonbuild.py' located in and what was the working
>>> directory when you ran the CLI command?
>>>
>>> has always been in /home/joe    I am running the CLI from there also
>>> the working directory is dev/Arduino/sample/sample.ino  which is relative
>>> to my ~ location. The abs path of the working directory would be
>>> /home/joe/dev/Arduino/sample/sample.ino
>>>
>>> If your command is 'python pythonbuild.py
>>> dev/Arduino/sample/sample.ino' then it must be executed in the
>>> directory that contains 'pythonbuild.py' since the path is given
>>> relative to the working directory (and so is
>>> 'dev/Arduino/sample/sample.ino' but we havn't gotten to it yet :).
>>>
>>> yes, that is true
>>>
>>> Geany commands (by default) run with a working directory that is the
>>> directory of the current file displayed in the edit area, you can
>>> change this in the "working directory" column of the "set build
>>> commands" dialog to make it a fixed location such as the directory
>>> where 'pythonbuild.py' lives.
>>>
>>> so your saying move pythonbuild to my working directory, correct ?
>>> Ok, I will try that. So maybe the problem is the there is no way for the
>>> working
>>> directory to get to reference the up stream directory ? as in its ok to
>>> drill down but
>>> not up ?? I will try try moving the *.py file to the working directory.
>>>
>>> Yes, so the working directory is just use  %d%f so the whole thing in
>>> Geany
>>> python home/joe/pythonbuild.py  %d/%f
>>>
>>> but I get Invalid working directory
>>> "/home/joe/dev/Arduino/4X20OLED/4X20OLED.ino"
>>>
>>>
>>>
>>>
>> _______________________________________________
>> Users mailing list
>> Users@lists.geany.org
>> https://lists.geany.org/cgi-bin/mailman/listinfo/users
>>
>> _______________________________________________
>> Users mailing list
>> Users@lists.geany.org
>> https://lists.geany.org/cgi-bin/mailman/listinfo/users