mu VS yq

I like mu4e (https://github.com/djcb/mu) for reading emails. You'll need to run mu init [email protected] (append as many --my-address entries as email addresses you receive mail at) in your Maildir and mu4e should start reading it.

For all details, see https://github.com/djcb/mu/blob/release/1.10/NEWS.org (and I'd recommend

And djcb already fixed it: https://github.com/djcb/mu/issues/2420 !

I've tried to follow the release notes here, but find it hard to follow... for instance, the releases jump from 1.4.15 to 1.6.0? (So where is 1.5.5?) Is there a compilation of all these changes from e.g. ~ to -- and other general refactoring?

> Surely there is a space for minimalist office suites and email clients,

FWIW, my email life improved massively when I left the likes of Thunderbird and KMail behind for the simplicity of mu/mu4e [1]. I hear similarly stellar things about Notmuch [2]. I'm never going back to an email client that even thinks about itself in relation to "office suites".

[1] https://www.djcbsoftware.nl/code/mu/

[2] https://notmuchmail.org/

and maildir-utils to index for search, https://www.djcbsoftware.nl/code/mu/

What I often use to just get the full key paths is yq (https://github.com/mikefarah/yq), piping into grep when necessary

  yq -o=props 

For more information about this command visit https://github.com/mikefarah/yq

I've been trying to install and config a plugin (papis.nvim) for a couple of days and am having issues with a function that uses io.popen to run yq to convert yaml files to json. I know my install of yq is fine- I can run yq -oj info.yaml from the command line with no issue and it produces the correct json output. I know the function can find the yq executable, but it returns nil. I've saved the error from the yq golang code: panic: runtime error: invalid memory address or nil pointer dereference

- yq has no if-then-else https://github.com/mikefarah/yq/issues/95 which is a poor design (or omission) in my opinion

After which, I use openapi-generator to make a yaml output.

https://gist.github.com/freshteapot/3637e8d2b5ecdf01b7d25246...

- yq version 3.4.1 (Worth noting, the example uses an out of date yq, so a few modifictaions might be needed)

https://github.com/mikefarah/yq

For those pining for a similar yaml query tool for working through acres of config: https://github.com/mikefarah/yq

jq is awesome and thanks to the new team for their recent efforts and energy, it massively appreciated.

For anyone looking for such a script, there's some CLIs that make it easy. One is `yq -o props` [1], another way is to use `yq -j` or `yj` [2] to convert to JSON and pipe it to `gron` [3].

[1] https://github.com/mikefarah/yq

[2] https://github.com/sclevine/yj

[3] https://github.com/tomnomnom/gron