And a single command invocation to dispatch on that map
WooT! I'm (mostly) up and running on a shiny new Apple Studio server (the new Mac Pro server based on Apple Silicon; aka the M1 chip). Still to do is migrating HomeBrew, and the apps it manages, from x86_64 to arm64 versions. It took an entire day to get to this point but I'm now no longer using an ancient 2012 Mac Pro tower. These sorts of upgrades are exhausting even with Apple's excellent TimeMachine import capability. I can't imagine someone who isn't a developer going through this process. On the other hand I have apps, like the home automation app from https://www.indigodomo.com/ and VMware Fusion, that most people don't have to deal with vis-a-vis compatibility with new hardware/software that considerably complicates the process.
there is no builtin function for that, so you're gonna have to make one
One way to reverse a list: var @l2 = $l1[(range (- (count $l1) 1) -1)]
This is a test message since I had to nuke my Matrix credentials after migrating to a new Apple Studio server since I had not saved my Matrix credentials in 1Password (the app I use to manage secrets). I just want to make sure I can still interact with this channel and people recognize me. 👽️
It's interesting, and annoying, how major upgrades of this nature tend to identify ancient cruft that needs cleanup. For example, I had two scripts I depend on that were still written in the Fish shell. I didn't want to reinstall Fish on my new server (since I stopped using Fish several years ago) so I rewrote them in Elvish.
This is a bit weird - seems sth. is broken with my starship promp and whenever i change to a specific directory it crashes and that causes elvish and my terminal instance to crash as well 🤔.
[shell] 2022/05/01 13:40:26 signal child exited
[shell] 2022/05/01 13:40:26 signal child exited
[shell] 2022/05/01 13:40:26 signal urgent I/O condition
[shell] 2022/05/01 13:40:26 signal urgent I/O condition
[shell] 2022/05/01 13:40:26 signal urgent I/O condition
[shell] 2022/05/01 13:40:26 signal urgent I/O condition
[shell] 2022/05/01 13:40:26 signal child exited
[shell] 2022/05/01 13:40:26 signal child exited
[shell] 2022/05/01 13:40:27 signal child exited
[shell] 2022/05/01 13:40:27 signal urgent I/O condition
[shell] 2022/05/01 13:40:28 signal urgent I/O condition
[shell] 2022/05/01 13:40:28 signal child exited
[shell] 2022/05/01 13:40:28 signal urgent I/O condition
[shell] 2022/05/01 13:40:28 signal hangup
1 reply
What is "sth"? The Elvish log implies some process is sending SIGHUP to the elvish process.
1 reply
Dear all, for those of us using carapace-bin for completion in elvish, there is a great new feature, spec files, added to V0.12: https://github.com/rsteube/carapace-bin/releases/tag/v0.12.0 — this makes it easy to specify completions using YAML for personal commands. Thank you rsteube !!!
You write a YAML spec file and you add it to your rc.elv like so:
eval (carapace --spec example.yaml|slurp) — apparently we will be able to specify a folder of spec files too. carapace is regularly updated and at least via @rsteube's homebrew tap, you can auto-update as soon as releases are made...
I don't quite undserstand how the
carapace --spec command knows it is elvish running, at least for built-in completers you need to specify elvish as eval (carapace git elvish|slurp) — but it works.
1 reply
carapace already comes with 426 completions that integrate so well with elvish, so I only have a couple of my own commands that actually need spec files in the end.
Maybe it saves a few microseconds if it is specified? 😂
Nice, will try that out. I did not know there was a homebrew tap. Will add that one as well
Thanks!
FYI the chat room bridge seems broken now - I was going to take a look today but I'm sick now. Should be able to fix it and set up some monitoring when I get better
Hey all, quick question, I'm trying to get the output of a command that segfaults, but I can't seem to come up with a syntax that works. I have an executable,
./foo, that will print some text and then segfault. I'd like to capture the text it outputs. Constructs like ?(./foo) will catch the error, but I can't seem to capture the text. Any ideas?
Note that if the command buffers its output, which is the usual case, then the segfault is all but certain to mean you won't be able to capture the buffered output. Many programs (especially those that use the stdio API in libc) won't buffer when writing to a tty. Which is why you can "see" the output before the program segfaults. But when writing to a pipe or file the output will be buffered and not flushed when the segfault occurs.
OK, a restart of services fixed the bridge. I'll look into setting up some monitoring and whether there are options of the bridge for recovering itself automatically
Hi! Which is the system and user completion folder that elvish load files from?
1 reply
well, they support elvish, I think that's great on its own
just to add some background, we don't even have working man pages generated from clap, so it's still a work in progress
fairy amazing they can generate completions
Hey guys. Thanks for teaching me a lot about golang and oss
I wish you all the best
Take care and thanks for all the help
It's been nearly a week since the last substantive comment so I'm going to ask people to weigh in on whether expansion of non-existent env vars should raise an exception just like builtin
get-env does. See elves/elvish#1537.
Also, I'm wondering how strongly people feel about adding "command" abbreviations. See elves/elvish#1472. I do not think the "small word" abbreviation mechanism I added is an adequate substitute for command abbreviations. So I've been working on a true command abbreviation implementation. Albeit using a regex rather than actually parsing the command line to identify the current "command".