| /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/editors/ui/tree/ |
| UiTreeBlock.java | 529 // Paste is not valid if it would add a second element on a terminal element
[all...] |
| /external/pcre/ |
| pcregrep.c | 386 /************* Test for a terminal in Unix **********/
513 /************* Test for a terminal in Win32 **********/
551 /************* Test for a terminal when we can't do it **********/
[all...] |
| /prebuilt/linux-x86/toolchain/arm-eabi-4.2.1/bin/ |
| arm-eabi-gdb | |
| /prebuilt/linux-x86/toolchain/arm-eabi-4.3.1/bin/ |
| arm-eabi-gdb | |
| arm-eabi-gdbtui | |
| /prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/ |
| arm-eabi-gdb | |
| arm-eabi-gdbtui | |
| /prebuilt/linux-x86/toolchain/i686-unknown-linux-gnu-4.2.1/bin/ |
| i686-unknown-linux-gnu-gdb | |
| i686-unknown-linux-gnu-gdbtui | |
| /prebuilt/darwin-x86/toolchain/arm-eabi-4.2.1/info/ |
| standards.info | 636 terminal), it is better not to include the program name in an error
639 input from a source other than a terminal, it is not interactive and
667 message syntax when using a terminal is ok, because that is a side issue
671 terminal, and another is most useful when the output is a file or a
673 is useful with output to a terminal, and have an option for the other
[all...] |
| /prebuilt/darwin-x86/toolchain/arm-eabi-4.3.1/info/ |
| standards.info | 636 terminal), it is better not to include the program name in an error
639 input from a source other than a terminal, it is not interactive and
667 message syntax when using a terminal is ok, because that is a side issue
671 terminal, and another is most useful when the output is a file or a
673 is useful with output to a terminal, and have an option for the other
[all...] |
| /prebuilt/darwin-x86/toolchain/arm-eabi-4.4.0/info/ |
| standards.info | 723 terminal), it is better not to include the program name in an error
726 input from a source other than a terminal, it is not interactive and
755 message syntax when using a terminal is ok, because that is a side issue
759 terminal, and another is most useful when the output is a file or a
[all...] |
| /prebuilt/darwin-x86/toolchain/arm-eabi-4.4.0/share/info/ |
| standards.info | 636 terminal), it is better not to include the program name in an error
639 input from a source other than a terminal, it is not interactive and
667 message syntax when using a terminal is ok, because that is a side issue
671 terminal, and another is most useful when the output is a file or a
673 is useful with output to a terminal, and have an option for the other
[all...] |
| /prebuilt/darwin-x86/toolchain/arm-eabi-4.4.3/info/ |
| standards.info | 723 terminal), it is better not to include the program name in an error
726 input from a source other than a terminal, it is not interactive and
755 message syntax when using a terminal is ok, because that is a side issue
759 terminal, and another is most useful when the output is a file or a
[all...] |
| /prebuilt/darwin-x86/toolchain/arm-eabi-4.4.3/share/info/ |
| standards.info | 723 terminal), it is better not to include the program name in an error
726 input from a source other than a terminal, it is not interactive and
755 message syntax when using a terminal is ok, because that is a side issue
759 terminal, and another is most useful when the output is a file or
[all...] |
| /prebuilt/darwin-x86/toolchain/arm-linux-androideabi-4.4.x/share/info/ |
| standards.info | 723 terminal), it is better not to include the program name in an error
726 input from a source other than a terminal, it is not interactive and
755 message syntax when using a terminal is ok, because that is a side issue
759 terminal, and another is most useful when the output is a file or
[all...] |
| /prebuilt/linux-x86/toolchain/arm-eabi-4.2.1/info/ |
| standards.info | 636 terminal), it is better not to include the program name in an error
639 input from a source other than a terminal, it is not interactive and
667 message syntax when using a terminal is ok, because that is a side issue
671 terminal, and another is most useful when the output is a file or a
673 is useful with output to a terminal, and have an option for the other
[all...] |
| /prebuilt/linux-x86/toolchain/arm-eabi-4.3.1/info/ |
| standards.info | 636 terminal), it is better not to include the program name in an error
639 input from a source other than a terminal, it is not interactive and
667 message syntax when using a terminal is ok, because that is a side issue
671 terminal, and another is most useful when the output is a file or a
673 is useful with output to a terminal, and have an option for the other
[all...] |
| /prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/info/ |
| standards.info | 723 terminal), it is better not to include the program name in an error
726 input from a source other than a terminal, it is not interactive and
755 message syntax when using a terminal is ok, because that is a side issue
759 terminal, and another is most useful when the output is a file or a
[all...] |
| /prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/share/info/ |
| standards.info | 635 terminal), it is better not to include the program name in an error
638 input from a source other than a terminal, it is not interactive and
666 message syntax when using a terminal is ok, because that is a side issue
670 terminal, and another is most useful when the output is a file or a
672 is useful with output to a terminal, and have an option for the other
[all...] |
| /prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/info/ |
| standards.info | 723 terminal), it is better not to include the program name in an error
726 input from a source other than a terminal, it is not interactive and
755 message syntax when using a terminal is ok, because that is a side issue
759 terminal, and another is most useful when the output is a file or a
[all...] |
| /prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/share/info/ |
| standards.info | 723 terminal), it is better not to include the program name in an error
726 input from a source other than a terminal, it is not interactive and
755 message syntax when using a terminal is ok, because that is a side issue
759 terminal, and another is most useful when the output is a file or
[all...] |
| /prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/share/info/ |
| standards.info | 723 terminal), it is better not to include the program name in an error
726 input from a source other than a terminal, it is not interactive and
755 message syntax when using a terminal is ok, because that is a side issue
759 terminal, and another is most useful when the output is a file or
[all...] |
| /prebuilt/linux-x86/toolchain/i686-unknown-linux-gnu-4.2.1/info/ |
| standards.info | 636 terminal), it is better not to include the program name in an error
639 input from a source other than a terminal, it is not interactive and
667 message syntax when using a terminal is ok, because that is a side issue
671 terminal, and another is most useful when the output is a file or a
673 is useful with output to a terminal, and have an option for the other
[all...] |
| /external/chromium/sdch/open-vcdiff/src/gtest/ |
| gtest.cc | 145 "being sent to a terminal and the TERM environment variable "
[all...] |
