Home GitHub Patreon
Discussions RSS Twitter

Use the input method from original org buffer in log note buffer

On switching various TODO states I've set up org mode to pop a buffer for attaching a quick note or explanation. You can do this also for refiling, clocking in or out, rescheduling and so on.

I don't use these logs very often in a review or retrospective but it helped me a bunch of times to figure out the circumstances of my past actions (e.g. rescheduling, postponing work etc.) so I find it worth to spend 30 seconds jotting down a simple note as opposed to then trying to figure out everything from scratch for hours.

Especially useful for when you are not meeting client's deadlines. Papertrail is good!

Also being a daily journalist and somewhat obsessive about tracking my life my settings here are pretty aggressive.

One thing that buggs me is, being not a native English speaker, is that when org-mode pops the note buffer its input method resets to English. Given the fact that the past and current org maintainers also don't speak English as a first language kind of led me to expect there to be some setting to inherit the input method of the original buffer1. Sadly, I couldn't find it, so I decided to "roll my own".

Now here comes the part that blew my mind… I've realized I wrote the whole code in under 2 minutes… where simply trying to read the manual and search the code would easily take more time2. This is the nice feature of being an Emacs power-user. I wrote the code on the first try, registered it in a hook which name I've guessed and it all worked flawlessly. Nice!

(defun my-org-inherit-input-method ()
  "Set the input method of this buffer to that of original's buffer."
  (let* ((note-buffer (marker-buffer org-log-note-marker))
         (im (with-current-buffer note-buffer
    (set-input-method im)))

(add-hook 'org-log-buffer-setup-hook 'my-org-inherit-input-method)

Of course, I've spent thousands of hours learning Elisp, so I'm not sure where or when the time/productivity curves actually crossed.



And really, 99% of the time, when you say "I'm going to write an org-extension", it already is in core.


This is not the greatest engineering and you should almost always prefer a well-tested lib over your own… on the other hand, being a pragmatic professional, I value my time over code purity

Published at: 2019-01-23 08:46 Last updated at: 2023-02-08 15:59
Found a typo? Edit on GitHub!