Can some of you folks who use Windows for development suggest some guides on workflow? For example, regarding WSL (Bash on Windows), I’ve read stern warnings against modifying any WSL files from Windows. So that means I’m not supposed to use Windows Atom editor to edit files that exist in my WSL f…

[image] OvermindDL1: What editor does not auto-detect what line endings a file already uses?! o.O? All of them, when you’re creating a new file.

[image] notriddle: All of them, when you’re creating a new file. Ah, I have everything default to \n only then. ^.^ I’d not doubt that there are .gitattribute plugins for things like atom or so that can auto-detect though, or at the very least it would be so easy to make one. That is a use…

[image] OvermindDL1: Uhh, not to me, not even remotely… Plus I need to compile stuff to run on a Windows 2008 server that does not have WSL, thus compiling inside WSL I do not think will work well for that. :wink: Cross-compilers work within WSL. [image] OvermindDL1: That is such a wtf…

[image] OvermindDL1: I’d not doubt that there are .gitattribute plugins for things like atom or so that can auto-detect though, or at the very least it would be so easy to make one. That is a useful idea, hmm… The problem is that dropping a * -text into your gitattributes file doesn’t tell i…

[image] notriddle: Cross-compilers work within WSL. Does mix use cross-compilers? [image] notriddle: OTOH, overriding wget and curl was a horrible, and deliberate, choice of action. These are the ones I am referencing, plus iex. They are entirely not functionally equivalent in any fo…

[image] OvermindDL1: These are the ones I am referencing, plus iex. They are entirely not functionally equivalent in any form other than the absolute basics. Even the command args are different. PowerShell iex, unlike PowerShell wget and curl, is not an attempted replacement for Elixir iex.…

[image] notriddle: PowerShell iex is short for Invoke-Expression. The fact that they share a name is a coincidence. Then it should be IEX, not iex. :wink:

PowerShell commands are case-insensitive. Also, that would be IEx, with mixed case.

[image] notriddle: PowerShell commands are case-insensitive. Also, that would be IEx, with mixed case. Ah true, it should be IEx. It’s not case sensitive? Wtf? That is a good reason not to use it right there…

[image] OvermindDL1: If you really need the default then just do env time <blah> (Remember that env <cmd> always uses the systems command, not a shell built-in). And PowerShell has a built-in called start. I used the .bat suffix to distinguish Invoke-Expression from Interactive Elixir, but th…

Windows and Linux co-development

Questions & Help Questions

OvermindDL1 July 21, 2017, 4:06pm 35

Then it should be IEX, not iex.