More diving into Org Mode and Emacs. I have a stuff-to-do.org file, that serves as an inbox for most long term tasks that I want to tackle. Stuff that needs doing, books that I want to buy, books that I want to read, courses that I want to learn, movies or tv shows that I want to watch, stuff on the web that I want to catchup on, etc. etc. etc. ...
(Update, 2024-03-15: I now use lego. will update this post later.) After struggling to renew my certs for the third time in a row, hopefully these pointers should keep me on track for the next time. Namecheap does not yet support automatic wildcard renewal for the Letsencrypt/Certbot combo. Check next year. Have your Namecheap control panel open and ready. Switch to root or run the command below with sudo Command to renew: certbot certonly --manual --manual-public-ip-logging-ok --preferred-challenges dns-01 -d *.domain.com -d domain.com certbot will then, print a couple of lines that you need to add as a TXT record in the Namecheap DNS control panel. When you do that, make sure you set the TTL of the record, to a minute, so that you can redo stuff quicker, if you mess up. certbot might ask you to do multiple records. Read the instructions carefully. When you check to see if the TXT record is set, search for the whole domain name. For e.g. _acme-challenge.domain.blah instead of just domain.blah If you’ve done all of the above, hopefully things should go smoothly and the certificate should renew. Restart Nginx and you’re done. If you have multiple machines, figure out a way to securely transfer the certs there too. P.S. Subscribe to my mailing list! Forward these posts and letters to your friends and get them to subscribe! P.P.S. Feed my insatiable reading habit.
Org mode is slowly spreading its tentacles increasingly becoming something, I cannot live without, to manage my day. And I’m getting pretty consistent with it too! Like you see above, I use dates as my headlines, below which I list the various tasks for the day.1 And that’s where I run into my current itch to scratch. ...
Originally published 2021/10/27. Updated to include the .xssessionsrc point I run pretty often into this issue, so this is a checklist for me. Issue being, that I cannot use Compose key sequences to type out the characters I need. Case in point being, the apostrophe ’ and the quote marks “” , ‘’ that I use, all the live long day. Make sure that emacs is running as a service. It runs in your user, so check status with systemctl --user status emacs.service Do the normal computer user thing. Restart the service.systemctl --user restart emacs.service.1 Make sure the system is UTF-8 everywhere. (en_IN.UTF-8 does not work for me. Make sure it’s en_US.UTF-8) One place that Emacs looks is the .xsessionrc file in the home folder. These are the contents of mine. My Emacs refuses to let the compose key sequences work, unless it’s present LC_NUMERIC=en_US.UTF-8 LC_MONETARY=en_US.UTF-8 LC_PAPER=en_US.UTF-8 LC_NAME=en_US.UTF-8 LC_ADDRESS=en_US.UTF-8 LC_TELEPHONE=en_US.UTF-8 LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=en_US.UTF-8 LC_TIME=en_US.UTF-8 PAPERSIZE=a4 LANGUAGE=en_US LANG=en_US.UTF-8 if [ $DISPLAY != ":0" ] then export XAUTHORITY=${HOME}/.Xauthority fi This should do the trick 99% of the time. ...
While building my work product on the fancy-schmancy M1 work Mac, I kept running into clang errors, when I did a pip install Turns out, PyCLD3 would not build. So I did it manually. This tip on Github did the trick We need brew installed. And then we run the following commands in a terminal … brew install protobuf #install protobuf # set various compiler flags export GRPC_PYTHON_BUILD_SYSTEM_OPENSSL=1 export GRPC_PYTHON_BUILD_SYSTEM_ZLIB=1 export CFLAGS='-I /opt/homebrew/opt/protobuf/include' export LDFLAGS=-L/opt/homebrew/opt/protobuf/lib # install pycld3 python3 -m pip install pycld3 And we’re set! ...
Update: 28/12/2021 The solution? Move off the 64 bit Raspberry Pi OS and install Ubuntu. Everything below is now just for history and context :) Every time I update my Pi, whether it be an kernel update or due to something goofy I do, it refuses to be accessible via ssh after it boots back up. And everytime I bring it back to my desk, it just works. And when I put it back into its niche, by the door, it continues to work. But inevitably, sooner or later, comes a reboot, and we’re back to being inaccessible. No ssh, no plex, no network. ...