Hi Jaromir, Marcel, all,
with Morphic-mt.1824 in current Trunk, we have the following behavior for closer brackets:
Via "enclose selection" preference, an opening bracket adds a level and a closer bracket removes a level. No toggling anymore.
So pressing a closer bracket removes the pair of brackets that is *enclosing* the selection. However, I still wonder whether we should also remove the pair of brackets *inside* the selection if there is no further pair of brackets.
So that
[123] (entire line selected)
when pressing
]
becomes
123 (entire line selected)
instead of (as in current Trunk)
] (nothing selected)
Or would this be more inconsistent than convenient? Wdyt?
Best, Christoph
--- Sent from Squeak Inbox Talk
On 2022-02-07T23:33:53+01:00, christoph.thiede@student.hpi.uni-potsdam.de wrote:
Just a quick note to myself, compensating for the lack of meta information on the list: This issue has been resolved via Morphic-mt.1809. Thanks. :-)
Best, Christoph
Sent from Squeak Inbox Talk
On 2021-11-01T22:09:46+01:00, christoph.thiede at student.hpi.uni-potsdam.de wrote:
Hi all!
This changeset refines the existing autoEnclose mechanism. Instead of having inserted enclosing brackets always, you can now activate a new preference to only insert these characters if there is any space after the cursor. This matches VS Code's setting value "beforeWhitespace" for "editor.autoClosingBrackets".
To me, this mode feels much more convenient because when having traditional autoEnclose enabled, I have been getting angry again and again when I wanted to bracketize an existing expression in some code and suddenly was disrupted by an unneeded closing bracket.
The changeset does not manipulate any defaults. The PreferenceWizard and the ReleaseBuilder are updated, too. Please honor the postscript of the changeset when merging it.
Best, Christoph
Sent from Squeak Inbox Talk