> It's called "quoting out of context". Your editing of the thread
> changes the tone of the thread for anyone that jumps in at the middle.
> If you are doing this on purpose, it is dishonest (and flabbergasting).
> If you are doing it out of ignorance, you should be aware of the
> consequences an
> No arguments here. You cut out the part of my reply where I agreed
> with you on this exact point. The execution was far from ideal.
If you already said it, my not reposting it does not in any way invalidate
it.
> I am not advocating either way; however, you failed to address my point
> about
> Which was last updated when? I will make it a priority to grok this
> document and regurgitate anything useful that I find to the list, but I
> just want to point out that the lack of up-to-date backing
> documentation raises questions about the objectivity of anyone's current
opinions.
> I beli
> Well I bricked a $15k board today :)
>
> The Flash on this ARM926EJ-S core board is 2 512Mbit NOR Spansion
> S29GL512N-11F chips arranged 32M x 32bit.
If you paid $15K for an ARM926EJ-S board, it sounds like you got screwed --
but because I now feel bad for you, I'm totally willing to sell you
> > zw> @@ -8953,7 +8954,8 @@
> > zw> const int cwd_len=2048;
> > zw> char *cwd=malloc(cwd_len);
> > zw> Jim_SetResult(interp, Jim_NewEmptyStringObj(interp));
> > zw> - getcwd( cwd, cwd_len );
> > zw> + cwd = getcwd( cwd, cwd_len );
> > zw> + if (N
> So async telnet messages enable/disalbe option then?
>
> Off by default?
That's my vote. Having them on slows down debugging a lot.
> The C code is of course the ultimate in flexibility, which is why open
> source is such fun.
>
> I hate systems with lots of incomprehensible and undocumented
> I like to have as many configuration options as is necessary and no
> more.
I agree in principle, but that's a difficult thing to nail down because
what's necessary for one may not be necessary for another.
> I hate configuration options that are there just because the problem of
> how to solv
> 3. add an option(yuk!) of sorts. Perhaps remove asynchronous messages
> by default and make it possible to enable them? Who's going to find
> this option anyway?
I don't think adding a 'verbose' option to turn something like this on is
terrible by any means.
You get this information inside of GD
