Re: Should &&/|| really be at the end of lines?

On 2017-02-16 18:21, Jean-Yves Avenard wrote: > > > On 17/02/17 00:17, Jeff Gilbert wrote: >> If there are so many parens that we require an editor to disambiguate >> them, it's too dense. Add whitespace or decompose the expression until >> readable. >> > I'd love to know how adding any

Re: Should &&/|| really be at the end of lines?

> On Feb 17, 2017, at 6:24 PM, ISHIKAWA,chiaki wrote: > > Point 2: > I prefer all the operators including "&&" and "||" > at the beginning since such a format makes the tree-like structure of > multi-line easier to understand and edit, too. > Adding a condition or

Re: Intent to remove: support for installing multiple xpis simultaneously

Unfortunately I'm using this approach to bundle my themes with an extension that extends capability to them. I'm wondering why to remove this feature at this point of development, since for Firefox 57 upwards XUL based addons will not work anymore.

Re: Should &&/|| really be at the end of lines?

On 17/02/17 23:18, gsquel...@mozilla.com wrote: Hi again Nick, Someone made me realize that I didn't fully read your message, sorry for that. I now see that as well as &&/||, you have grepped for other operators, and shown that the overwhelming usage is to put all of them at the end of