> For the complete documentation index, see [llms.txt](https://everedit.gitbook.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://everedit.gitbook.io/doc/cli.md).

# Command line parameters

EverEdit support several command line parameters, you can work with other programs easily on top of these parameters.

* -n: (-n10:20), Move cursor to specified line and column when opening a file, column is optional.
* -h: Don't add opened files to MRU (most recently used file)
* -e: Force encoding, example: `utf8: -e65001, Chinese: -e936, Japanese: -e932`
* -s: Syntax highlight, example: `-s"HTML"`
* -r: Read-only mode
* -i: Create a new instance of EverEdit
* -c: Clean mode (Don't load plugins and modes)
* -u: Update addons with `update mode`，example: `everedit.exe -u %1`
* -w: working directory, example: `-w"d:/"`

Open a file by relative path:

```
everedit ./test.txt
```


---

# 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:

```
GET https://everedit.gitbook.io/doc/cli.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.