[erlang-questions] Some ideas for the shell.

[Pierre Fenoll]

On the REPL enhancements wishlist train, I have opened an issue on the bug
tracker a while ago to add tab completion for variable names.
One of the comments on it was asking for documentation access too, as the
Python REPL has been offering for some time.

Since some things may be undesirable on production REPLs, maybe a flag that
can be set from a rebar3 profile can help toggle some features thus
allowing more enhancements for dev REPLs.

On Mon 4 Dec 2017 at 08:22, bengt e <cean.ebengt@REDACTED> wrote:

> Greetings,
>
> Is 2) similar enough to file:consult/1, to maybe warrant it to be called
> 'consult' instead?
>
> bengt
>
> On Mon, Dec 4, 2017 at 1:09 AM, Richard A. O'Keefe <ok@REDACTED>
> wrote:
>
>> There are two things that would make life easier for me using the
>> Erlang shell, and I thought I'd ask for thoughts here before writing
>> them up as EEPs.
>>
>> (1) import(Module, Functions)
>>     where Functions is a list of {Name,Arity} pairs.
>>     Effect: calls to that function from the shell don't need a
>>     Module prefix, just like -import directives in files.
>>
>>     Reason: I often want to call a function or a small number of
>>     functions many times to explore it or test it.
>>
>> (2) include(FileName)
>>     Effect: reads FileName as a sequence of Erlang expressions and
>>     interprets them as if typed into the same shell.
>>
>>     Reason: set up constants and imports.
>>
>>
>>
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions
>>
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
-- 

Cheers,
-- 
Pierre Fenoll
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20171204/a27a96d4/attachment.htm>