Try Out Org2Blog v1.1.0 Using This Package

Right now you can’t try out an Org2Blog v1.1.0 package from MELPA because it isn’t yet building using Org2Blog’s new recipe. Eventually the pull request will get merged. Once it does I will push the changes. However, you can still try out v1.1.0 using a package.

If you’ve been waiting to try Org2Blog v1.1.0 using a package then you can download it here just download the tar file. After downloading it you can install it from Emacs by typing M-x package-install-file and then choosing the file org2blog-master.tar you just downloaded.

The package manager should install the required packages but if it doesn’t it will warn you and you can manually install them. Depending on how you configured package-archives and package-archive-priorities everything should go just fine. Let me know if it doesn’t.

Checkout the README.org now included within the package.

Happy blogging

Interested in testing Org2Blog v1.1.0?

Org2Blog v1.1.0 has some improvements to it. The README has a lot more in it. There is a user interface (Hydra) now that makes all of the features very visible and easy to use. Some code was refactored and some features were implemented and completed. There are a lot more status and other messages to help make sense of what the application is doing. There is a Test Plan and notes about Contributing.

Tonight I finished coding and testing Org2Blog 1.1.0 as far as I can take it. You know the point where you lose the ability to see the artifacts anymore? That is where I am. Everything seems to work, I’ve been using it and “it works on my computer” lol. It is ready for folks that feel like trying out the new version. Folks who are patient and curious and pretty OK with bugs ranging from the dumb to the painful along with suggesting improvements for better documentation and even new functionality might enjoy this sort of thing.

The source code is here. If you want to try it out from a package here is the latest build.

Go To The Logical Begin And End Of A Buffer’s Content

The only time that I call beginning-of-buffer is when I want to visit the file header, which isn’t very often. The rest of the time I only want to go up to where the code begins, or at least close to it. That is the logical beginning of the buffer. Another example is going to the beginning of a magit-status invoked buffer: I’ve never use the first first 3 lines of it. The logical start of it is the Untracked file listing. The Beginend package moves your cursor to the the logical beginning of the buffer content. It also implements a logical end-of-buffer. It might not sound like much, but it bumps up your user experience by more than a few notches: it makes the modes do what many of us are thinking and that is the ultimate feel good experience. Here is an example:

Demonstration Follows

Blogging With Emacs? From Org2Blog? to WordPress

Blogging from Org2Blog to WordPress just works and that is just about all there is to it. All of the markup works. Even MathJax works:

Brad told me that this is the most beautiful equation in mathematics:

Euler’s Formula: \(e^{ \pm i\theta } = \cos \theta \pm i\sin \theta\)

Thank you Brad.

https://raw.githubusercontent.com/grettke/wisdomandwonder/master/post/2019-02-01-01.org is this post itself ??.

Start using it https://github.com/org2blog/org2blog!

HELP: Yet Another Literate Emacs Configuration!

HELP is the culmination of everything that I’ve learned about literate programming (LP) in Org-Mode—written with the intent to share it with others in total and complete respect and consideration of you and the value of your time. No platitude here: time is precious.

With that in mind here is a breakdown of the sections you might be interested in (and should ignore):

Continue reading “HELP: Yet Another Literate Emacs Configuration!”

bash: update_terminal_cwd: command not found resolution

When you run Bash under shell in Emacs on macOS then update_terminal_cwd is never defined and after every command you get the error message bash: update_terminal_cwd: command not found making the shell unusable.

The simplest solution is to define update_terminal_cwd when it isn’t defined.

Here is the code:

if [ -z “$(type -t update_terminal_cwd)” ] || [ “$(type -t update_terminal_cwd)” != “function” ]; then
update_terminal_cwd() {
true
}
fi