enmadsen.com
>
>
> On Fri, Jul 15, 2016 at 9:51 AM, Adam Lindberg <he...@alind.io> wrote:
>> Yeah, a family of such functions makes sense.
>>
>> Not every deployment includes IEx necessarily (embedded systems, Erlang
>> releases including Elixir depen
;
> José Valim
> www.plataformatec.com.br <http://www.plataformatec.com.br/>
> Skype: jv.ptec
> Founder and Director of R
>
> On Fri, Jul 15, 2016 at 4:10 PM, Adam Lindberg <he...@alind.io
> <mailto:he...@alind.io>> wrote:
> After thinking a bit mo
(similar to Erlang
> regs()).
>
>
>
> José Valim
> www.plataformatec.com.br <http://www.plataformatec.com.br/>
> Skype: jv.ptec
> Founder and Director of R
>
> On Fri, Jul 15, 2016 at 3:27 PM, Adam Lindberg <he...@alind.io
> <mailto:he...@al
Would there be any interest in a new function Application.process_tree/1? I’m
envisioning something like the shell `tree` utility but for an application
process tree for situations when :observer cannot be started (for example, on a
remote session via SSH).
Cheers,
Adam
--
You received this
I know it’s not the prettiest solution, but if it is really a unique ID you
could use an atom (or string) instead:
%{ "specialId" => :"10002" }
Cheers,
Adam
> On 21. Apr 2018, at 10:06, Allen Wyma wrote:
>
> First of all, I'd like to say thanks so much for the
There’s also :sys.get_state(pid|name) which returns the state for debugging
purposes.
Cheers,
Adam
> On 31. Jan 2018, at 00:39, José Valim wrote:
>
>
> I am not in favour of the proposal but can see some merit in handlers not
> modifying the state. For that case we