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

If DYALOGLINK is set to a non-existent file, the error message concludes with "Hit Enter" but hitting Enter has no effect #12

Open
dyaandys opened this issue Mar 7, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@dyaandys
Copy link
Contributor

dyaandys commented Mar 7, 2024

Linux example using 64 Unicode, 19.0 Issue 2.

DYALOG_INITSESSION=1 SESSION_FILE= DYALOGLINK=dasfsfdsf /opt/mdyalog/19.0/64/unicode/mapl
[APL starts]
..
Thu Mar 7 19:37:38 2024
Cannot read DYALOGLINK ("dasfsfdsf"). Press Enter.

But nothing happens when you hit Enter .. I suspect that some timeout kicks in eventually.

[Was originally logged as mantis 21226: Starting the interpreter with DYALOGLINK pointing to an invalid folder prompts to you to hit Enter, but nothing happens]

Dyalog 19.0.48958 64-bit Unicode, BuildID 3fbdac4c
OS Linux 5.4.0-169-generic Dyalog/link#187-Ubuntu SMP Thu Nov 23 14:52:28 UTC 2023 x86_64
Link 4.0.17
SALT 2.915
UCMD 2.6
.NET
WS 19.0
Tatin (unavailable)
Cider (unavailable)

@dyaandys dyaandys added the bug Something isn't working label Mar 7, 2024
@abrudz abrudz transferred this issue from Dyalog/link Dec 16, 2024
@dyavc
Copy link

dyavc commented Jan 24, 2025

K, a customer, also reports this issue.

I tried with 19.0.50771 64-bit Unicode, on MS Windows 10, you don't see anything and Dyalog just exits.

K writes: There are several lines in the function StartupSession (which comes from "C:\Program Files\Dyalog\Dyalog APL-64 19.0
Unicode\StartupSession.aplf")
giving the user the impression that she has time and is supposed to press before anything can happen, but that is not true.

For example:

[66] ⍞←'Cannot read DYALOGLINK ("',dl,'"). Press Enter.'
[67] ⎕DL 5 ⋄ ⎕OFF 1

Whether the user presses or not does not matter, after 5 seconds ⎕OFF is executed, fullstop.

That can't be right and needs fixing.

While we are at it: I am not sure that it is a good idea to put ⎕DL and ⎕OFF on a single line, because that means the user cannot stop ⎕OFF from being executed, even when she interrupts the ⎕DL with an interrupt. ⎕OFF would only be executed faster. Is that really wise?

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