ConTEXT

[Monty Python]

Hi, I'm new to FreeBASIC and use ConText editor. I would like a few hints and tips on the best way to set up the 'user execute keys'.

Currently I have f12 set to run a batch file and compile the source and f11 runs the compiled executable. This means that after every compilation I have to close the window created by the batch file and then hit f11 to run the executable.

I wrote the batch file because the compiler window was closing before I could see if there are any errors.

Any help will be appreciated , thank you,

Monty.

[steven_basic]

I use ConTEXT as my editor for FreeBASIC. I found the best setup for the I do things is as follows...

Execute keys for BAS extension:

F9
Execute: C:\freebasic\fbc.exe
Start in: %p
Parameters: -g -v -e -s console %f
Capture Console Output: [checked]
Compiler Output Parser Rule: %n(%l)

F10
Execute: C:\freebasic\fbc.exe
Start in: %p
Parameters: -s gui %f
Capture Console Output: [checked]
Compiler Output Parser Rule: %n(%l)

F11
Execute: C:\freebasic\fbc.exe
Start in: %p
Parameters: -l sdl -s gui %f
Capture Console Output: [checked]
Compiler Output Parser Rule: %n(%l)

F12
Execute: %p%F
Start in: %p
Parameters:
Capture Console Output: [unchecked]
Compiler Output Parser Rule:


F9 is used for "debugging" with console output.
F10 is win32 gui compile.
F11 was setup for some SDL coding I was tinkering with.
F12 is used to run the compiled source code.

With the parser rule setup, you can click the error line on the captured output and go directly to the line in the source file.

[Monty Python]

Thank you, it works great except I can't jump to error line :S Oh well, there seems to be plenty of info on the context forum concerning this.

Thanks for taking the time to reply,

Monty.

[Monty Python]

Hi, just to say that I've solved it. For reference in the parameter box %f needs replacing with %n and everything is cool

Thank you,

Monty.

[steven_basic]

No. You have to have the "Start In:" parameter set to %p "file path" and the %f "file name only" will work.

Context launches the FBC.EXE command line compiler from its installation location. It moves to the current file location and compiles the file name. This works best if you are going to $include other source files that reside in the current file's same folder.