summary refs log tree commit diff stats
path: root/nimsuggest
Commit message (Collapse)AuthorAgeFilesLines
* Remove the uses of {.procvar.} pragma (#14359)Kaushal Modi2020-05-151-7/+7
| | | | | | | This pragma did nothing. Ref: - https://github.com/nim-lang/Nim/issues/2172#issuecomment-383276469 - https://github.com/nim-lang/Nim/issues/12975
* compiler/suggest: highlight squashed operators (#11796)alaviss2020-04-201-0/+11
| | | | | | The operator fetching proc is greedy, so operators such as `%*` in expression `%*{}` can't be highlighted. This commit fixes that.
* fix deprecations and other warnings (#13748)Miran2020-03-251-3/+3
|
* fix nimsuggest warning (#13699)Jasper Jenkins2020-03-203-7/+4
|
* fix .deprecated. object typedef crash (#13643)Andy Davidoff2020-03-162-8/+7
| | | | | * fix .deprecated. object typedef crash * fixup a test that i don't understand * disable the test rather than debug ci
* Revert "nimsuggest: don't add CRLF to replies (#13545)" (#13597)alaviss2020-03-061-4/+4
| | | | | | | | This reverts commit a974684b149faa19645f1e18b7b11aa67f169997. The CRLF was to separate between each response, and removing them causes the responses to not be splitted correctly. I didn't notice that it was in a loop when I made the #13545.
* nimsuggest: don't add CRLF to replies (#13545)alaviss2020-03-041-4/+4
| | | This is already sent by replTcp after the message is sent.
* make case-object transitions explicit, make unknownLineInfo a const, replace ↵Jasper Jenkins2020-01-171-1/+0
| | | | a few magic numbers with consts (#13170)
* fix nimsuggest deprecation warnings (#12772)Jasper Jenkins2019-11-301-2/+2
|
* remove unused importsnarimiran2019-11-061-4/+3
|
* compiler/suggest: add variable support to `con` (#12569)alaviss2019-11-041-0/+12
| | | This allows for the type of a variable to be retrieved.
* compiler/semtypes: improve lineinfo for exported object fields (#12495)alaviss2019-10-251-0/+11
| | | | | | | The line info should now points to the `a`, not the `*`, like this: a*: string ^ Additionally this fixes nimsuggest's highlighting of exported object fields.
* compiler/semcall: return the correct lineinfo for nkCallStrLit (#12484)alaviss2019-10-241-0/+11
|
* nimsuggest: add a command that returns the project file (#12411)alaviss2019-10-111-1/+10
| | | | | | | This can be used to let nimsuggest users know which project is nimsuggest being in charge of, so they can know when should a new nimsuggest instance be spawned. An additional feature is to debug the project file finding feature.
* nimsuggest: add option to force finding the project file (#12409)alaviss2019-10-111-1/+10
|
* nimsuggest: fix tcp socket leak for epc backend (#12384) [backport]alaviss2019-10-081-1/+1
| | | | | | | | Same as e9fa4c9b9c8e2926449399a69a02676936bb842c, but for the epc backend which is used by emacs and vscode plugin. Since the EPC backend only deal with one connection per nimsuggest instance, only one socket is leaked, thus not as servere as with the tcp backend.
* nimsuggest: fix tcp socket leak (#12377) [backport]alaviss2019-10-081-1/+1
| | | | | | A new socket is created for each iteration and leak immediately thanks to the accept() call replacing the created socket with the client socket. This commit fixes that.
* Fix spellings (#12277) [backport]Federico Ceratto2019-09-272-2/+2
|
* fixes #12125 (#12131)Andreas Rumpf2019-09-061-0/+0
| | | | * fixes #12125
* minor style changesAraq2019-07-112-10/+10
|
* [bugfix] fix #11482, fix nimsuggest range error (#11519)Miran2019-06-171-2/+2
| | | | | | The default starting parameters for `line` and `col` were switched. See line 141: "line starts at 1, column at 0, dirtyfile is optional". Also, in `TLineInfo` object, `line` is uint16, `col` is int16.
* [other] nimsuggest: adhere to our style guideAraq2019-06-131-2/+2
|
* make fullpaths the default in error messages and stack traces for mor… ↵Andreas Rumpf2019-06-051-0/+1
| | | | | | | | | | | | (#11385) * make fullpaths the default in error messages and stack traces for more convenient development * split up -d:release into -d:release and -d:danger flags * workaround a Nim config parser bug * fixes an old nim config parser bug * make megatest green again * make nimpretty tests work again * make nimsuggest green
* update nimsuggestAraq2019-05-271-39/+15
|
* Allow void macro result (#11286)Arne Döring2019-05-211-1/+1
| | | | | * allow void macro result * add test for void macro result type
* move assertions and iterators out of system.nim (#10597)Miran2019-03-072-3/+2
| | | | | * move assertions and iterators out of system.nim * limit nimsuggest tests to the first 3 suggestions
* nimsuggest: make use project file name if none given for 'sug' command; ↵Andreas Rumpf2019-03-041-4/+8
| | | | allows for more convenient debugging
* StringStream and parseJson, parseCfg, parseSql et al for the vm (#10746)Arne Döring2019-02-281-30/+25
|
* better docs: osproc (#10708)Miran2019-02-192-3/+3
| | | | | * better docs: osproc * fix a typo in the docs, deprecate "demon"
* document proper imports, fixes #8164 (#10698)Miran2019-02-191-0/+2
|
* compiler/types: correctly generates signature for non-proc types (#10658)alaviss2019-02-131-0/+12
| | | | This makes signatures generated for nimsuggest correctly distinguish template/macro/converter from proc.
* nimsuggest: only log when logging is enabled (#10646)alaviss2019-02-131-2/+2
| | | fixes #6199
* compiler/[msgs, suggest]: improve highlighter accuracy (#10496)alaviss2019-02-072-0/+21
| | | | | | | | | | Previously the compiler would generate suggestions based on the symbol identifier length, but that might not reflect the actual representation of it within the actual source code. This commit implements a simple source scanner for the suggest module to address the problem outlined above. Fixes nim-lang/nimsuggest#24
* suggest: quote operators and keywords on suggestion (#10460)alaviss2019-01-281-0/+10
|
* semcall: correct lineinfo for accquoted symbols (#10461)alaviss2019-01-271-0/+2
|
* compiler/sem: correct macros lineinfo (#10438)alaviss2019-01-241-0/+13
| | | | | | | | | The compiler believes these are where a macro call starts (marked with `^`): m "string" ^ ^ This commit addresses that.
* compiler/sem*: better lineinfo for templates (#10428)alaviss2019-01-233-2/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | * compiler/sem*: better lineinfo for templates Lineinfo for templates is inconsistant across the compiler, for example: doAssert true ^ ^ a[int](10) ^^ ^ The `^` marks where the compiler thinks the template starts. For qualified call, we got the same situation with `proc`s before #10427: system.once ^ Generics lineinfo within template declaration is also incorrect, for example, this is where the compiler believes the `T` in `[T]` is: template a[T](b: T) ^ This PR addresses all of these problems. * nimsuggest: add tests for template highlighting
* nimsuggest/tester: disable highlight tests for epc (#10426)alaviss2019-01-233-2/+4
| | | | The EPC backend of nimsuggest currently doesn't support nimsuggest highlighter, see nim-lang/nim-mode#140
* compiler/sem*: improve lineinfo for qualified and generic procs (#10427)alaviss2019-01-232-0/+27
| | | | | | | | | | | | | | | | Previously the compiler will believe these are where `newSeq` symbol starts: newSeq[int]() ^ system.newSeq[int]() ^ This commit moves them back to: newSeq[int]() ^ system.newSeq[int]() ^
* Correct lineinfo for accent quoted symbols in proc definition (#10399)alaviss2019-01-211-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * compiler/parser: preserve lineinfo for accent quoted symbols Previously the lineinfo for symbol $$$ in this example is: proc `$$$` ^ After this commit: proc `$$$` ^ * compiler/semstmts: correct lineinfo for accent quoted idents Previously nimsuggest would highlight this as: proc `$$$` ^~~ After this commit: proc `$$$` ^~~ * nimsuggest/tests: add a test for accent quoted proc Disabled by default
* nimsuggest: add an option to bind to a free port (#10328)alaviss2019-01-161-2/+15
|
* fixes nim-lang/nimsuggest#76 (#10093)alaviss2018-12-252-2/+30
| | | | | | | | * nimsuggest: prevent out-of-bound access * fixes nim-lang/nimsuggest#76 * undo tester changes
* Moved some code around in nimsuggest to avoid crash when run as library (#9818)PMunch2018-12-011-8/+22
| | | | | | | | * Moved some code around in nimsuggest to avoid crash when run as library * Moved the common executecallback setting to a procedure * Fixed slight issue
* Made nimsuggest importable as a library and add Nim-path override option (#9784)PMunch2018-11-231-1/+100
| | | | | | * Made nimsuggest importable as a library and add Nim-path override option * Remove leftover debug output
* nimsuggest: fixes #96Timothee Cour2018-11-201-2/+3
|
* refs #9637 ; cleanup installation of nimsuggest (#9703)Timothee Cour2018-11-151-1/+0
|
* remove ---path:"../compiler" from nimsuggest/nimsuggest.nim.cfgTimothee Cour2018-11-071-1/+0
|
* compiler refactoring; use typesafe path handing; docgen: render symbols ↵Andreas Rumpf2018-09-071-18/+21
| | | | between modules
* make config.nims behave like nim.cfg in terms of where these scripts are ↵Timothee Cour2018-08-301-48/+25
| | | | | | | | | searched / run (#8682) * run project config.nims if exists, then inputfile.nims if exists * ~/.config/nim/config.nims can now be used * also check in getSystemConfigPath for config.nims * refactor handleCmdLine for nim and nimsuggest
* add nim c -r nimsuggest/tester to travis (#8805)Timothee Cour2018-08-299-2/+26
|