I think it is better if we don't add more configurations at that
level. DrRacket should only reflect what the program text already
says, not try to control it (as much as we can).
Better to look for ways that #lang can have the right kind of control here.
Robby
On Fri, Feb 1, 2019 at 10:36 AM La
But I should add that that's not a big deal to me now, since at least now I
know how to work around it.
On Fri, Feb 1, 2019 at 4:06 PM Laurent wrote:
> Or better yet, maybe replace the choice between print and write to a
> boolean choice on the initial value of 'print-as-expression'.
>
> Ideally
Or better yet, maybe replace the choice between print and write to a
boolean choice on the initial value of 'print-as-expression'.
Ideally, changing this value at the top of the module to evaluate would
overwrite this default though.
On Fri, Feb 1, 2019 at 4:04 PM Sam Tobin-Hochstadt
wrote:
> C
Could it be changed to also set `(print-as-expression)` appropriately?
Sam
On Fri, Feb 1, 2019 at 11:02 AM Robby Findler
wrote:
>
> Ah, right! I forgot about that setting. Yes, what you describe is
> exactly what happens.
>
> Robby
>
> On Fri, Feb 1, 2019 at 9:57 AM Laurent wrote:
> >
> > I thi
Ah, right! I forgot about that setting. Yes, what you describe is
exactly what happens.
Robby
On Fri, Feb 1, 2019 at 9:57 AM Laurent wrote:
>
> I think I've found the problem.
>
> In the preferences, I chose 'Output syntax | Output style | write' which
> seems to force the behaviour of (print-a
I think I've found the problem.
In the preferences, I chose 'Output syntax | Output style | write' which
seems to force the behaviour of (print-as-expression #f) without actually
changing the parameter.
After changing this preference to print, I observe a consistent behaviour
between DrRacket and
That's not what I see in DrRacket. Try hitting "Run" again on a
lang-line only DrRacket buffer and sending the entire REPL?
Welcome to DrRacket, version 7.2.0.3--2019-01-15(-/f) [cs].
Language: racket, with debugging; memory limit: 512 MB.
> (~v 'x)
"'x"
>
On Fri, Feb 1, 2019 at 9:48 AM Laurent
I'm in #lang racket for DrRacket, and I assume it's the same for the
command line when merely starting "$ racket"
On Fri, Feb 1, 2019 at 3:39 PM Robby Findler
wrote:
> This setting is controlled by the language of the original file (so
> the one in the definitions window in DrRacket or the one
This setting is controlled by the language of the original file (so
the one in the definitions window in DrRacket or the one you are
"inside" in the repl if you're in one). Possibly those are different
for you, Laurent?
Robby
On Fri, Feb 1, 2019 at 9:33 AM Sam Tobin-Hochstadt wrote:
>
> I see th
I see the same behavior in DrRacket as in command line racket.
On Fri, Feb 1, 2019 at 10:19 AM Laurent wrote:
>
> I'm seeing a difference that I can't explain. In the interactions below, look
> for the leading quote in the output string on the commandline, and its
> absence in DrRacket.
>
> The
I'm seeing a difference that I can't explain. In the interactions below,
look for the leading quote in the output string on the commandline, and its
absence in DrRacket.
The same problem happens when running a module containing the same code, so
it's not a top-level issue.
Is there another parame
11 matches
Mail list logo
