> For the complete documentation index, see [llms.txt](https://ploegert.gitbook.io/til/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ploegert.gitbook.io/til/tools/vim/interact-with-the-alternate-file.md).

# Interact With The Alternate File

If you have a couple buffers going in a Vim session and you check out the buffer list with `:ls`, you'll notice that one of those buffers has a `#` indicator next to it. That means the file for this buffer is considered the alternate file of the current, visible buffer. In addition to hitting `CTRL-^` to switch to that buffer, you can reference it in other commands with `#`. This means you can quickly `:edit`, `:split`, `:vsplit`, and so forth the alternate file by just giving `#` as the argument to those commands.

Quickly open the alternate file in a vertical split with:

```
:vsp #
```

See `:h alternate-file` for more details.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ploegert.gitbook.io/til/tools/vim/interact-with-the-alternate-file.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
