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

Export refuses to export LX, with less than helpful message #639

Open
mkromberg opened this issue Mar 16, 2024 · 1 comment
Open

Export refuses to export LX, with less than helpful message #639

mkromberg opened this issue Mar 16, 2024 · 1 comment
Labels
bug Something isn't working
Milestone

Comments

@mkromberg
Copy link
Contributor

  myns.⎕LX←'lx'
  ]link.export myns.⎕LX c:\tmp\myns

ERRORS ENCOUNTERED: ⎕SE.Link.Export: Not a properly named namespace: #.myns.⎕LX

It should be possible to explicitly export any system variable, even if it does not have namespace scope. Or at least improve the error message.

@mkromberg mkromberg added the bug Something isn't working label Mar 16, 2024
@mkromberg mkromberg added this to the Link 5.0 milestone Mar 16, 2024
@abrudz
Copy link
Contributor

abrudz commented Apr 2, 2024

Not any, but we can allow workspace (not session!) scope sysvars with a warning and the condition that Import and Create refuse to bring in this folder into any other namespace than #.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants