> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/8.5/user-guide/disassembler/navigation/how-to-enter-text.md). # How to enter text ``` In the text version of IDA, you can use the following keys: Enter starts a new line Ctrl-Enter finishes the input Esc cancels the input F1 gives some help Shift- Select Ctrl-L Search Again Shift-Ins Paste Ctrl-O Indent Mode Shift-Del Cut Ctrl-T Delete Word Ctrl-Ins Copy Ctrl-U Undo Ctrl-Del Clear Ctrl-Y Delete Line Ctrl-K B Start Select Ctrl-Left Word Left Ctrl-K H Hide Select Ctrl-Right Word Right Ctrl-PgUp Text Start Ctrl-Q A Replace Ctrl-PgDn Text End Ctrl-Q F Search Ctrl-Q H Delete Line Start Ctrl-Q Y Delete Line End ``` Input containing only whitespaces is equal to an empty input. Do not forget that you can also use the clipboard. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.hex-rays.com/8.5/user-guide/disassembler/navigation/how-to-enter-text.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.