IDLE: Double click text in editor to select more meaningful area
@terryjreedy ya está trabajando en esto.
Desde el 5/7/2022.
- Lenguaje dominante
- Python
- Estrellas
- 77.2k
- Forks
- 36k
- Merge medio
- 1 d 9 h
- PR fusionados (30 d)
- 558
Descripción
Feature or enhancement
- Highlight the selected word.
- Click the boundaries of string to select the whole string. (by using pre-tagged TAG in tk.Text)
- Quick select the whole comments by click the comment mark (# sign).
- Quick select the matched parentheses, including in comments.
- Select a row by double-click the end of line.
- Multi-line select by click the colon mark or click the space in indent.
- Select escape character (\n, \xhh, \uxxxx, …).
- …
Pitch
In the original IDLE, the logic that controlled the double-click selected text area was in file "~\tcl\tk8.6\text.tcl".
It is equivalent to select a regular expression that equal with "\w+" or "\W+". It help us double-click to select a whole parameter. It is better than nothing. But in my solution, it can do better.
Such as s.split('\n')[:ln], tk's auto selection will select ')[: and ('\, but this seems does not benefit to editing.
In my solution, I can double-click to select ('\n'), '\n', \n, and [:ln] (these were 3 types of match mode). I think this will help developers copy or cut code for what they want much more easier.
Notable things
-
Considering that sometimes I want to copy text with brackets from comment text, So I use the text rule to match the bracket pairs. Unexpected selection may occur when existing escape characters.
-
Highlighting the selected word will cause difference user experience at interface. Maybe not everyone like this feature. Do you have any suggestions?
Previous discussion
Usage: https://github.com/znsoooo/IDLE-Advance
Implementation: https://github.com/znsoooo/IDLE-Advance/blob/master/idlealib/SmartSelect.py
Linked PRs
- gh-145386
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Evaluación
Este issue todavía no se ha evaluado.