Fixed the quotes now. Copy and paste error.
Thanks for catching those. Gave you credit in the article.
Fixed the quotes now. Copy and paste error.
Hi, I’m the maintainer of Comeonin, and it’s great to see posts like this. It’s good to have more detailed information for Windows users.
Also another bug (I think with iex, not your article, but probably want to mention this too), if you spool up iex with --sname or --name then the prompt will not be colored (although output will). I was not able to find a quick way to resolve this issue, but like stated, seems like an iex bug.
I seem to have posted this reply under the wrong post, it was meant for you @rodwatkins
Let me look into it. I am not at my machine at the moment, but I’ll see if I can get it to compile when I am.
For a windows user, how has your experience been?
What is your Linux-tools setup?
Virtual-box Ubuntu or something else?
Also, do you have a go-to setup for running elixir successfully on windows?
The Elixir Windows community could really do with some official step-by-step guidance on setting up a (near) perfect windows environment for Elixir, that can handle ANY
make compilation issues.
I never made a step-by-step but here is how I made it work, roughly (NOTE: It requires at least Windows 10 Anniversary Edition be installed):
- Install the Chocolatey Windows package manager.
- Install Erlang via
choco install erlangin an elevated CMD shell. (SIDE NOTE: I use ConEmu64 as a shell, makes life much easier and nicer on the command line in Windows)
- You can choose between
choco install elixirnext, or to manually download it from the Elixir releases. I prefer the latter since the maintainer of the Elixir package in Chocolatey doesn’t seem fast, and manual install of Elixir is as simple as extracting a ZIP + adding an entry in your
It’s easy from there on. The only possible issues are Git and SSH. I use
msysgit 2.x but I had trouble with it and can’t really vouch for it. SSH is just fine if you use PuTTY or KiTTY (or any other fork really) however, but a proper Git setup in CMD is something I never really chased fully.
Using this setup, what has been your experience with
Have you successfully used / compiled the
Ranch Erlang module? or any other Erlang modules that have a
make compilation step?
This is where my Elixir on windows experience breaks down.
Apologies for misunderstanding, I didn’t mean to pollute.
As far as
make goes, Windows hasn’t really progressed much during the last 10 years. You can always use Cygwin or various GNU Windows environments (Mingw, UnxUtils etc.) but frankly, I believe our best bet for now is to sort of bypass Windows and just use Bash on Ubuntu on Windows 10 (the native Ubuntu inside it).
(Trouble with this approach however is that Erlang/OTP 19.0 and 19.1 don’t work; you have to use 18.0, at least for the time being)
You are correct, @svarlet, sorry.
I no longer am using Windows because I found that setting up Ubuntu + Erlang was actually quite easy and painless. I started off with Hyper-V and Ubuntu VMs, and then gradually transitioned myself to running it on bare metal as my experience with VMs in Ubuntu has been less than fruitful. Then I found Elixir and this made the process even easier, since Elixir does documentation so ridiculously well.
As for my current tooling, I point you to the Atom thread. Emacs has too many chords for my taste,
(Thanks for moving this question @AstonJ…I had asked that it be moved when starting to write this thing!)
Hey! I know the last reply here been a while but I hope you can help me…
I’ve been setting up my elixir environment as described in the article but got two problems with credo:
It does show some strange characters instead of vertical lines and symbols and no colors. Color in iex work fine. I guess there’s something I need to configure or install for it to work in the command line (I’m using cmder) :
Ôöâ [R] ÔåÆ Modules should have a @moduledoc tag.
Ôöâ lib/credo-test.ex:1:11 #(CredoTest)
Ôöâ [C] Ôåù File is using windows line endings while most of the files use unix line
Ôöâ lib/credo-test.ex #()
Please report incorrect results: https://github.com/rrrene/credo/issues
Analysis took 0.1 seconds (0.01s to load, 0.09s running checks)
3 mods/funs, found 1 consistency issue, 1 code readability issue.
Showing priority issues: Ôåæ Ôåù ÔåÆ (use
--strictto show all issues,
It does not show the credo results in linter. It always shows “0 0 0” (see screenshot below)
I’m new to atom and elixir, so please be patient and nice with me Hope someone can help me solve my problems.
The atom-credo-linter is fundamentally broken by design. It will not work unless you are using a linux system (not even mac, well, but sometimes it will…) and are on an english locale and mix is installed at a certain location where it was found by the creator of the plugin.
Also the creator of the pliugin does not use atom by himself, so the problems will probably never get fixed: https://github.com/smeevil/linter-elixir-credo/issues/10#issuecomment-257242841
linter-elixir-credo is working on Windows 10 here for me, though I do have the entire mingw suite of tools installed so that may help.
As you can see from the linked issue, it’s been a while it was discussed. Roughly at that time I also had a chat with other people hit by that problem and the only people that we were able to find were running on linux. None of the windows folks had luck.
Anyway. Since even my workspace is moving away from atom in favor of VScode and emacs, I do not care any more for atom.
I’m currently searchin for the best environment for elixir coding on windows. Are there some articles like the one above but for VScode?
I’m not aware of any articles, tutorials or stuff.
I just opened my first
*.ex, got a banner which told me that there were plugins for this language, which I installed and then dropped about three weeks ago after the ElixirLS has been released.
VScode just worked for me, not like atom where credo didn’t work correctly, it also didn’t crash in the last 6 month.
Thanks @NobbZ I’ll try my luck
My environment is Windows 10 with Vim and Powershell.
Every once and awhile I go for something a little bit more risqué and do
Are you really trying to tell me that there is ANY other way to code? Nonsense.