Table.el is a package that lets you utilize tables in plain text files.
It also works correctly within org-mode files.
What I found most interesting was the ability to split individual cells vertically and horizontally.
Table.el is a package that lets you utilize tables in plain text files.
It also works correctly within org-mode files.
What I found most interesting was the ability to split individual cells vertically and horizontally.
refcard-org-babel “contains the reference documentation that describes how to perform code execution within Org mode documents using Org Babel 8”.
Look forward to referencing this when I read about other’s personal org workflows, and, document down my own.
This post reveals a nice function comment-indent-new-line
which gives you the
right kind of indentation for block comments. That got me wondering if my
enter
key-binding should do different things depending upon whether or not the
cursor is inside of a comment block or not. Specifically, if it is, then call
the aforementioned function, else call the normal binding. This seems that it
might be an improvement
This post explains how to check if the cursor is inside of a comment block:
(nth 4 (syntax-ppss))
It is not nil when the point (cursor) is inside of a comment block.
Great to know.
I decided not to make this change yet, but, I wanted to capture how, here.
This announcement is pretty exciting because it reveals a new-to-me take on literate programming. The style is to store a single file as a source, and render disparate parts of that file in different buffers in a mode correct for the content.
For example you may have an Emacs Lisp file serve as the source and two separate buffers, one Emacs Lisp and one Organization (Mode), to work on the content, with all of the mode-specific assistance.
Is it a new idea? It is new to me and I am curious to find out about other approaches people have taken to realize this style.
When I first learned how to set up Emacs, I really liked local-set-key
because you didn’t have to know about the keymap for the mode you just had to make the call in that mode’s hook. That is simple and makes total sense. That has worked well for me for years until two things happened:
The former is part of the natural expansion of use and its refinement. The latter is similar, but specific to running Emacs on Windows.
The last time that I ran Emacs on Windows I did not use the Super key. Then I went off into the wilderness and use it a lot only to return and find that Windows owns lot of my keybindings. Not only were they owned, but they would not let go of them no matter how I tried! Because if this major inconvenience, I’ve got no reasonable choice other than refactoring some of my perfect bindings into something, ahem, better.
This refactoring would have been pretty easy if I’d jus done normal keybindings against keymaps, but I didn’t, I used local-set-key
. So this becomes a good learning opportunity about the key-map names and additionally how, at least for myself, this is generally a bad approach because makes re-factoring harder.
The good thing is that at least up front there is a good time savings, I suppose.
Pose the question “Is there ever a time when Emacs users should be running out-of-date bytecode instead of the up-to-date bytecode or lisp?” to yourself.
All Emacs users should probably run auto-compile.
Eshell can be used for su
and will quite happily remember your password according to this answer.
A defined abbrev is a word which expands, if you insert it, into some different text.
They are really simple and really helpful if you like this kind of thing. If you grew up hacking on Java, then you surely already use this in IntelliJ IDEA!
Here is a nice post on how to choose and define abbrevs based upon actual usage.