You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
With existing links to a script file (not a folder), Notify sends Warnings on any changes in the files folder.
This doesn´t happen, when only folders are linked.
Link Warning: ⎕SE.Link.Notify: created F:/Test/Code/Data/test.csv: path not in a linked directory
Link Warning: ⎕SE.Link.Notify: created F:/Test/Code/Data/test.csv: path not in a linked directory
Link Warning: ⎕SE.Link.Notify: changed F:/Test/Code/Data/test.csv: path not in a linked directory
Link Warning: ⎕SE.Link.Notify: changed F:/Test/Code/Data/test.csv: path not in a linked directory
Expected behaviour
I would not expect a warning in this case, because the Data folder is not linked. Only single files in its parent folder are linked.
Desktop :
OS: Windows
APL version: 19.0 Unicode 64-bit]
⎕SE.Link.Version: 4.0.17
The text was updated successfully, but these errors were encountered:
Describe the bug
With existing links to a script file (not a folder), Notify sends Warnings on any changes in the files folder.
This doesn´t happen, when only folders are linked.
To Reproduce
]LINK.Create 'EXCEL' 'F:\Test\Code\Excel.dyalog'
Linked: #.EXCEL ←→ F:\Test\Code\Excel.dyalog
]LINK.Create 'ADO' 'F:\Test\Code\ADO.apln'
Linked: #.ADO ←→ F:\Test\Code\ADO.apln
Link Warning: ⎕SE.Link.Notify: created F:/Test/Code/Data/test.csv: path not in a linked directory
Link Warning: ⎕SE.Link.Notify: created F:/Test/Code/Data/test.csv: path not in a linked directory
Link Warning: ⎕SE.Link.Notify: changed F:/Test/Code/Data/test.csv: path not in a linked directory
Link Warning: ⎕SE.Link.Notify: changed F:/Test/Code/Data/test.csv: path not in a linked directory
Expected behaviour
I would not expect a warning in this case, because the Data folder is not linked. Only single files in its parent folder are linked.
Desktop :
⎕SE.Link.Version
: 4.0.17The text was updated successfully, but these errors were encountered: