Lines Matching defs:TTY

215 =item * TTY
217 the TTY to use for debugging i/o.
221 if set, goes in NonStop mode.  On interrupt, if TTY is not set,
222 uses the value of noTTY or F<$HOME/.perldbtty$$> to find TTY using
223 Term::Rendezvous.  Current variant is to have the name of TTY in this
283 Used to control when the debugger will attempt to acquire another TTY to be
952   AutoTrace    TTY           noTTY
1011     TTY           => \&TTY,
1070 =item C<$CreateTTY> - whether or not to create a new TTY for this debugger
1173 TTY later.
1180 PERLDB_PIDS plus the new PID. They also mark themselves as not having a TTY
1217     # more TTY's is we have to.
1482 If there's no TTY, we set the debugger to run non-stop; there's not going
1508 If there is a TTY, we have to determine who it belongs to before we can
1609 If there is a TTY hanging around from a parent, we use that as the console.
1637 If no C<RemotePort> was defined, and we want to create a TTY on startup,
1640 OUT filehandle, and do the necessary mojo to create a new TTY if we know how
6818 =head1 TTY MANAGEMENT
6850     # If noTTY is set, but we have a TTY name, go ahead and hook up to it.
6855             open( IN,  '<', $i ) or die "Cannot open TTY '$i' for read: $!";
6856             open( OUT, '>', $o ) or die "Cannot open TTY '$o' for write: $!";
6862         # We don't have a TTY - try to find one via Term::Rendezvous.
6877     # We're a daughter debugger. Try to fork off another TTY.
6878     if ( $term_pid eq '-1' ) {    # In a TTY with another debugger
6956 TTY (and probably another window) and to direct the new debugger to read and
6999 command (which prints the device name of the TTY we'll want to use for input
7002 is STDOUT from the I<commands> we ran) to get the TTY we want to use.
7033     # There's our new TTY.
7187 Create a new pair of filehandles, pointing to a new TTY. If impossible,
7194 =item * 1 - Don't know how to create a new TTY.
7196 =item * 2 - Debugger has forked, but we can't get a new TTY.
7208     # If we know how to get a new TTY, do it! $in will have
7209     # the TTY name if get_fork_TTY works.
7220 I<#########> Forked, but do not know how to create a new B<TTY>. I<#########>
7225 I<#########> Daughter session, do not know how to change a B<TTY>. I<#########>
7231   Since two debuggers fight for the same TTY, input is severely entangled.
7237   of the created I<TTY> in B<\$DB::fork_TTY>, or define a function
7240   On I<UNIX>-like systems one can get the name of a I<TTY> for the given window
7241   by typing B<tty>, and disconnect the I<shell> from I<TTY> by S<B<sleep 1000000>>.
7246         TTY($in);
7273 sub resetterm {    # We forked, so we need a different TTY
7298     # Just return if we're not supposed to try to create a new TTY.
7500       pager quote ReadLine recallCommand RemotePort ShellBang TTY CommandSet
7706 =head1 INITIALIZATION TTY SUPPORT
7747 =head2 C<TTY>
7759 sub TTY {
7763         # This terminal supports switching to a new TTY.
7790     # Terminal doesn't support new TTY, or doesn't support readline.
7793         _db_warn("Too late to set TTY, enabled on next 'R'!\n");
7799     # Return whatever the TTY is.
7801 } ## end sub TTY
8237     I<CreateTTY>     bits control attempts to create a new TTY on events:
8241     You can put additional initialization options I<TTY>, I<noTTY>,
8413     I<CreateTTY>     bits control attempts to create a new TTY on events:
8417     You can put additional initialization options I<TTY>, I<noTTY>,