Welcome to Costco, I love you!
512 karma · joined August 26, 2016
I enjoy it.
Maybe it’s decades of doing it, and I don’t consider myself especially dexterous, but I never have any problem with it.
:( seems like that would be a very basic feature.
https://github.com/nushell/nushell/issues/1329
Have you tried adjusting the option: Appearance › Show inline title ?
* All of the endpoints are singular, but then /summaries is plural for some reason
* You can enumerate the congresses, but non of the congress representations have a value which represents the numeric ID that should be used on other requests. Unless you request the congress data using that number, and then it does include it.
Oh well, hopefully it improves and becomes more consistent over time.
Authentication seems to be done with a query string ?api_key=KEY instead of some kind of standard header.
Also, there is a query string "format" for changing the output, ?format=json. Instead of using the Accept header :/
Feel like it is every single day. It’s not quite that often, but it is very often. And I use it on multiple devices, so it really feels like every time I launch it.
https://www.merriam-webster.com/dictionary/embiggen
A noble spirit embiggens the smallest man.
I failed.
yadm will keep its repo in ~/.local/share/yadm/repo.git.
Once cloned, you do not need to be in any specific directory to run yadm.
I'm a huge fan of Git, and the Git mental model just makes sense to me. I wanted to manage my dotfiles in the same way. At the time I had tried several other solutions, mostly similar tools like homeschick and vcsh.
I wanted a solution that was very portable, which both of those existing tools were. However, homeschick became a bit clunky to use because each time I wanted to do most operations I had to first "cd" into my "castle". In addition, that tool used symlinks, which doesn't work out well to manage a file that may get overwritten by a tool.
vcsh was the other main tool I tried. This tool adopts the bare repo technique, allowing files to be used instead of symlinks. The major drawback it had was that it was designed to work with multiple repos, and forces you to specify the repo with every command. Some simple aliasing helped mitigate that though. But by that time I also started writing some custom code to encrypt private data and was struggling to maintain different branches for different systems which had slight tweaks to configurations. It just became all fragmented and difficult to manage.
That is what lead me to create my own tool. The important features I wanted: portability, seamless interaction with Git, alternate files for different hosts, encryption for private data. I shared it as open source back in 2015 and it has grown in popularity some. It's been improved a lot over time including contributions from others. I'm glad so many others have found it useful.
1. Create a Smart Selection with the regular expression "SC\d+"
2. Add an action to "Open URL...", with the URL "https://github.com/koalaman/shellcheck/wiki/\0" (\0 will be replaced with the matched regex)
3. Now holding down the command key will change any ShellCheck errors to be active http links.
It took some redesign, but I was finally able to demonstrate how much could be done locally before pushes. Some just need their eyes opened up.
I specifically have a design goal of very little external dependency. It only requires Git and Bash be present, so it is quite portable. Many people even use it on some network equipment. You can simply download the script if it isn’t packaged somewhere.
It can easily handle directories of files, but also submodules. Many people add vim plugin Git repos directly as submodules.
If you are familiar with Git, you’ll find yadm extremely easy to use. When you need them, more features are there to solve specific problems, like bootstrapping operations, encrypting private data, templating, or system dependent alternate files.
On a new system you can quickly bootstrap your existing dotfiles repo using https://bootstrap.yadm.io, without yadm installed yet. This is mostly useful if you’ve included yadm directly in you dotfiles (directly, or as a submodule, or as some installation during bootstrap).
You rebase BEFORE you merge into the mainline branch.