Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Explain CodeEditor's parameters within the doctring

See original GitHub issue

Issue Report Checklist

Searched the issues page for similar reports

Problem Description

There is not an explanation of the multiple parameters that a CodeEditor instance can receive

Following suggestion at https://github.com/spyder-ide/spyder/pull/9897#discussion_r320016309

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:11 (11 by maintainers)

Top GitHub Comments

2reactions

Akashtyagicommented, Apr 8, 2020

Working on it.

2reactions

dalthvizcommented, Apr 6, 2020

@Akashtyagi08 the missing initial descriptions:

occurrence_timeout : Timeout in milliseconds to start highlighting matches/occurrences for the current word under the cursor. Default 1500 ms.
tab_stop_width_spaces: Enable/Disable using tabs for indentation. Default True
auto_unindent: Enable/Disable automatically unindentation before else, elif, finally or except statements. Default True
scrollflagarea : Enable/Disable flag area that shows at the left of the scroll bar. Default True
strip_mode: Enable/Disable striping trailing spaces when modifying the file. Default False
occurrence_highlighting: Enable/Disable highlighting of current word occurrence in the file
intelligent_backspace: Enable/Disable automatically unindenting inserted text (unindenting happens if the leading text length of the line isn’t module of the length of indentation chars being use). Default True