That is cool. Maybe someday Elvish will learn that magic
I personally would not like that. The name is fine, but doesn't mean that its behavior needs to include those references.
1 reply
Also not everyone would get the references. Like me - I use Elvish because it's a good shell, but I'm not particularly a fan of LOTR, and I don't even know what Roguelike games are ;)
1 reply
Anyway I have no work assigned right now on the file module. So if anyone needs mu help, let me know
I have bash, zsh and Elvish set up
I know what each of the components will do but i am not sure of the output
Start with any portion of that statement. For example, what does
put "x="$x do?
It will concat them
Put will print them on the screen
"X=valueofX"
Like that
That is partially correct for the statement as a whole. I, however, asked what does
put "x="$x do.
Its 8:30 am and I just woke up
Put is responsible for printing but it sends the words throught stdout 1 string at a time
Put wow elvish will do ->
Wow
Elvish
Put "x="$x will do
X=valueOfX
Correct, depending on what you mean by "stdout". The
put command outputs its values on the value channel. Which isn't the same thing as the stdout byte channel.
I didn't know that
You should take some time to read the documentation more than once. For example, http://localhost/elvish/learn/tour.html#value-pipelines is relevant to this discussion.
1 reply
I mean that it is not the same as stdout channel
My previous link should have been to elv.sh rather than localhost/elvish (which is what I use to verify the correctness of changes to the documentation).
i was going to refer you to #elvish-zh but i found that i never bothered to set up bridging for that channel...
Day 10 of main laptop being broken, I finally decided to set up a dev environment in my Windows laptop (which I normally only use for games). Should be able to get back to PR reviews by this weekend too
The official "windows terminal" app is not bad - it supports tabs and splitting panes and I was able to replicate my tmux key bindings to appease my muscle memory
I'm intentionally not using WSL - I may work on some Windows compatibility issues hopefully bringing Windows support out of experimental status
IMO, WSL is really only useful to people who prefer Windows and occasionally want to experiment with Linux without having to setup a native Linux (or BSD) distro.
Do you think there's anything that prevents from being a full-fledged development environment? If you are referring to incompatibilities with a real Linux kernel (like the mmap issue that causes boltdb to panic) - those are resolved with the new VM-based WSL 2
WSL 1 was a paravirtualization mechanism implemented by implementing Linux syscalls in the Windows kernel, so some incompatibility was unavoidable. WSL 2 runs mainline Linux kernels in a Hyper-V VM
I installed WSL 2. It's effectively not much different than using VMware on macOS to host Windows (which is what I do). So, yeah, if you're primarily a "Windows" person who sometimes needs to do development on Linux WSL 2 is a pretty good option.
I don't bother with WSL anymore because it's better to use Elvish in a native Windows terminal to understand where there are compatibility problems.
Like the need for a
path:temp-file command that works on Windows and UNIX.
There may be more people who use Windows to develop Linux software than you might think - I personally know a lot of developers who are otherwise Windows users but are "forced" to develop against Linux because their companies have servers that run Linux
Before WSL, they either had to use a test server to test their code or use a more heavyweight VM, and WSL simplifies their workflows considerably