mirror of
https://github.com/JetBrains/intellij-sdk-code-samples.git
synced 2025-07-30 02:07:50 +08:00
4e802980f2
* [webhelp] Fixes for TXP00152, TXP00002, test build 27 Jul 22:26 * [webhelp] Fixes for Part #4 TXP00010, EXCEPT decimal numbers in section titles * [webhelp] Fixes for Part #5 TXP00017 * [webhelp] Fixes for Part #4 TXP00010 - removed numbers from page section titles in "Custom Language Support Tutorial" and "Testing a Custom Language Plugin". * [webhelp] Removed numbers from page section titles in rest of project *.md files. * [new webhelp] Build #44 changes * [new webhelp] Maintenance merge from master * [new webhelp] Add placeholder file for webhelp import. * [webhelp] Correct redirects for file name changes * [webhelp] TOC not needed in webhelp * [format] {:toc} not needed for webhelp * add {:disable-links} to ensure demo links are not interpreted as real links. * Put all badges on the same line to simplify composition. * formatter.md: fix upsource link * fix some links * api_changes_list.md: remove note * migrate to webhelp - initial * fix GH edit URL * remove sdkdocs-template setup in VCS config * remove recently_updated.md * restore COC/CONTRIBUTING.md * api_changes_list.md: remove note * useful_links.md: IPE Co-authored-by: JohnHake <john.hake@jetbrains.com> Co-authored-by: Yann Cébron <yann.cebron@jetbrains.com>
66 lines
4.0 KiB
Markdown
66 lines
4.0 KiB
Markdown
[//]: # (title: Documents)
|
|
|
|
<!-- Copyright 2000-2020 JetBrains s.r.o. and other contributors. Use of this source code is governed by the Apache 2.0 license that can be found in the LICENSE file. -->
|
|
|
|
A [`Document`](upsource:///platform/core-api/src/com/intellij/openapi/editor/Document.java) is an editable sequence of Unicode characters, typically corresponding to the text contents of a [virtual file](virtual_file.md).
|
|
|
|
Line breaks in a document are _always_ normalized to `\n`.
|
|
The *IntelliJ Platform* handles encoding and line break conversions when loading and saving documents transparently.
|
|
|
|
## How do I get a document?
|
|
|
|
From an action
|
|
: `e.getData(PlatformDataKeys.EDITOR).getDocument()`
|
|
|
|
From a virtual file
|
|
: `FileDocumentManager.getDocument()`. This call forces the document content to be loaded from disk if it wasn't loaded previously. If only open documents or documents which may have been modified are considered relevant, use `FileDocumentManager.getCachedDocument()` instead.
|
|
|
|
From a PSI file
|
|
: `PsiDocumentManager.getInstance().getDocument()` or `PsiDocumentManager.getInstance().getCachedDocument()`
|
|
|
|
## What can I do with a Document?
|
|
|
|
You may perform any operations that access or modify the file contents on the "plain text" level (as a sequence of characters, not as a tree of PSI elements).
|
|
|
|
## Where does a Document come from?
|
|
|
|
Document instances are created when some operation needs to access the text contents of a file (in particular, this is necessary to build the PSI for a file).
|
|
Also, document instances not linked to any virtual files can be created temporarily, for example, representing the contents of a text editor field in a dialog.
|
|
|
|
## How long does a Document persist?
|
|
|
|
Document instances are weakly referenced from `VirtualFile` instances.
|
|
Thus, an unmodified `Document` instance can be garbage-collected if no one references it, and a new instance is created if the document contents are reaccessed later.
|
|
|
|
> Storing `Document` references in long-term data structures of a plugin will cause memory leaks.
|
|
>
|
|
{type="warning"}
|
|
|
|
## How do I create a Document?
|
|
|
|
For creating a new file on disk, please do not create a `Document` but a PSI file and get its `Document`.
|
|
To create a `Document` instance that isn't bound to anything, use `EditorFactory.createDocument()`.
|
|
|
|
## How do I get notified when Documents change?
|
|
|
|
* `Document.addDocumentListener()` allows receiving notifications about changes in a particular `Document` instance.
|
|
* `EditorFactory.getEventMulticaster().addDocumentListener()` allows receiving notifications about changes in all open documents.
|
|
* Subscribe to `AppTopics.FILE_DOCUMENT_SYNC` on any level bus to receive notifications when a `Document` is saved or reloaded from disk.
|
|
|
|
## What are the rules of working with Documents?
|
|
|
|
The general read/write action rules are in effect.
|
|
Besides, any operations which modify the contents of the document must be wrapped in a command (`CommandProcessor.getInstance().executeCommand()`).
|
|
`executeCommand()` calls can be nested, and the outermost `executeCommand()` call is added to the undo stack.
|
|
If multiple documents are modified within a command, undoing this command will, by default, show a confirmation dialog to the user.
|
|
|
|
If the file corresponding to a `Document` is read-only (for example, not checked out from the version control system), document modifications will fail.
|
|
Thus, before modifying the `Document`, it is necessary to call `ReadonlyStatusHandler.getInstance(project).ensureFilesWritable()` to check out the file.
|
|
|
|
All text strings passed to `Document` modification methods (`setText()`, `insertString()`, `replaceString()`) must use only `\n` as line separators.
|
|
|
|
## Are there any utilities available for working with Documents?
|
|
|
|
[`DocumentUtil`](upsource:///platform/core-impl/src/com/intellij/util/DocumentUtil.java) contains utility methods for `Document` processing.
|
|
This allows you to get information like the text offsets of particular lines.
|
|
This is particularly useful when you need text location/offset information about a given `PsiElement`. |