Re: [elixir-core:5956] Proposal: Stop appending a trailing dot when autocompleting modules in IEx

2016-06-23 Thread Eric E. 
I like it as well.

Also for those looking for a way to "cancel the current line" in iex, you 
can type #iex:break at any time to return to do so.

On Thursday, June 23, 2016 at 2:15:46 PM UTC-4, José Valim wrote:
>
> Sounds good to me too!
>
>
>
> *José Valim*
> www.plataformatec.com.br
> Skype: jv.ptec
> Founder and Director of R
>
> On Thu, Jun 23, 2016 at 8:11 PM, Paul Clegg  > wrote:
>
>> I can get behind this as a no-config-option compromise.  :)
>>
>> ...Paul
>>
>>
>>
>> On Thu, Jun 23, 2016 at 10:59 AM, Aleksei Magusev > > wrote:
>>
>>> I'm wondering, what if we go with combined approach:
>>> at first TAB we're getting autocomplete up to the "dot"
>>> and next TAB is appending the "dot".
>>>
>>> I believe it can be a good compromise. :)
>>>
>>>
>>> On Thursday, June 23, 2016 at 7:29:24 PM UTC+2, Myron Marston wrote:

 Since I haven't found a good way in iex to "cancel the current line", 
> if I get in that spot, I lose a lot of history and current variables and 
> whatnot.


 I've tend to do this, too, even though I've been using Elixir as my 
 main language at work for nearly a year.  It's a big reason I find the 
 appended period to be so annoying.

 If anything, my vote would be to make it optional -- but default it to 
> NOT appending the dot.

  
 I agree.  If we make it a config option, I think it would help 
 newcomers to the language if we made it opt-in instead of opt-out.  Given 
 that most auto-complete tooling does not usually add an extra period, 
 newcomers to the language are not going to expect it, and won't know how 
 to 
 get out of the "current line" issue Paul mentioned without exiting the IEx 
 session and restarting it.  Furthermore, since they are a newcomer, they 
 are not likely to know about the config option.

 OTOH, experienced users who may want the appended period will 
 understand IEx's config system and can more easily configure it for their 
 needs.

 Myron

 On Thursday, June 23, 2016 at 9:51:02 AM UTC-7, ...Paul wrote:
>
> I'm actually with Myron.  Since I haven't found a good way in iex to 
> "cancel the current line", if I get in that spot, I lose a lot of history 
> and current variables and whatnot.  If anything, my vote would be to make 
> it optional -- but default it to NOT appending the dot.  I prefer UI 
> elements that help me do what I want to do, not make presumptions about 
> what I want to do.
>
> ...Paul
>
>
>
> On Thu, Jun 23, 2016 at 9:42 AM, Louis Pop  
> wrote:
>
>> I share Jose' opinion here, but making it configurable sounds good.
>>
>> Cheers,
>> Louis
>>
>> On 23 June 2016 at 17:40, Myron Marston  wrote:
>>
>>> This behavior of IEx has always surprised and annoyed me. I 
>>> regularly type h [first few chars of mod name] in IEx 
>>> to read the read the moduledoc of a particular module, and the trailing 
>>> period gets in the way every time.
>>>
>>> Here’s a demonstration showing what happens to me regularly when I 
>>> try to read the @moduledoc for a module:
>>>
>>> [image: iex_autocomplete_original]
>>>
>>> With this change, it avoids this problem:
>>>
>>> [image: iex_autocomplete_improved]
>>>
>>> I opened a PR with this change 
>>>  but was asked to 
>>> redirect conversation here for community feedback first. On the PR, 
>>> @antipax said (and @josevalim concurred):
>>>
>>> I’m not in support of merging this, if only because the vast 
>>> majority of the time I autocomplete a module in IEx it is to make a 
>>> remote 
>>> call.
>>>
>>> I thought the purpose of autocomplete in IEx is to autocomplete 
>>> tokens (e.g. module and function names) not to guess the intention of 
>>> the 
>>> programmer and add additional characters after the token. IMO, it’s 
>>> much 
>>> more natural to just complete the module name, and people who want to 
>>> do a 
>>> remote call (or navigate to a “nested” module) can type a period, than 
>>> to 
>>> add the period and force the programmer to delete it. After all, I 
>>> believe 
>>> the autocomplete plugins in most text editors/IDEs would just 
>>> autocomplete 
>>> the module name, and not add the period.
>>>
>>> On the PR @antipax also said:
>>>
>>> I would be in support of making this configurable, however.
>>>
>>> Having this be configurable would meet my needs as long as I could 
>>> configure it globally (presumably in ~/.iex.exs) but the trailing 
>>> dot still feels like an odd default to me.
>>>
>>> Thoughts from the community?
>>>
>>> Thanks,
>>> Myron

Re: [elixir-core:5898] Elixir v1.3.0-rc.0 released

2016-06-02 Thread Eric E. 
mix local.rebar --force
On Jun 2, 2016 1:48 PM, "Myron Marston"  wrote:

> Thanks Eric!  I can confirm it's available on Travis now.
>
> I'm running into an issue with using it on Travis, though...when my build
> gets to a step that does:
>
> mix compile --warnings-as-errors --force
>
>
> ...it gets stuck at this prompt:
>
> Could not find "rebar3", which is needed to build dependency :idna
>> I can install a local copy which is just used by Mix
>> Shall I install rebar3? [Yn]
>
>
> ...and then the build times out after 10 minutes.
>
> I thought there was a flag to force mix to download things like rebar3
> when needed so it can work in situations like this but I haven't been able
> to figure out what the flag is.  Anyone have a suggestion?
>
> Thanks,
> Myron
>
> On Thu, Jun 2, 2016 at 8:30 AM, Eric Meadows-Jönsson <
> eric.meadows.jons...@gmail.com> wrote:
>
>> It should be available now.
>>
>> On Wednesday, 1 June 2016, Myron Marston  wrote:
>>
>>> The new 1.3 features look really great!  Any idea when 1.3.0-rc.0 will
>>> be available on hex so it can be used on travis?
>>>
>>> On Monday, May 30, 2016 at 6:41:32 AM UTC-7, José Valim wrote:

 Hello everyone,

 We are glad to announce our first release candidate for Elixir v1.3.0.
 This release includes the new Calendar types as well as many improvements
 to the toolchain. We hope it will make everyone more productive, specially
 when using Mix and ExUnit.

 Since this is a release candidate, there is a chance your package
 managers won't be updated to include it. Luckily, you can use a
 version manager
 
  or compile from source
 
 .

 To learn more about this release, read the CHANGELOG
 
  or access its docs .

 We recommend everyone to take this new release for a spin and let us
 know how it goes. This release should be fully backwards compatible, please
 report any inconsistencies you find in our issues tracker
 .

 Happy coding!

 *José Valim*
 www.plataformatec.com.br
 Skype: jv.ptec
 Founder and Director of R

>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "elixir-lang-core" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to elixir-lang-core+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/elixir-lang-core/3460f9bf-07fb-4e56-8647-a63130fe900d%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Eric Meadows-Jönsson
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "elixir-lang-core" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/elixir-lang-core/JptOMxrLxcs/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> elixir-lang-core+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/elixir-lang-core/CAM_eaphTVHBgR%2B0SUKG-sdjeXS2cNAPC7P7d%3Dwj5oNvcy2-ofA%40mail.gmail.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "elixir-lang-core" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/elixir-lang-core/JptOMxrLxcs/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> elixir-lang-core+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elixir-lang-core/CADUxQmuXfMoJ7gKiVrYoB4hsRadfPEjs0ft5wvcLzMn-%2B_5uiA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elixir-lang-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit

Re: [elixir-core:5886] Elixir v1.3.0-rc.0 released

2016-05-31 Thread Eric E. 
It should be possible to use --callers to generate ctags. Any and all 
remote calls are included.

On Tuesday, May 31, 2016 at 9:00:42 AM UTC-4, Wojciech Kaczmarek wrote:
>
> Wow this looks like a really cool set of changes, esp. in the area of 
> tooling.
>
> mix xref and mix test --stale sound great!
>
> Now if I understand it correctly, mix xref --callers  can be used to 
> generate ctags, right? Seems better than scanning the source which always 
> has some heuristics involved. Does it also cover the dependencies and 
> standard library?
>
>
> cheers,
> W.
>
>
>
> On Mon, May 30, 2016 at 3:41 PM, José Valim  > wrote:
>
>> Hello everyone,
>>
>> We are glad to announce our first release candidate for Elixir v1.3.0. 
>> This release includes the new Calendar types as well as many improvements 
>> to the toolchain. We hope it will make everyone more productive, specially 
>> when using Mix and ExUnit.
>>
>> Since this is a release candidate, there is a chance your package 
>> managers won't be updated to include it. Luckily, you can use a version 
>> manager 
>>  or 
>> compile 
>> from source 
>> 
>> .
>>
>> To learn more about this release, read the CHANGELOG 
>>  or 
>> access 
>> its docs .
>>
>> We recommend everyone to take this new release for a spin and let us know 
>> how it goes. This release should be fully backwards compatible, please 
>> report any inconsistencies you find in our issues tracker 
>> .
>>
>> Happy coding!
>>
>> *José Valim*
>> www.plataformatec.com.br
>> Skype: jv.ptec
>> Founder and Director of R
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "elixir-lang-core" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to elixir-lang-co...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elixir-lang-core/CAGnRm4K4Hy%2BWpNyp_QbnkS3q66Hfq9KzF7kWZUFfKw8PFd_kuw%40mail.gmail.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elixir-lang-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elixir-lang-core/e4d3dddc-7eef-44a6-b49f-ad86711ab73d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.