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

Pressing Ctrl + D spams iron> in the console #36

Open
KristofferC opened this issue Mar 21, 2019 · 8 comments
Open

Pressing Ctrl + D spams iron> in the console #36

KristofferC opened this issue Mar 21, 2019 · 8 comments

Comments

@KristofferC
Copy link
Contributor

iron

@oxinabox
Copy link
Owner

oxinabox commented Mar 21, 2019

Can you do versioninfo() for me?

This is the return of #13 (which related to JuliaLang/julia#30790)
which was closed in #15

@KristofferC
Copy link
Contributor Author

julia> versioninfo()
Julia Version 1.1.0
Commit 80516ca202 (2019-01-21 21:24 UTC)
Platform Info:
  OS: Linux (x86_64-pc-linux-gnu)
  CPU: Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-6.0.1 (ORCJIT, skylake)

I updated to latest master of MagneticReadHead and tried again but same thing.

@oxinabox
Copy link
Owner

As an aside what did you expect Ctrl+d to do?
My instinct says Continue, does that align with yours?

@KristofferC
Copy link
Contributor Author

I expected it to exit the debugger.

@oxinabox
Copy link
Owner

But should it keep running the function (Continue)
or should it terminate imediately (Abort)

@KristofferC
Copy link
Contributor Author

I think abort everything and give julia prompt. That was my intention but it doesn't mean it is the best choice :).

@oxinabox
Copy link
Owner

I think you are right,.
It means I am done,
e.g. when I press it in julia I exit julia.

@oxinabox
Copy link
Owner

I can't reproduce this on


julia> versioninfo()
Julia Version 1.1.0
Commit 80516ca202 (2019-01-21 21:24 UTC)
Platform Info:
  OS: macOS (x86_64-apple-darwin14.5.0)
  CPU: Intel(R) Core(TM) i7-8559U CPU @ 2.70GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-6.0.1 (ORCJIT, skylake)

asciicast

You didn't by any chance do something like include(test/runtests.jl) before running it?
(A side-effect of how that takes control of readline is when it relinquishes control it doesn't reenable to the protections against this.)

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