You mean that when you are in the code editor from the debugger and do cmd+o it goes in the inspector embedded in the debugger or is your use case a little more general? 


On Fri, May 2, 2014 at 3:57 PM, Alexandre Bergel <alexandre.bergel@me.com> wrote:
ok!

Also, it would be great that when I use “cmd-o” in the browser, it flows as in the playground :-) Do you see what I mean?

Cheers,
Alexandre


On May 2, 2014, at 10:49 AM, Andrei Chis <chisvasileandrei@gmail.com> wrote:

> Hi Alex,
>
> There is right now a bug when complying code that triggers certain warnings.
>
> https://code.google.com/p/moose-technology/issues/detail?id=1062
>
> To be fixed really soon.
>
> Cheers,
> Andrei
>
>
>
>
>
>
> On Fri, May 2, 2014 at 3:43 PM, Alexandre Bergel <alexandre.bergel@me.com> wrote:
> Hi!
>
> It often appears that compiling a method in the debugger does not work properly.
> For example, if I have the method:
>
> A>>foo
>         self halt
>
> Running A new foo opens a debugger. In the debugger if I modify foo by the following broken code:
> foo
>         | t |
>         [ :t | ]
>
> The code gets compiled without giving any warning. But foo remains with “self halt”.
> I would expect an error window to popup up, but not to loose my change.
>
> Cheers,
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.