Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Hello Esteemed Monks,

I have an app using Tk's main window integrated with Term::ReadLine::Gnu in the terminal window. I would like to be able to clean up before exiting on Ctrl-C issued in either window.

With main window focus, I use Tk::bind to associate Ctrl-C with a callback (\&abort) that exits via CORE::exit. Although this causes a hard landing (segfault), the terminal functions normally afterwards.

With terminal window focus, the signal handler exits in the same way, however, after exiting, the terminal fails to echo the characters I type. Leaving via Tk::exit() results in the same echoless state, regardless of how it is invoked.

I suspect the line $OUT = $term->OUT || \*STDOUT (which I cut and pasted) of doing some redirection.

Update:This line provides an output filehandle, however all of my print statements output correctly without writing print $OUT $something.

I also looked at the Term::ReadLine methods such as rl_reset_terminal() without finding a solution.

Update: Issuing $term->rl_deprep_terminal() before exit() appears to solve the problem. (c.f 'man readline')

Here is my (revised) code:

use Tk; my $mw = MainWindow->new; $mw->bind('<Control-Key-c>' => \&abort); use Term::ReadLine; $SIG{INT} = \&abort; my $term = new Term::ReadLine(); loop(); sub loop { $term->tkRunning(1); $OUT = $term->OUT || \*STDOUT; while (1) { my ($user_input) = $term->readline("input>") ; process_line( $user_input ); } } sub abort { # do some cleanup $term->rl_deprep_terminal(); # Update! CORE::exit(); } sub process_line { print "user input: $_[0]\n" }
Update: Including $term->rl_deprep_terminal() in &abort appears sufficient to terminate the application.

In reply to Echoless terminal state after exiting Tk/Term::ReadLine event loop (Solved!) by gnosti

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others chanting in the Monastery: (10)
    As of 2018-06-22 15:51 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (124 votes). Check out past polls.