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
No explicit ^D and no newline after ^D in the REPL in Rakudo #1393
Comments
From @masakkaye:~ masak$ perl6
Compare irb and python: $ irb
kaye:~ masak$ python
Irb shows a '^D'. Python does both that and puts in an extra newline |
From @cokeOn Fri, Nov 6, 2009 at 11:50 AM, Carl Mäsak
To provide another interactive shell example (but not a vote): (I hit ^D after the %) $ tclsh8.5 -- |
The RT System itself - Status changed from 'new' to 'open' |
From @japhbI have always preferred the look that masak++ suggests: ^D or ^C or ^Z -'f |
From @moritzNow a EOF (Ctrl+D) is answered with a newline, and the REPL exits. Closing without spectests, because the REPL isn't specced. |
@moritz - Status changed from 'open' to 'resolved' |
From @masakOn Sat Oct 01 04:22:04 2011, moritz wrote:
As the original submitter, I'm reopening the ticket because only one of |
@masak - Status changed from 'resolved' to 'open' |
From @masakOn Sat Oct 01 15:16:23 2011, masak wrote:
...and now, in 2013, we have neither "^D" nor newline. |
From @ShimmerFairyNone of the interpreters I tried (which include irb, python, python3, and ghci) show "^D" upon pressing Ctrl-D, so I don't think this is something the Perl 6 REPL should do. Whether it should print a newline or not is still a question, however (currently it doesn't, the other interpreters I tried do). |
From @cokeOn Sat Jul 18 08:07:40 2015, lue wrote:
Here's my REPL today, first exiting with ^D. $ perl6
$ Then with exit: $ perl6
I think this meets the criteria of the original request. Closable with tests. -- |
From @zoffixznetPer http://irclog.perlgeek.de/perl6/2016-07-07#i_12800728, suggestion was to ask masak whether the ticket has been resolved. They responded that it has: http://irclog.perlgeek.de/perl6/2016-07-08#i_12806773 Tests added in Raku/roast@dbb6a58a34 |
@zoffixznet - Status changed from 'open' to 'resolved' |
From @zoffixznetFudging tests and reopening as the output actually differs on OSX: # Failed test 'stdout is correct' Tests fudged in Raku/roast@5e25756c3f |
@zoffixznet - Status changed from 'resolved' to 'open' |
Can someone confirm this test still fails on OSX? |
|
So, can we safely close it? Is it properly addressed? |
Closing it too, since it's been addressed in OSX, as proved by @coke |
Migrated from rt.perl.org#70297 (status was 'open')
Searchable as RT70297$
The text was updated successfully, but these errors were encountered: