Lines Matching refs:TTY
202 =item * TTY
204 the TTY to use for debugging i/o.
208 if set, goes in NonStop mode. On interrupt, if TTY is not set,
209 uses the value of noTTY or "/tmp/perldbtty$$" to find TTY using
210 Term::Rendezvous. Current variant is to have the name of TTY in this
260 Used to control when the debugger will attempt to acquire another TTY to be
805 # + Support for auto-creation of new TTY window on startup, either
808 # I<CreateTTY> bits control attempts to create a new TTY on events:
812 # + Code to auto-create a new TTY window on OS/2 (currently one
815 # compatibility hack); now returns the TTY name to use; return of ''
818 # + Convert the existing code to create a TTY into a custom createTTY
820 # + Consistent support for TTY names of the form "TTYin,TTYout";
821 # + Switch line-tracing output too to the created TTY window;
1007 AutoTrace TTY noTTY
1056 TTY => \&TTY,
1112 =item C<$CreateTTY> - whether or not to create a new TTY for this debugger
1203 TTY later.
1210 PERLDB_PIDS plus the new PID. They also mark themselves as not having a TTY
1230 # more TTY's is we have to.
1424 If there's no TTY, we set the debugger to run non-stop; there's not going
1435 If there is a TTY, we have to determine who it belongs to before we can
1539 If there is a TTY hanging around from a parent, we use that as the console.
1572 If no C<RemotePort> was defined, and we want to create a TTY on startup,
1575 OUT filehandle, and do the necessary mojo to create a new TTY if we know how
5701 =head1 TTY MANAGEMENT
5727 # If noTTY is set, but we have a TTY name, go ahead and hook up to it.
5732 open(IN, "<$i") or die "Cannot open TTY `$i' for read: $!";
5733 open(OUT, ">$o") or die "Cannot open TTY `$o' for write: $!";
5741 # We don't have a TTY - try to find one via Term::Rendezvous.
5756 # We're a daughter debugger. Try to fork off another TTY.
5757 if ($term_pid eq '-1') { # In a TTY with another debugger
5805 TTY (and probably another window) and to direct the new debugger to read and
5820 command (which prints the device name of the TTY we'll want to use for input
5823 is STDOUT from the I<commands> we ran) to get the TTY we want to use.
5842 # There's our new TTY.
5916 Create a new pair of filehandles, pointing to a new TTY. If impossible,
5923 =item * 1 - Don't know how to create a new TTY.
5925 =item * 2 - Debugger has forked, but we can't get a new TTY.
5935 # If we know how to get a new TTY, do it! $in will have
5936 # the TTY name if get_fork_TTY works.
5947 I<#########> Forked, but do not know how to create a new B<TTY>. I<#########>
5952 I<#########> Daughter session, do not know how to change a B<TTY>. I<#########>
5958 Since two debuggers fight for the same TTY, input is severely entangled.
5963 and OS/2 consoles only. For a manual switch, put the name of the created I<TTY>
5966 On I<UNIX>-like systems one can get the name of a I<TTY> for the given window
5967 by typing B<tty>, and disconnect the I<shell> from I<TTY> by B<sleep 1000000>.
5972 TTY($in);
5999 sub resetterm { # We forked, so we need a different TTY
6024 # Just return if we're not supposed to try to create a new TTY.
6202 pager quote ReadLine recallCommand RemotePort ShellBang TTY CommandSet
6391 =head1 INITIALIZATION TTY SUPPORT
6434 =head2 C<TTY>
6446 sub TTY {
6448 # This terminal supports switching to a new TTY.
6473 # Terminal doesn't support new TTY, or doesn't support readline.
6475 &warn("Too late to set TTY, enabled on next `R'!\n") if $term and @_;
6480 # Return whatever the TTY is.
6482 } ## end sub TTY
6890 I<CreateTTY> bits control attempts to create a new TTY on events:
6894 You can put additional initialization options I<TTY>, I<noTTY>,
7066 I<CreateTTY> bits control attempts to create a new TTY on events:
7070 You can put additional initialization options I<TTY>, I<noTTY>,