I do not turn on autoformatting and use the format menu entry on an as needed basis.
Autoformatting on Seaside renderOn: methods is a royal PITA. Phil On Thu, Oct 26, 2017 at 8:44 PM, Peter Uhnák <[email protected]> wrote: > > Autoformatting messing with my parentheses is just a mistake. > > I put them in, leave them where they are, 'kay? I do not need an editor > that rewrites what I tell it. AST power or not. > > By the same argument you can tear apart any property of autoformatting. > "Why is it messing with my indentation here?" "Why is it removing > newlines?" "Why is it removing the last dot?" > The problem here is that the autoformatter has no way of knowing that it > is some "special" use rather than general binary message. > (And for the record, I have startup scripts that modify the source code of > the formatter, so I certainly am aware of autoformatting limitations...) > > Peter > > > On Thu, Oct 26, 2017 at 8:34 PM, Bernardo Ezequiel Contreras < > [email protected]> wrote: > >> you could do >> >> 1 x + 2 y + 5 z >> >> and that expression will give you a 3d vector. >> but it creates a lot of intermediate objects >> >> On Thu, Oct 26, 2017 at 2:04 PM, Chris Cunningham < >> [email protected]> wrote: >> >>> >>> >>> On Thu, Oct 26, 2017 at 7:09 AM, Sean P. DeNigris <[email protected] >>> > wrote: >>> >>>> Maybe we can follow the FS/PP pattern >>>> and scope the message to only-vector-like-things via an initial >>>> message, so >>>> just like `$f asParser, …`, have `1 {vector-appropriate-message}, …`? >>>> >>>> So, something like >>> 1 vector, 2, 5 >>> or >>> 1 biVector, 2, 6 >>> ? >>> >>> -cbc >>> >> >> >> >> -- >> Bernardo E.C. >> >> Sent from a cheap desktop computer in South America. >> > >
