mirror of https://gitlab.com/basile.b/dexed.git
docs, use new name
This commit is contained in:
Basile Burg
parent
766389876c
commit
536490ad44
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: Build Coedit
|
||||
title: Build Dexed
|
||||
---
|
||||
|
||||
{% raw %}
|
||||
|
|
@ -8,34 +8,34 @@ title: Build Coedit
|
|||
|
||||
### Build
|
||||
|
||||
#### Coedit
|
||||
#### Dexed
|
||||
|
||||
Coedit is mostly programmed in Object Pascal, using the the [Lazarus development platform](http://www.lazarus-ide.org/).
|
||||
Dexed is mostly programmed in Object Pascal, using the the [Lazarus development platform](http://www.lazarus-ide.org/).
|
||||
|
||||
* [Download](http://lazarus.freepascal.org/index.php?page=downloads) and setup the latest Lazarus version (>= 1.8.0) and FPC + FPC sources (>= 3.0.4) for your platform.
|
||||
* Windows: the three packages are bundled in an installer.
|
||||
* Linux: the three packages must be downloaded and setup individually. It's recommended to download the packages from _SourceForge_ and not from the official repository of the distribution because they don't always propose the latest version.
|
||||
* `cd <user dir where to clone>`
|
||||
* `git clone https://github.com/BBasile/Coedit.git`
|
||||
* `git clone https://github.com/BBasile/dexed.git`
|
||||
* `git submodule update --init --recursive`, to clone the dependencies used by the background tool.
|
||||
|
||||
The Lazarus LCL and the FreePascal FCL may require patches that fix bugs or regressions present in the latest Lazarus release and for which Coedit cannot include workarounds.
|
||||
The Lazarus LCL and the FreePascal FCL may require patches that fix bugs or regressions present in the latest Lazarus release and for which Dexed cannot include workarounds.
|
||||
Any `.patch` file located in the `patches/` folder should be applied. On linux you'll have to set the write permissions to `/usr/lib64/fpc` and `/usr/lib64/lazarus`.
|
||||
|
||||
You're now ready to build Coedit. This can be done in the IDE or using the _lazbuild_ utility.
|
||||
You're now ready to build Dexed. This can be done in the IDE or using the _lazbuild_ utility.
|
||||
|
||||
* If you don't plan to develop the project, use _lazbuild_:
|
||||
* open a console.
|
||||
* `cd` to the repository location, sub folder **lazproj**.
|
||||
* type `lazbuild -B coedit.lpi` and <kbd>ENTER</kbd>. note that the path to _lazbuild_ may have to be specified.
|
||||
* type `lazbuild -B dexed.lpi` and <kbd>ENTER</kbd>. note that the path to _lazbuild_ may have to be specified.
|
||||
|
||||
* If you plan to help developing you'd better get started with _Lazarus_, which is less conveniant:
|
||||
* start Lazarus.
|
||||
* setup `lazproj/cedsgncontrols.lpk` with Lazarus package manager (requires to rebuild Lazarus).
|
||||
* in the **project** menu, click *open...* and select the file **Coedit.lpi**, which is located in the sub-folder **lazproj**.
|
||||
* in the **project** menu, click *open...* and select the file **dexed.lpi**, which is located in the sub-folder **lazproj**.
|
||||
* in the menu **Execute** click **Create**.
|
||||
|
||||
After what Coedit should be build. The executable is output to the _bin_ folder.
|
||||
After what Dexed should be build. The executable is output to the _bin_ folder.
|
||||
|
||||
#### Dastworx
|
||||
|
||||
|
|
|
|||
|
|
@ -23,25 +23,25 @@ The D Completion Daemon (DCD) is used to accomplish IDE-grade features such as
|
|||
|
||||
#### Setup
|
||||
|
||||
_DCD_ is a third part software, it's bundled in the archives distributed for each new [release](https://github.com/BBasile/Coedit/releases).
|
||||
However, _DCD_ may have to be build manually, for example if a new version is released while _Coedit_ development is paused for a while.
|
||||
_DCD_ is a third part software, it's bundled in the archives distributed for each new [release](https://github.com/BBasile/dexed/releases).
|
||||
However, _DCD_ may have to be build manually, for example if a new version is released while _Dexed_ development is paused for a while.
|
||||
Visit the product [homepage](https://github.com/dlang-community/DCD) for more information.
|
||||
|
||||
Once DCD build or extracted from the release archive, copy the two programs (_dcd-client_ and _dcd-server_) to the folder where the Coedit executable stands.
|
||||
Once DCD build or extracted from the release archive, copy the two programs (_dcd-client_ and _dcd-server_) to the folder where the Dexed executable stands.
|
||||
They can be put elsewhere, as long as the target directory is a known operating system PATH.
|
||||
|
||||
#### Imports
|
||||
|
||||
In _Coedit_, _DCD_ relies on the [compilers paths](options_compilers_paths), on the [library manager](widgets_library_manager) entries and on the project parameters. When the [_libman_](widgets_library_manager) is empty then the scope of DCD is limited to the symbols of current module, of the current project sources and of the standard library, that's why it necessary to register the development libraries used in the _libman_.
|
||||
In _Dexed_, _DCD_ relies on the [compilers paths](options_compilers_paths), on the [library manager](widgets_library_manager) entries and on the project parameters. When the [_libman_](widgets_library_manager) is empty then the scope of DCD is limited to the symbols of current module, of the current project sources and of the standard library, that's why it necessary to register the development libraries used in the _libman_.
|
||||
|
||||
_DCD_ also has its own configuration system. Refer to the official [Readme](https://github.com/dlang-community/DCD#configuration-files).
|
||||
|
||||
#### Initialization
|
||||
|
||||
When Coedit starts and if the DCD server is not already listening then it's launched by CE.
|
||||
When Coedit stops, the server is only terminated if it was not already running when starting.
|
||||
When Dexed starts and if the DCD server is not already listening then it's launched by CE.
|
||||
When Dexed stops, the server is only terminated if it was not already running when starting.
|
||||
|
||||
If the DCD server crashes while Coedit is running then both must be restarted.
|
||||
If the DCD server crashes while Dexed is running then both must be restarted.
|
||||
|
||||
#### Usage
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ Project properties are edited in specific widgets.
|
|||
|
||||
#### DUB
|
||||
|
||||
Coedit handles [DUB](http://code.dlang.org/getting_started) projects.
|
||||
Dexed handles [DUB](http://code.dlang.org/getting_started) projects.
|
||||
|
||||
DUB [JSON format](http://code.dlang.org/package-format?lang=json) format is fully supported.
|
||||
DUB [SDL](http://code.dlang.org/package-format?lang=sdl) format is supported in read-only mode.
|
||||
|
|
@ -25,7 +25,7 @@ The option editor exposes a [category for DUB](options_dub_build). The options s
|
|||
|
||||
#### CE format
|
||||
|
||||
The CE (Coedit) format (previously called _native format_) is based on DMD command line interface.
|
||||
The CE format (previously called _native format_) is based on DMD command line interface.
|
||||
The widget used to edit the properties is the [CE project editor](widgets_ce_project_editor) (the format is detailed in this page).
|
||||
|
||||
#### Menu reference
|
||||
|
|
|
|||
|
|
@ -10,10 +10,10 @@ title: Runnable modules
|
|||
|
||||
#### Description
|
||||
|
||||
Coedit is able to compile and execute the module that's currently edited even if it's not part of a project.
|
||||
Dexed is able to compile and execute the module that's currently edited even if it's not part of a project.
|
||||
Such a module is called a **runnable** module.
|
||||
|
||||
Runnable modules don't have to be explicitly saved because Coedit will handle the task automatically, using an unique temporary file name.
|
||||
Runnable modules don't have to be explicitly saved because Dexed will handle the task automatically, using an unique temporary file name.
|
||||
For example it's possible to execute the _Compile and run file_ action directly after the _New runnable module_ action .
|
||||
By default the binary is produced in the folder where is located the D source but this can be changed in the options applied to this feature.
|
||||
|
||||
|
|
@ -27,7 +27,7 @@ Two typical scenarios:
|
|||
- the runnable will be debugged so DWARF informations must be generated with `-g`.
|
||||
- the runnable must be linked with a C static library so the linker flag `-L-lthelib` must be specified.
|
||||
|
||||
Coedit doesn't handle the program specified after the She-Bang, which means that all the following script lines are valid:
|
||||
Dexed doesn't handle the program specified after the She-Bang, which means that all the following script lines are valid:
|
||||
|
||||
- `#!runnable-flags: --whatever`
|
||||
- `#!usr/bin/dmd --whatever`
|
||||
|
|
@ -85,7 +85,7 @@ Note that the action _Run file unittest_ is based on the same internal function
|
|||
- **outputFolder**: Defines a folder where the runnable binary is output. If the value starts by a drive letter or a directory separator then the folder must exist, otherwise it's considered as a subfolder, relative to the runnable filename, which is created automatically.
|
||||
- **outputFolderConditions**: Defines the conditions for which **outputFolder** is handled.
|
||||
- **ifInProject**: The runnable file is part of the current project. For example if **temp/** is in the `.gitignore` and if **outputFolder** is also set to **temp/** then the binary won't appear in the staging area.
|
||||
- **ifSaved**: The runnable file is not in the current project but it's been saved explicitly out of the temp folder that's automatically used by Coedit.
|
||||
- **ifSaved**: The runnable file is not in the current project but it's been saved explicitly out of the temp folder that's automatically used by Dexed.
|
||||
- **ifNotSaved**: The runnable file is not part of the project and has never been saved explicitly.
|
||||
- **staticSwitches**: Defines a list of switches that are always passed to the compiler when a runnable is produced or when a module is tested.
|
||||
|
||||
|
|
|
|||
|
|
@ -20,8 +20,8 @@ Possible symbols, by context, include:
|
|||
|
||||
Application:
|
||||
|
||||
- **`<CAF>`**: also _`<CoeditApplicationFile>`_. Expanded to Coedit filename.
|
||||
- **`<CAP>`**: also _`<CoeditApplicationPath>`_. Expanded to Coedit path.
|
||||
- **`<AF>`**: Expanded to the application (Dexed) filename.
|
||||
- **`<AP>`**: Expanded to the application (Dexed) path.
|
||||
- **`<MEP>`**: Expanded to the path of the folder selected in the [mini-explorer](widgets_mini_explorer).
|
||||
|
||||
Environment:
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ title: index
|
|||
<script src="//cdnjs.cloudflare.com/ajax/libs/anchor-js/4.0.0/anchor.min.js"></script>
|
||||
{% endraw %}
|
||||
|
||||
### Coedit documentation
|
||||
### Dexed documentation
|
||||
|
||||
|
||||
|
||||
|
|
@ -15,7 +15,7 @@ Screenshots can be outdated but descriptions are up to date.
|
|||
|
||||
#### First steps
|
||||
|
||||
_Install and configure Coedit._
|
||||
_Install and configure Dexed._
|
||||
|
||||
* [Build](build.md)
|
||||
* [Setup](setup.md)
|
||||
|
|
@ -44,7 +44,7 @@ _Description of each entry in the main menu. May redirect to a specific widget p
|
|||
|
||||
#### Options categories
|
||||
|
||||
_Full description of Coedit options. May redirect to a specific widget page._
|
||||
_Full description of Dexed options. May redirect to a specific widget page._
|
||||
|
||||
* [Application](options_application)
|
||||
* [Code metrics](options_code_metrics)
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ In general several metrics exist:
|
|||
* [Halstead complexity](https://en.wikipedia.org/wiki/Halstead_complexity_measures): quality indicator based on the count of operators and operands.
|
||||
* [Cyclomatic complexity](https://en.wikipedia.org/wiki/Cyclomatic_complexity): quality indicator based on the program execution flow.
|
||||
|
||||
Coedit implements the Halstead metric. The others may be added in a further version.
|
||||
Dexed implements the Halstead metric. The others may be added in a further version.
|
||||
|
||||
#### Halstead complexity
|
||||
|
||||
|
|
|
|||
|
|
@ -16,14 +16,14 @@ These settings are important and should be verified after the installation.
|
|||
|
||||
Up to five D compilers can be defined.
|
||||
|
||||
* __DMD__: should be set to the stable DMD version. The paths are normally detected when _Coedit_ is launched for the first time.
|
||||
* __DMD__: should be set to the stable DMD version. The paths are normally detected when _Dexed_ is launched for the first time.
|
||||
* __GDC__: should be set to the stable GDC version. The _runtime_ and _Phobos_ sources stand in the same folder so the third field can be left empty.
|
||||
* __LDC__: should be set to the stable LDC version. The _runtime_ and _Phobos_ sources stand in the same folder so the third field can be left empty.
|
||||
* __User1__: can be set to any compiler, for the example the development version of DMD.
|
||||
* __User2__: a second user-defined compiler.
|
||||
|
||||
The combo box at the top is used to select which are the paths passed to the [completion daemon](features_dcd).
|
||||
If the completion daemon is launched by _Coedit_ then the change is applied directly after the validation, otherwise it has to be restarted manually.
|
||||
If the completion daemon is launched by _Dexed_ then the change is applied directly after the validation, otherwise it has to be restarted manually.
|
||||
|
||||
In other options categories one of these compilers can be selected.
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ This category exposes the DUB options that are passed to the build tool each tim
|
|||
|
||||
|
||||
- **archOverride: The option allows to build for x86 under x86_64 and the opposite.
|
||||
- **autoFetch**: If checked then Coedit will try to download missing dependencies when a project or a libman entry is opened. This option is designed to provide better completion but can slow down the startup and the loading of a project.
|
||||
- **autoFetch**: If checked then Dexed will try to download missing dependencies when a project or a libman entry is opened. This option is designed to provide better completion but can slow down the startup and the loading of a project.
|
||||
- **combined**: If checked, tries to build the whole project in a single compiler run.
|
||||
- **compiler**: Selects [which compiler](options_compilers_paths) is used by DUB when a project is compiled. Note that the DUB scripts don't use this setting, instead the same preference set for the [runnable modules](features_runnables#options) is used.
|
||||
- **dependenciesCheck**: Defines how DUB checks the project dependencies, typically used to avoid too much network operations.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: Setup Coedit
|
||||
title: Setup Dexed
|
||||
---
|
||||
|
||||
{% raw %}
|
||||
|
|
@ -15,10 +15,10 @@ There are four ways to get the program:
|
|||
|
||||
In all the cases, the _DMD_ D2 compiler must setup and its location has to match to one of the directory of the PATH environment variable.
|
||||
If it's not already installed, [download](http://dlang.org/download.html) and setup DMD2 for your platform.
|
||||
The latest Coedit version requires at least DMD 2.072.
|
||||
The latest Dexed version requires at least DMD 2.072.
|
||||
Note that DMD is only required for the _ddemangle_ tool otherwise the software can be fully used with only LDC or GDC as compiler.
|
||||
|
||||
For each platform Coedit can be setup using a setup program or by extracting the binaries.
|
||||
For each platform Dexed can be setup using a setup program or by extracting the binaries.
|
||||
|
||||
### Linux dependencies
|
||||
|
||||
|
|
@ -30,17 +30,17 @@ Windows interface is based on native win32 controls.
|
|||
|
||||
### Setup program
|
||||
|
||||
* Go to [the release page](https://github.com/BBasile/Coedit/releases),
|
||||
* Choose the zipped setup for your platform (at the bottom of a release log, the buttons labeled `coedit.<version>.<platform>.setup.zip`).
|
||||
* Go to [the release page](https://github.com/BBasile/dexed/releases),
|
||||
* Choose the zipped setup for your platform (at the bottom of a release log, the buttons labeled `dexed.<version>.<platform>.setup.zip`).
|
||||
* The content must be extracted and executed:
|
||||
* note that the option `--nodcd` can be typed to skip the installation of the completion daemon.
|
||||
* Linux, setup for all the users: in a console `cd` to the file location and type `sudo ./coedit.<version>.<platform>.setup`.
|
||||
* Linux, setup for the current user: in a console `cd` to the file location and type: `./coedit.<version>.<platform>.setup`.
|
||||
* Linux, setup for all the users: in a console `cd` to the file location and type `sudo ./dexed.<version>.<platform>.setup`.
|
||||
* Linux, setup for the current user: in a console `cd` to the file location and type: `./dexed.<version>.<platform>.setup`.
|
||||
* Windows, optional, it may be necessary to deactivate your anti-virus software. Norton AV or McAfee hav been reported for detecting a potential threat.
|
||||
* Windows: double click, and confirm in the UAC dialog box.
|
||||
* To uninstall, run the same program but with the `-u` option.
|
||||
* Linux: if coedit has been setup with `sudo` you must also uninstall with elevated privileges: `sudo ./coedit.<version>.<platform>.setup -u`.
|
||||
* Windows: start a console as administrator and execute: `coedit.<version>.win32.setup -u`.
|
||||
* Linux: if Dexed has been setup with `sudo` you must also uninstall with elevated privileges: `sudo ./dexed.<version>.<platform>.setup -u`.
|
||||
* Windows: start a console as administrator and execute: `dexed.<version>.win32.setup -u`.
|
||||
* Troubleshooting: run the setup program with the `-l` (or `--list`) option to get the status of the files and use the report to uninstall manually the files or open a ticket [here][lnk_bugtracker].
|
||||
|
||||
Note for the future versions:
|
||||
|
|
@ -50,8 +50,8 @@ Note for the future versions:
|
|||
|
||||
### Binaries
|
||||
|
||||
* Go to [the release page](https://github.com/BBasile/Coedit/releases),
|
||||
* Choose the binaries for your platform (at the bottom of an entry, the buttons labeled `coedit.<version>.<platform>.zip`).
|
||||
* Go to [the release page](https://github.com/BBasile/dexed/releases),
|
||||
* Choose the binaries for your platform (at the bottom of an entry, the buttons labeled `dexed.<version>.<platform>.zip`).
|
||||
* Extract the executables.
|
||||
* Linux: it's recommended to put them in `/home/<your account>/bin`, since it's a known system PATH and that it doesn't require the super user privileges.
|
||||
* Windows: the target folder must be added to your system PATH variable. When the location is not known the background tools won't work (symbol list, todo list, DCD).
|
||||
|
|
@ -62,7 +62,7 @@ Under Linux, the command line tool *zip* is used (_deflate_ and _-9_).
|
|||
Under Linux you could have to set the files permission to allow their execution. This used to be necessary when
|
||||
the early alpha zip were all done on Windows (files attributes were lost) but it shouldn't be the case anymore.
|
||||
|
||||
If they are not correctly set, for each of the following file **coedit**, **dcd-client**, **dcd-server**, **dastworx**, either set the permission in the context menu (check _allow execution_ or _executable_ depending on the desktop) or `chmod a+x` the file in a console.
|
||||
If they are not correctly set, for each of the following file **dexed**, **dcd-client**, **dcd-server**, **dastworx**, either set the permission in the context menu (check _allow execution_ or _executable_ depending on the desktop) or `chmod a+x` the file in a console.
|
||||
|
||||
### Linux package
|
||||
|
||||
|
|
|
|||
|
|
@ -6,9 +6,9 @@ title: Widgets - CE project editor
|
|||
{% endraw %}
|
||||
{% include xstyle.css %}
|
||||
|
||||
### Coedit project editor
|
||||
### CE project editor
|
||||
|
||||
The widget is used to edit the properties of a project that has the CE (Coedit) format.
|
||||
The widget is used to edit the properties of a project that has the CE (for _Coedit_, Dexed former name) format.
|
||||
It's no recommended to use this format anymore.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ title: Widgets - custom tools
|
|||
|
||||
### Custom tools
|
||||
|
||||
This widget allows to define a set of third party applications that can be launched from Coedit.
|
||||
This widget allows to define a set of third party applications that can be launched from Dexed.
|
||||
The tools are not just applications that are launched from the software.
|
||||
Since they support [symbolic strings](features_symbolic_strings) they can directly perform some actions on the current source file, in its directory, in the project directory and more.
|
||||
The tools can even be chained and piped between themselves.
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ A property value can be modified in the field at the bottom. New values always r
|
|||
New properties can be added or removed:
|
||||
|
||||
- <img src="{%include icurl%}other/textfield_add.png" class="tlbric"/>: Shows a small dialog that allows to add a new value, a new array or a new object.
|
||||
- <img src="{%include icurl%}other/textfield_delete.png" class="tlbric"/>: Removes the selected property. Note that the effect is not reflected until the project is saved as a file (since Coedit does not communicate directly with DUB).
|
||||
- <img src="{%include icurl%}other/textfield_delete.png" class="tlbric"/>: Removes the selected property. Note that the effect is not reflected until the project is saved as a file (since Dexed does not communicate directly with DUB).
|
||||
- <img src="{%include icurl%}other/copy.png" class="tlbric"/>: Duplicates the selected object. Can be used to clone a configuration or a build type.
|
||||
- <img src="{%include icurl%}arrow/arrow_update.png" class="tlbric"/>: Updates the list of sources files and auto fetch dependencies if specified as an option for [DUB](options_dub_build)
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ The _editor widget_ is a standard code editor, specialized for highlighting D so
|
|||
|
||||
#### Navigation
|
||||
|
||||
In addition to the standard actions used to navigate in a source, Coedit implements several helpers:
|
||||
In addition to the standard actions used to navigate in a source, Dexed implements several helpers:
|
||||
|
||||
- **Next/Previous location**: The two actions are used to jump to the locations where the caret was activated. They follow the chronology and not the line numbers. In the [shortcut editor](options_shortcuts_editor) they can be found under the names _PreviousLocation_ and _NextLocation_. The actions are also hard linked to the mouse buttons X1 and X2 and the multimedia keys usually used by web browsers to reload the next or the previous page.
|
||||
- **Next/Previous changed area**: The two actions are used to jump to the locations that contain changes. They follow the line numbers. In the [shortcut editor](options_shortcuts_editor) they can be found under the names _PreviousChangedArea_ and _NextChangedArea_.
|
||||
|
|
@ -88,7 +88,7 @@ It's useful to display a module that contains the declarations of a library bind
|
|||
|
||||
#### External Modification tracking
|
||||
|
||||
When a document that's edited in Coedit is modified by another program, a _diff_ is displayed.
|
||||
When a document that's edited in Dexed is modified by another program, a _diff_ is displayed.
|
||||
|
||||
|
||||
|
||||
|
|
@ -99,7 +99,7 @@ The dialog is guaranteed to be only displayed when the content contains changes.
|
|||
If activated in the options (see beyond), the source can be automatically linted, after a relative period of time, following the last keystroke.
|
||||
Results are displayed in the gutter and the warning body can be consulted in the hint displayed when the mouse motin stops over the icon.
|
||||
Linting requires [D-Scanner](https://github.com/dlang-community/D-Scanner) to be setup.
|
||||
It's possible to use the [information box](widgets_about) to determine if Coedit can find the tool.
|
||||
It's possible to use the [information box](widgets_about) to determine if Dexed can find the tool.
|
||||
Note that linting can also be launched manually from the _File_ or the _Project_ menus.
|
||||
|
||||
#### Notable options
|
||||
|
|
|
|||
|
|
@ -51,7 +51,7 @@ When the toolbar button that displays DUB logo is clicked, a dialog is displayed
|
|||
The text field is used to select the name of the package to install.
|
||||
|
||||
- <img src="{%include icurl%}arrow/arrow_update.png" class="tlbric"/>: Update the list of the online packages.
|
||||
- <img src="{%include icurl%}other/tag_purple.png" class="tlbric"/>: By the default the master version of the package is installed. When the tag button is down Coedit rather installs the package from its latest tag.
|
||||
- <img src="{%include icurl%}other/tag_purple.png" class="tlbric"/>: By the default the master version of the package is installed. When the tag button is down Dexed rather installs the package from its latest tag.
|
||||
- <img src="{%include icurl%}other/accept.png" class="tlbric"/>: Closes the dialog and start downloading before installing.
|
||||
- <img src="{%include icurl%}other/cancel.png" class="tlbric"/>: Cancels and does nothing.
|
||||
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ This value and several other options can be changed in the options.
|
|||
|
||||
|
||||
- **alwaysFilter**: Sets if the custom filter (text filed at the top right) is maintained or if it's reset when new messages are emitted.
|
||||
- **autoDemangle**: Automatically filters the new messages with [ddemangle](https://github.com/dlang/tools#d-tools). Note that Coedit uses the tool as a daemon so it's perfectly normal that it remains in the task list when the IDE runs.
|
||||
- **autoDemangle**: Automatically filters the new messages with [ddemangle](https://github.com/dlang/tools#d-tools). Note that Dexed uses the tool as a daemon so it's perfectly normal that it remains in the task list when the IDE runs.
|
||||
- **autoSelect**: Defines if the widget change dynamically the message categories.
|
||||
This is a recommended setting because if a run-time error happens, it will be immediately displayed.
|
||||
- **colors**: Allows to associate a message kind to a particular color.
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ title: Widgets - symbol list
|
|||
## Symbol list
|
||||
|
||||
This list displays the symbols declared in the D module that has the focus (imports, classes, variables, etc).
|
||||
The widget is a GUI front-end for one the [_dastworx_](https://github.com/BBasile/Coedit/tree/master/dastworx) feature.
|
||||
The widget is a GUI front-end for one the [_dastworx_](https://github.com/BBasile/dexed/tree/master/dastworx) feature.
|
||||
|
||||
It can be used to quickly find and go to the declaration of a symbol but also as a basic linter since the syntactic errors are displayed (almost immediately if the option _refresh on change_ is checked).
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue