The problem is that dropping a * -text into your gitattributes file doesn’t tell it to use Unix line endings. It tells it to not change them, whatever it may be. If I’m creating a .reg file for Windows, I want my text editor to use Windows line endings, and if I’m creating or editing an HL7 message, I want the lines to be terminated by a lone “\r”.
notriddle
0
OvermindDL1
Does mix use cross-compilers?
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.
That is for the purpose of getting more accurate timing data, which is what it’s purpose is. 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).
.gitattributes can specify those. text=auto means use the system default (when pulling/pushing), which also works fine for an editor default as well. 
0
notriddle
PowerShell iex, unlike PowerShell wget and curl, is not an attempted replacement for Elixir iex. PowerShell iex is short for Invoke-Expression. The fact that they share a name is a coincidence.
0
OvermindDL1
notriddle
OvermindDL1
Ah true, it should be IEx.
It’s not case sensitive? Wtf? That is a good reason not to use it right there…
1
notriddle
And PowerShell has a built-in called start. I used the .bat suffix to distinguish Invoke-Expression from Interactive Elixir, but this works too:
start iex --werl
Executables are case-insensitive under Windows. Given a choice, I’d rather have the PowerShell builtins also be case insensitive than have exes and builtins disagree.
Also, having executables on your system with names that differ only in case is a serious system configuration smell.
0
OvermindDL1
Oooo, useful, I’ll give that a try next time I need. Thanks!
Not under Windows, but rather under the filesystems it includes by default. A custom filesystem does not need such a limitation as case-insensitivity.
Executables sure, but not commands. I’ve made a LOT of functions and aliases and such in my shell that differ from an executable via just their case so that I can have special functionality without needing to replace the existing functionality.
This is also why it is a wtf that powershell has case-insensitive ‘commands’. o.O?!
0
notriddle
False. Case-insensitive semantics are provided by the Win32 subsystem on top of whatever native filesystem you’re using. With the right API calls, I can do this:
NTFS is capable of a lot. It’s the Win32 subsystem that limits you.
0