It sounds like you find it better than Atom. If that's true, any chance
you could elaborate on what you find particularly nicer and/or what's
missing?
Thanks,
Dan
2017-02-24 5:49 GMT-08:00 James Cheng :
> Hi,
> Is it possible to configure VSCode to make "watch window" show "value"
> with *"ty
2017-06-16 6:22 GMT-07:00 Ehsan Akhgari :
> On 06/15/2017 04:37 PM, Nathan Froyd wrote:
>
>> Would it be feasible to use headless mode for mochitests (or reftests,
>> etc. etc.)?
>>
> Running the tests that we rely on for correctness on an environment that
> looks this different than the environme
I wonder if this isn't (in large part) a design problem disguised as a
behavior problem. The existing try syntax (even with try chooser) is so
finicky and filled with abbreviations that even after years of working with
it, I still regularly have to look up stuff and sometimes when I've been in
a h
Could we do this on a per-module opt-in basis to allow for gradual
migration? That is to say, assuming there's enough information in the
stack to tell where it was thrown from (I'm guessing that's the case most
of the time), by default, ignore these errors unless they're from code in
an opted-in m
Dave, how would you feel about deciding on one of those and allowing
modules to opt-in to using them, perhaps just as an experiment. Presumably
most existing modules wouldn't, but new ones being written might.
Dan
2017-10-18 9:06 GMT-07:00 Dave Townsend :
> On Wed, Oct 18, 2017 at 4:51 AM Mark
I've had good luck with
https://addons.mozilla.org/en-US/firefox/addon/theme-font-size-changer/ on
Mac. It may be a good place to play with some of the user-experiences
available if we want to provide something in core Firefox...
Dan
2016-09-09 17:23 GMT-07:00 Myk Melez :
> Justin Dolske
> 201
Indeed, a good argument could be made that the old "quirks mode" years of
the web were a strong example of the web suffering a lot while learning
this very lesson (and modern web standardization processes work pretty hard
to try and avoid it).
Dan
On Fri, May 15, 2015 at 9:47 AM, Martin Thomson
free to respond to the mailing
list where you saw this question, email me directly, or ask in #go-node in
slack.
-
For bigger issues (eg “I don’t think this should land yet”, “there’s a
big problem that’s likely to affect one or more groups of people”), feel
free to reach out to o
u saw this question, email me directly, or ask in
#go-node in slack.
* For bigger issues (eg “I don’t think this should land yet”, “there’s
a big problem that’s likely to affect one or more groups of people”),
feel free to reach out to one of: Dan Mosedale (me)
<https://mozillians.org/en-US/u/dmose/
Am Mi., 27. Feb. 2019 um 06:28 Uhr schrieb Nathan Froyd :
> > > If people have problems with bootstrap (it doesn't do enough, it
> > > assumes too much about your system, etc. etc.), please file bugs on
> > > what's wrong. We need to start depending more on bootstrap for
> > > everything, to the
I've looked at the UX spec and Sylvestre's announcement, and I have
some relevant experience here working on teams which have used the
"enhancement" value of the "severity" field with the intent of using
that information to monitor our rate of defect introduction.
That workflow has turned out to h
Seems like it ought to be straightforward to do something to cause
in-testsuite? flags to send mail occasionally, or show up on some
dashboard, or...
Dan
Am Di., 10. Sept. 2019 um 09:11 Uhr schrieb Andrew McCreight
:
>
> On Tue, Sep 10, 2019 at 4:55 PM Dave Townsend wrote:
>
> > On Mon, Sep 9, 2
Also, if you did the double self-update to move over to pip while
running under pyenv, moz-phab may suddenly disappear from your path
until you restart your shell.
Dan
Am Do., 24. Okt. 2019 um 03:55 Uhr schrieb Axel Hecht :
>
> Am 24.10.19 um 12:13 schrieb Henrik Skupin:
> > glob wrote on 23.10.1
Now that we have NodeJS in the tree, we want to unlock the rich set of tooling
in the NodeJS/npm ecosystem so that we can start depending on things available
there in a coherent, managed, more secure way.
We've drafted policy docs to govern use and management of those
packages, and we'd love you
* Upgrades for NodeJS from 8.11.3 to 8.17.0 and for NPM from 5.6.0 to 6.13.4
have merged to mozilla-central.
* Everyone is encouraged to run `mach bootstrap` to upgrade the toolchain on
their machine.
* The main security fix that we’re concerned with is in npm, so I’ve also set
6.13.4 as the
As Ed Lee posted last week [1], we’re about to start requiring NodeJS version
10 for our builds for Firefox 75 and later [2].
In the next small number of days, I plan to land this change via Lando. After
the patch from [2] merges to mozilla-central and you’ve updated your copy of
m-c, in orde
Node 10 support has now merged to mozilla-central, see below for more details:
On Tue, 11 Feb 2020 at 12:49, Dan Mosedale wrote:
> After the patch from [1] merges to mozilla-central and you’ve
> updated your copy of m-c, in order for your builds to continue to
> work:
>
> fo
17 matches
Mail list logo
