IDLE: Double click text in editor to select more meaningful area
@terryjreedy ci sta già lavorando.
Dal 5/7/2022.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
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
- Lingua principale
- Python
- Stelle
- 77.2k
- Fork
- 36k
- Merge medio
- 1g 9h
- PR unite (30g)
- 558
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di python/cpython
-
docs pending
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
-
stdlib type-feature
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
-
stdlib type-feature
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
build type-bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
-
stdlib topic-email type-feature
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
Tutte le issue di python/cpython
Issue simili
-
🐛 Bug 🔔 Pending processing
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
jumpserver/jumpserver#17584 ·
-
link-check link-check:sphinx-theme
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 90/100
modelscope/DiffSynth-Studio#1702 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
qgis/QGIS-Documentation#11275 ·
-
bug priority:normal ready-for-dev
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
OpenHands/extensions#626 · 1 commento ·