> 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/ida-9.5/core/disassembler/how-tos/hiding-and-collapsing.md).
# Hiding and collapsing output
The menu items **View → Hide** and **View → Unhide** allow the user to hide/collapse and unhide/uncollapse part of IDA's output.
## Hiding instructions or data items
It is possible to hide or replace some parts of the listing by a short text.
To do so:
1. Select some instructions or data items
2. Invoke **View → Hide** (or Ctrl+Numpad-)
3. Enter the replacement text and optionally pick a color.
The selected instructions, or data, are replaced by the entered text. They are not removed from the database. They can be made visible again by using **View → Unhide** (or Ctrl+Numpad+)
## Hiding a whole function
To hide a whole function, place the cursor on the function name, then **View → Hide** (or Ctrl+Numpad-). You can also right-click on the function as shown below:
## Terse struct representation
When defining structure instances in data, IDA will, by default, try to display them in terse form, with everything on one line. By using **Unhide**, you can have it in full, or verbose form, with each field on a separate line and a comment with the field name. Conversely, you can use **Hide** to collapse a structure instance into a terse form. Note that it may not work due to the specific structure's layout.
## Collapsing blocks in the decompiler
The decompiler also has a similar pair of actions. They are available via the context menu or the **Numpad-** and **Numpad+** hotkeys.
---
# 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/ida-9.5/core/disassembler/how-tos/hiding-and-collapsing.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.