> 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/user-interface/concepts/list-viewers.md).
# List Viewers
Some views, known as *choosers*, are a specific type of view called **list viewers**. They have interactive content that you can modify and manipulate.
## List Viewer Commands and Navigation
The following commands work in the list viewers:
1\. All usual movement keys: PgUp, PgDn, Home, End and arrows (↑ ↓ → ←).
2\. Typing filters the list. See [Typing in a list](#typing-in-a-list) below.
3\. Alt+T search for a substring (case-insensitive). Ctrl+T repeat last search. The search moves the selection and does not filter the list.
4\. If the list is not in dialog mode, you can use the following keys:
* Enter: jump to the selected item in the last IDA View window
* Ctrl+E: edit the current item
* Del delete the current item
* Ins insert a new item
* Ctrl+U refresh information in the window
5\. Ctrl+F puts the focus in the filter bar. More complex filters can be defined with a right click (only the GUI mode).
6\. The list can be sorted by any column by clicking on it. Please note that maintaining a frequently modified list sorted can be very time consuming, so try not to sort non-modal lists during the initial analysis. (sorting is available only in the GUI mode).
7\. Right-click may show additional functionality for the list viewer.
Esc or Enter close modal list viewers.
## Typing in a list
Typing in a list viewer (Functions, Names, Imports, Local Types, ...) filters it. The filter bar at the bottom of the list is always visible, so it is clear where your typing goes.
* The first key you type goes into the filter bar, and the filter bar keeps the focus for the keys after it. The list shows only the rows that match.
* A key that is bound to an action does that action and does not go into the filter. When the filter bar has the focus, the same key is typed as text.
* Space toggles check boxes in lists that have them.
* When the filter bar has the focus, ↑ / ↓ / PgUp / PgDn move the selection in the list, and Enter acts on the selected row. Esc puts the focus back in the list and keeps the filter.
* To remove the filter, delete its text.
* Right-click the filter bar to select how the text matches: match case, whole words, regular expression or fuzzy.
* Characters that need AltGr, and the numpad digits, go into the filter too.
Lists that cannot be filtered do not show a filter bar, and typing does not filter them.
### Feature flags
Two [feature flags](/ida-9.5/ida-actions/showfeatureflags.md) control this behavior:
* **Typing in a list filters it**: untick it to search the list incrementally instead of filtering it. See [Incremental search](#incremental-search).
* **Always show the filter bar**: untick it to show the filter bar only when you type or press Ctrl+F. The filter bar then has a close button. This flag is available only while **Typing in a list filters it** is ticked.
### Incremental search
When **Typing in a list filters it** is unticked, typing moves the selection instead of filtering the list:
* Type a line number to go to that line.
* Type the beginning of a line to go to it. Backspace erases the last character typed, Ctrl+Enter finds the next line with the same beginning, and Ctrl+Shift+Enter finds the previous one. The search ignores the beginning of a line up to the last backslash (\\\\) or slash (/), if the line has one.
While a search is in progress, it takes the keys that you type, including keys that are bound to actions.
---
# 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/user-interface/concepts/list-viewers.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.