On 10.12.10 21:05, Noel Welsh wrote:
It is moderately useful to see what is reloaded if you renter enter!
Just a quick thought:
Let it output what it is "reloading" and not what is loaded for the
first time. OTOH does enter! really do any reloading?
--
regards,
Jakub Piotr Cłapa
___
Why is it more useful for enter! to give this output than load or require?
Carl Eastlund
On Fri, Dec 10, 2010 at 3:05 PM, Noel Welsh wrote:
> It is moderately useful to see what is reloaded if you renter enter!
>
> N.
>
> On Fri, Dec 10, 2010 at 5:26 PM, Carl Eastlund wrote:
>> Whenever I use e
It is moderately useful to see what is reloaded if you renter enter!
N.
On Fri, Dec 10, 2010 at 5:26 PM, Carl Eastlund wrote:
> Whenever I use enter! in racket, it spews a huge list of notifications
> of every file being loaded. Is there any reason for this? It seems
> like a complete waste of
On Dec 10, 2010, at 11:38 AM, Robby Findler wrote:
> Both this and Sam's idea seem like good ways to improve the error
> message to me. Not sure if Casey or Sam (or Christos?) wants to try to
> their hand at the actual formatting or not. I will, if not.
A couple of things to note for anyone who at
Whenever I use enter! in racket, it spews a huge list of notifications
of every file being loaded. Is there any reason for this? It seems
like a complete waste of screen space, it obscures anything useful I
did before the enter!, and the first time it made me worry I'd done
something wrong.
--Ca
On Fri, Dec 10, 2010 at 10:38 AM, Robby Findler
wrote:
> Both this and Sam's idea seem like good ways to improve the error
> message to me. Not sure if Casey or Sam (or Christos?) wants to try to
> their hand at the actual formatting or not. I will, if not.
>
> I don't like the "possible fixes inc
Both this and Sam's idea seem like good ways to improve the error
message to me. Not sure if Casey or Sam (or Christos?) wants to try to
their hand at the actual formatting or not. I will, if not.
I don't like the "possible fixes include" language, tho-- I prefer
that we either say that this error
Three hours ago, Robby Findler wrote:
> Okay. So I'll just start by spelling out the pieces of information
> that's there to be put into a message:
>
> - is the contract blaming the party where the contract was written (or not)
> - the source location where the contract was written down
> - the
On Fri, Dec 10, 2010 at 7:34 AM, Sam Tobin-Hochstadt wrote:
> On Fri, Dec 10, 2010 at 8:26 AM, Casey Klein
> wrote:
>> On Fri, Dec 10, 2010 at 7:00 AM, Eli Barzilay wrote:
>>>
>>> As for a suggestion, I don't have anything concrete (and I don't have
>>> nearly enough contract experience to say s
About two weeks ago, Matthew Flatt wrote:
> Pango likes to warn you when it sets up certain font substitutions.
> I don't know whether there's any way to turn it off.
This bugged me a little, then when I got the same warnings on windows
it became more annoying. To make a long story short, the war
On Fri, Dec 10, 2010 at 9:26 AM, Stevie Strickland wrote:
> On Dec 10, 2010, at 8:12 AM, Robby Findler wrote:
>> If someone besides me wants to take a stab at formulating a less painful
>> message, the code is in collects/racket/contract/private/blame.rkt and,
>> thanks to Stevie's refactoring,
On Dec 10, 2010, at 8:12 AM, Robby Findler wrote:
> If someone besides me wants to take a stab at formulating a less painful
> message, the code is in collects/racket/contract/private/blame.rkt and,
> thanks to Stevie's refactoring, very easy to work with.
While I'd love to take the credit on th
On Fri, Dec 10, 2010 at 8:26 AM, Casey Klein
wrote:
> On Fri, Dec 10, 2010 at 7:00 AM, Eli Barzilay wrote:
>>
>> As for a suggestion, I don't have anything concrete (and I don't have
>> nearly enough contract experience to say something concrete) -- but in
>> general I prefer to see those importa
On Fri, Dec 10, 2010 at 7:00 AM, Eli Barzilay wrote:
>
> As for a suggestion, I don't have anything concrete (and I don't have
> nearly enough contract experience to say something concrete) -- but in
> general I prefer to see those important bits first, and the vague
> human text later.
>
This or
Okay. So I'll just start by spelling out the pieces of information
that's there to be put into a message:
- is the contract blaming the party where the contract was written (or not)
- the source location where the contract was written down
- the contract, written out
- the names of the two par
Thanks, Casey. Perhaps I should have announced our intentions in
changing this message but you've pretty much gotten it (implicitly
written below).
A little more detail: recently I got a complaint that the contract
system error messages were wrong, a complaint that I had now heard
many many times.
15 minutes ago, Robby Findler wrote:
> Positive suggestions for improvement are welcome. Bad analogies that
> don't help are like someone coming over to your house and hitting
> you with hammer before you even get a chance to have some coffee.
I didn't even intend for this to be a (bad) analogy --
Positive suggestions for improvement are welcome. Bad analogies that
don't help are like someone coming over to your house and hitting you
with hammer before you even get a chance to have some coffee.
Robby
On Fri, Dec 10, 2010 at 5:01 AM, Eli Barzilay wrote:
> 5 minutes ago, Casey Klein wrote:
Two minutes ago, Eli Barzilay wrote:
> 5 minutes ago, Casey Klein wrote:
> >
> > For anyone following at home, the change turns this message [...]
>
> Ah, so that's what broke enough tests to make the build log explode...
See also the drdr party:
http://drdr.racket-lang.org/21707/collects/tests/
5 minutes ago, Casey Klein wrote:
>
> For anyone following at home, the change turns this message [...]
Ah, so that's what broke enough tests to make the build log explode...
> into this one
>
> /Users/clklein/tmp/contract-violator.rkt:9.17: found a contradiction
> between the contract (-> any
On Thu, Dec 9, 2010 at 3:50 PM, wrote:
>
> 18dacad Robby Findler 2010-12-09 10:20
> :
> | a first attempt at a rewording of the blame error messages to admit the
> possibility that the contract was wrong and also to claim that fixing the
> blamed module or the contract is all that is required
21 matches
Mail list logo
