Markdown link migration part 2 (#20371)
This commit is contained in:
parent
2147b116a1
commit
c4ba4f06f8
18 changed files with 287 additions and 283 deletions
|
|
@ -12,19 +12,19 @@
|
|||
|
||||
> "yes, I'm the creator" -- Araq, 2013-07-26 19:28:32.
|
||||
|
||||
Note: this is mostly outdated, see instead `nimsuggest <nimsuggest.html>`_
|
||||
Note: this is mostly outdated, see instead [nimsuggest](nimsuggest.html)
|
||||
|
||||
Nim differs from many other compilers in that it is really fast,
|
||||
and being so fast makes it suited to provide external queries for
|
||||
text editors about the source code being written. Through the
|
||||
`idetools` command of `the compiler <nimc.html>`_, any IDE
|
||||
`idetools` command of [the compiler](nimc.html), any IDE
|
||||
can query a `.nim` source file and obtain useful information like
|
||||
definition of symbols or suggestions for completion.
|
||||
|
||||
This document will guide you through the available options. If you
|
||||
want to look at practical examples of idetools support you can look
|
||||
at the test files found in the `Test suite`_ or `various editor
|
||||
integrations <https://github.com/Araq/Nim/wiki/Editor-Support>`_
|
||||
at the test files found in the [Test suite] or [various editor
|
||||
integrations](https://github.com/Araq/Nim/wiki/Editor-Support)
|
||||
already available.
|
||||
|
||||
|
||||
|
|
@ -124,8 +124,8 @@ to the case insensitiveness of the language (plus underscores as
|
|||
separators!).
|
||||
|
||||
The typical usage scenario for this option is to call it after the
|
||||
user has typed the dot character for `the object oriented call
|
||||
syntax <tut2.html#object-oriented-programming-method-call-syntax>`_.
|
||||
user has typed the dot character for [the object oriented call
|
||||
syntax](tut2.html#object-oriented-programming-method-call-syntax).
|
||||
Idetools will try to return the suggestions sorted first by scope
|
||||
(from innermost to outermost) and then by item name.
|
||||
|
||||
|
|
@ -196,7 +196,7 @@ of text it thinks necessary plus an empty line to indicate the end
|
|||
of the answer.
|
||||
|
||||
You can find examples of client/server communication in the idetools
|
||||
tests found in the `Test suite`_.
|
||||
tests found in the [Test suite].
|
||||
|
||||
|
||||
Parsing idetools output
|
||||
|
|
@ -367,8 +367,8 @@ defined, since at that point in the file the parser hasn't processed
|
|||
the full line yet. The signature will be returned complete in
|
||||
posterior instances of the method.
|
||||
|
||||
Methods imply `dynamic dispatch
|
||||
<tut2.html#object-oriented-programming-dynamic-dispatch>`_ and
|
||||
Methods imply [dynamic dispatch](
|
||||
tut2.html#object-oriented-programming-dynamic-dispatch) and
|
||||
idetools performs a static analysis on the code. For this reason
|
||||
idetools may not return the definition of the correct method you
|
||||
are querying because it may be impossible to know until the code
|
||||
|
|
@ -590,7 +590,7 @@ All the `tests/caas/*.txt` files encode a session with the compiler:
|
|||
modes, you can prefix a line with the mode and the line will be
|
||||
processed only in that mode.
|
||||
|
||||
* The rest of the line is treated as a `regular expression <re.html>`_,
|
||||
* The rest of the line is treated as a [regular expression](re.html),
|
||||
so be careful escaping metacharacters like parenthesis.
|
||||
|
||||
Before the line is processed as a regular expression, some basic
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue