>
> It is only the autoEnclose preference that causes problems in
> workspaces,


What "problems" are those?   Just as you see in the subject-line of this
email, for every open-parenthesis, there's a closing, as well as for every
open bracket, a closing.  That's the structure of these characters in every
normal context.  "Problems" arise when they get out of balance, which is
why other editors have this feature too.  IIRC, eclipse was doing it in
2005.

IMO, it's a good thing for developers and users alike.

+1 for autoEnclose being true by default in the release image.   :)

 - Chris



> so that is the only one that I think should be
> disabled out of the box.
>
> Sorry for the confusion.
>
> Dave
>
>
>
> On Sun, Dec 22, 2019 at 06:06:42PM +0100, Jakob Reschke wrote:
> > I think autoIndent is really practical when writing code in blocks or
> > cascades, or otherwise indented text. Why do you feel that it should it
> be
> > off by default?
> >
> > Am So., 22. Dez. 2019 um 17:17 Uhr schrieb David T. Lewis <
> > lewis at mail.msen.com>:
> >
> > > These default settings seem good to me, with the exception of:
> > >
> > >   TextEditor autoEnclose: true.
> > >   TextEditor autoIndent: true.
> > >
> > > I think that both of these should be false by default.
> > >
> > > Dave
> > >
>
> >
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20191223/637d1b44/attachment.html>