> For the complete documentation index, see [llms.txt](https://manual.egclinea.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.egclinea.com/beskeder/skaermbillede_beskeder/vertikal-visning_beskeder.md).

# Vertikal visning

For bedre udnyttelse af widescreen kan skiftes til vertikal visning, hvor læseruden er placeret ude til højre i stedet for nederst i skærmbilledet.

Det forudsætter **indstillingen** **Beskeder → Visning → 'Vis vertikalt'** har sat markering i '*Aktiveret*'. Læs mere om, hvordan en indstilling kan ændres [her](/tips_og_tricks/tilpas_indstillinger.md).

Første gang modulet åbnes efter indstillingen er sat til vertikal visning, skal skillelinjerne justeres med musen ved at trække i området med 'prikker' på bjælken.

## Specielt ved vertikal visning

I den vertikale visning fylder hver besked 2 linjer. Der kan søges i samtlige meddelelser på samtlige tekstfelter.

Sortering vælges ved højreklik på menuen i headeren. Klik på selve headeren for stigende eller faldende sortering.

Afhængig af hvilken bakke fokus er i, er der en tjekboks ”**Ikke godkendt**” og ”**Ikke overført**”. De kan bruges som et hurtigt filter. Indstilling afgør, hvilken bakke er  standard bakke og om filter skal være sat til eller ej.

## Skærmbillede

![Vertikal visning](https://3548167157-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfDHx4SrlSNAKGCJ3m7yH%2Fuploads%2Fgit-blob-8c25788d6442e1a72fb2bb0de5abb2d0c700cffe%2Fhmfile_hash_1ea26281.png?alt=media)


---

# 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://manual.egclinea.com/beskeder/skaermbillede_beskeder/vertikal-visning_beskeder.md?ask=<question>&goal=<user_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.