Idea's while setting up nvim as editor for a simple basic hello world console app

[Glog78]

Since the editor and UI leaves alot to desire i wanted to use another editor (neovim). While setting all up i i stumbled across a few things and wanted to give feedback.

• The compiler has it's own error format which is most likely not supported in any other editor (at least not in neovim). It would be cool if there was an option to change the error format to gcc like error messages. (example -> fpc's -vr option)

• The linux compiler does something strange. If you do:: qb64 -x input.bas -o output.|ext| -> it removes the ext. | If you do qb64 -x input.bas -o output.|ext1|.|ext2| it only removes ext2 | since i guess there is no consistent way to make this extension removing implicit right for everyone i would love to see no handling of the extension when the -o paramter is used. (change to an explicit behaivior)

• qb64 -z ignores completly the -o option | I am not sure why you decided for this to be the case but i would love to see an option to have the cpp sourcecode next to the basic sourcecode. I would prefer something like -od (output directory) where you have a cpp compilable structure.

• qb64 seems to have troubles with specific path names to find the sourcecode. I stumbled accross no source file found when having a underscore in my pathname or it could be related to subdirs being larger than 8 character.

• it would be totally cool to have lsif / lsp support (big feature).

For reference i attached the small project with the Makefile and a screenshot using nvim + a few plugins.

hello.tar.gz

[aouwt]

Related to third bulletpoint: #199