Skip to content

Commit

Permalink
Minor formatting fixes
Browse files Browse the repository at this point in the history
  • Loading branch information
citizenmatt committed Jun 9, 2017
1 parent 50f5b3d commit c307eb5
Show file tree
Hide file tree
Showing 5 changed files with 5 additions and 17 deletions.
2 changes: 1 addition & 1 deletion basics/getting_started/deploying_plugin.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ Before your custom plugin can be used, it must be deployed: built, installed, an
To deploy a plugin:

* Make your project by invoking **Build \| Make Project**.
* Prepare your plugin for deployment. In the main menu, select **Build \| Prepare Plugin Module '<module name>' for Deployment**.
* Prepare your plugin for deployment. In the main menu, select **Build \| Prepare Plugin Module '\<module name\>' for Deployment**.

![Prepare Plugin for Deployment](deploying_plugin/img/prepare_plugin_for_deployment.png)

Expand Down
2 changes: 1 addition & 1 deletion basics/plugin_structure/plugin_dependencies.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ In your plugin, you may depend on classes from other plugins, either bundled, th

* Add the jars of the plugin you're depending on to the classpath of your *IntelliJ Platform SDK*.

> **warning** Do not add the plugin jars as a library: this will fail at runtime because IntelliJ Platform will load two separate copies of the dependency plugin classes.
> **warning** Do not add the plugin jars as a library: this will fail at runtime because IntelliJ Platform will load two separate copies of the dependency plugin classes.
* Add a `<depends>` tag to your plugin.xml, adding the ID of the plugin you're depending on as the contents of the tag.
For example:
Expand Down
7 changes: 1 addition & 6 deletions reference_guide/localization_guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,12 +30,7 @@ tool for more details.

Property values mostly follow MessageFormat rules.

**Note**:

Due to historic reasons main menu, toolbar, popup menus and other actions have their mnemonic char prefixed with
'\_' (underscore) char while all other mnemonics like those for checkboxes, buttons etc use '&' (ampersand) sign for the same purpose.
Moreover one can encounter && (double ampersand) in some places, which denote alternative mnemonic to be used under MacOS X (mnemonics mapped to U, I, O N chars won't work there).
Generally, use the same mnemonic denotation used in original property value and everything will be OK.
> **Note** Due to historic reasons main menu, toolbar, popup menus and other actions have their mnemonic char prefixed with `\_` (underscore) char while all other mnemonics like those for checkboxes, buttons etc. use `&` (ampersand) sign for the same purpose. Moreover one can encounter `&&` (double ampersand) in some places, which denote alternative mnemonic to be used under MacOS X (mnemonics mapped to `U`, `I`, `O`, `N` chars won't work there). Generally, use the same mnemonic denotation used in original property value and everything will be OK.
## Components Location

Expand Down
7 changes: 1 addition & 6 deletions reference_guide/vcs_integration_for_plugins.md
Original file line number Diff line number Diff line change
Expand Up @@ -116,12 +116,7 @@ There are two main kinds of changelists:
For VCSes which use per-file commit (like CVS), the plugin can use heuristics to group a sequence of individual file commits into a
[CommittedChangeList](upsource:///platform/vcs-api/src/com/intellij/openapi/vcs/versionBrowser/CommittedChangeList.java)

**Note**:

```
The *Unversioned Files*, *Locally Deleted Files* etc. nodes in the *Changes* view are not actually changelists,
and files under those nodes are not represented by Change objects.
```
> **Note** The *Unversioned Files*, *Locally Deleted Files* etc. nodes in the *Changes* view are not actually changelists, and files under those nodes are not represented by Change objects.
## Plugin Components

Expand Down
4 changes: 1 addition & 3 deletions user_interface_components/popups.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,9 +50,7 @@ Once you've created the popup, you need to display it by calling one of the `sho
You can let the IntelliJ Platform automatically choose the position based on the context, by calling `showInBestPositionFor()`, or specify the position explicitly through methods like `showUnderneathOf()` and `showInCenterOf()`.


**Note:**

> The `show()` methods return immediately and do not wait for the popup to be closed.
> **Note:** The `show()` methods return immediately and do not wait for the popup to be closed.
If you need to perform some action when the popup is closed, you can either attach a listener to it using the `addListener()` method, override a method of the popup contents such as
[PopupStep.onChosen()](upsource:///platform/platform-api/src/com/intellij/openapi/ui/popup/PopupStep.java),
Expand Down

0 comments on commit c307eb5

Please sign in to comment.