How do I get my ++include file(s) open and added to the tab list?

Hi Maurice,
Unless I misunderstood your question, you don't have a list of include files in any window where you can double-click to open, instead, you position the cursor in the ++include line and combine the CTRL+ALT+O to open it.

Hope it helps.

Also note that if you are working with a particular set of files and want to close the session and return to it later, use the File > Save Workspace As option to save the workspace (the collection of files that are open), and then open the workspace when you want to return to that environment.

As an aside, although having all the relevant files open at the same time is one of the best advantages of multi-file editors like APN over VUE, the usual problem I have (and I suspect others do too) is to open so many files that you can't keep track of them all. I suggest reminding yourself to periodically double-click on the tab to close any files you aren't actively using so that the multi-file advantage doesn't turn into a disadvantage.

Hi Jorge,
Thanks for responding. I did move the cursor on the include line and hit Ctrl+Alt+O, but I got the following warning in the output dailogue;

WARNING : include.pyc:open_include() Include file not found: answer.map

I think there might be something missing in the APN options and I do not know what it is. What I really need to understand is how to get APN to identify my shared library files?

Does the program compile with the F5 command? If it can't find the parts, that would suggest the -ini file isn't set up.

oh! yes, for APN know all the include paths you need to compile the program, at least, once.

The program did not compile, it requires the shared library. I did setup my ini as APN.ini to look at the following devices;

DEVICE=DSK0 /vm/miame/dsk0/
DEVICE=DSK90 /vm/miame/dsk90/
DEVICE=SOS61 /vm/miame/dsk0/907010/

You don't actually have to compile the program, since each AShell BASIC program is pre-compiled when it gets loaded. But compiling is a good way to verify that the configuration is correct, which it appears not to be.

First, let's verify that APN recognizes your files as A-Shell BASIC. You should see something like this in the toolbar...



If not, then review this section of the doc.

If it is recognizing your files as A-Shell BASIC, then the next most likely problem would be that the compiler command line isn't set up, in which case see this topic .

If still having trouble, perhaps post us the exact contents of the Compiler command line definition.

See command line below along with parameters;

Command:
%(APN)\compil.exe

Parameters:
-ini L:\apn.ini -w:4000 -x:2 -m -px -lf -lsm -so "%d%f"

That seems right.

And is it identifying your file as A-Shell BASIC?

Any other messages in the window at the bottom when you compile?

Are you sure the L:\apn.ini has all the right DEVICE and ERSATZ definitions? Can you launch an A-Shell/Windows session using that same ini? (I use the same miame.ini for APN as I do for A-Shell/Windows, but it may be that you're not used to using A-Shell/Windows, so perhaps that complicates things, but also increases the suspicions about possible problems in your ini.)

You might try adding TRACE=FOPENS to that ini, then look in the ashlog.log after your compile attempt to see what kind of filespecs it is trying to open.

I think A-Shell BASIC is identified because I am able to navigate to my programs directory and select the file I want.

Here is the output of the my compile;

> "c:\vm\APN\compil.exe" -ini L:\apn.ini -w:4000 -x:2 -m -px -lf -lsm -so "L:\dsk90\060201\emvdsp.bas"
Compil 6.3(781)
emvdsp.bas,1,Unable to find ++INCLUDE file ,++INCLUDE SYSTEM.MAP
emvdsp.bas,2,Unable to find ++INCLUDE file ,++INCLUDE DATE.MAP
emvdsp.bas,3,Unable to find ++INCLUDE file ,++INCLUDE CHGPMT.MAP
emvdsp.bas,4,Unable to find ++INCLUDE file ,++INCLUDE PAT.MAP
emvdsp.bas,5,Unable to find ++INCLUDE file ,++INCLUDE BOX.MAP
emvdsp.bas,6,Unable to find ++INCLUDE file ,++INCLUDE ANSWER.MAP
emvdsp.bas,8,Unable to find ++INCLUDE file ,++INCLUDE SYSTEM.SUB

The fact that it executes the compil does tend to confirm that it recognizes your source code as A-Shell BASIC. My suspicion centers on two areas:

a) The DEVICE definitions in L:\apn.ini. (Can we have a look?)

b) Some issue in the compiler that was fixed and forgotten long ago. (Your version 781 is over 100 edits back from the current 886.) I can understand if you want to stick with the version for absolute certainty of compatibility with your present environment, but for testing/debugging purposes, it would eliminate some doubts if you switched to a newer version. Just make a copy of your c:\apn\compil.exe and then download a fresh one, such as:

compil-6.5.886-w32.zip

If that doesn't get us to the bottom of it, I'd be happy to connect to your workstation to debug it directly.

I got the same result. Let me know when you are available and I will provide you access.

> "c:\vm\APN\compil.exe" -ini L:\apn.ini -w:4000 -x:2 -m -px -lf -lsm -so "L:\dsk90\060201\emvdsp.bas"
Compil 6.5(886)
emvdsp.bas,1,Unable to find ++INCLUDE file ,++INCLUDE SYSTEM.MAP
emvdsp.bas,2,Unable to find ++INCLUDE file ,++INCLUDE DATE.MAP
emvdsp.bas,3,Unable to fin

The -ini file I use resides in the samba share on my linux server and my devices were reference using the format, DEVICE=DSK90/vm/miame/dsk90/, which does not work with APN. I then change the format to
DEVICE=DSK90 L:\dsk90\ and was able to access my share library and INCLUDE files.

Jack, thanks for your assistance.