Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatic source dep. with a relative path for all files #345

Closed
Giupeppe999 opened this issue Sep 24, 2024 · 7 comments
Closed

Automatic source dep. with a relative path for all files #345

Giupeppe999 opened this issue Sep 24, 2024 · 7 comments

Comments

@Giupeppe999
Copy link

My source dependency files are always in the same scheme of path that change depending on the name and on the position of the file.

The path could be compose with the vscode variables in this way:
${relativeFileDirname}/CBL/${fileBasenameNoExtension}.CBL
(resolved is SL/E28/CBL/PROGRAM.CBL)

Is possible to set this path (with vscode vars) automatically for all of files that end for example with "*.DD" and the extension considers the resolved one (without vars but values)?

THANK YOU, sorry if i am disturbing you a lot.

@spgennard
Copy link
Owner

Why dont you use the copybookdirs setting?

@Giupeppe999
Copy link
Author

Because there is one file source dependency for only one source file not for all files. And is not a copybook but a compiled resutl file by preprocessor.

@spgennard
Copy link
Owner

A source-dependancy is a copybook that is included via a comment.

Referencing a listing file will bring in more items than is required and should be avoided, which may well break the structure program.

Only include the items you need, and as rule of thumb source-dependencies and copybooks are interchangeable.

@Giupeppe999
Copy link
Author

Giupeppe999 commented Sep 24, 2024

In the source files the source dep. is not referenced by "COPY" statement, and if i add the directory in copybookdirs, it doesn't do nothing, so i'm using for every file the source-dependency comment and it works as well as possible.
But for every source i must add the comment, and i have a lot of source files.
So this is the reason why i want to declare a relative path to include the source dependecy in every file, without writing the file everytime.

@spgennard
Copy link
Owner

Relative paths are not portable as vscode uses urls under the covers, as it works in the browser.

@Giupeppe999
Copy link
Author

Giupeppe999 commented Sep 24, 2024

ok so if you cannot do anything i close this issue, but please resolve this in the last comment IS IMPORTANT for us:
#343 (comment)

@Giupeppe999
Copy link
Author

closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants