Tag: Emacs
Edit a source block with its name shown in org
My preference is to rely upon heading property inheritance to define source block
names. That way, you can just do your work knowing “where” you are working and
keep it simple by not having to name everything. That was just fine until I
wrote a document where I needed to name each source block.
It gets easy to forget the source block’s name. Not the end of the world, but very nice to know.
(defun gcr/org-edit-src-code-plus-name ()
"Edit the well-described source code block.
Attribution: URL `https://lists.gnu.org/archive/html/emacs-orgmode/2014-09/msg00778.html'"
(interactive)
(let* ((eop (org-element-at-point))
(name (or (org-element-property :name (org-element-context eop))
"ॐ"))
(lang (org-element-property :language eop))
(buff-name (concat "*Org Src " name "[" lang "]*")))
(org-edit-src-code nil nil buff-name)))
Announce: PicoLisp in Hardware (PilMCU)
PilMCU is an implementation of 64-bit PicoLisp directly in hardware. A
truly minimalistic system. PicoLisp is both the machine language and the
operating system:
Via help-gnu-emacs.
zk-phi releases two perhaps necessary packages for Emacs
You may not be totally sure why, but you will immediately feel like you ought to install the following two packages for Emacs:
[indent-guide] show vertical lines to guide indentation
[highlight-stages] highlight staged (quasi-quoted) expressions
Problems installing (M)ELPA packages
In Problems installing (M)ELPA packages Sebastien wrote:
While using `package.el’ fulfills a long-awaited dream for easily adding and upgrading Emacs libraries, I now feel upgrading packages is much more complex than what I anticipated.
At least two of the packages I use daily (Org and Helm) require to be installed from inside a fresh Emacs session (emacs -Q), where nothing has been loaded.
I had wondered but never found out why one must follow this approach when installing org from scratch. Good to know!
elpakit
Testing Emacs Packages: surprisingly non-awful
Testing Emacs Packages: surprisingly non-awful is a nice example of one approach to testing Emacs Lisp.
Force unified coding style from all your contributors
EditorConfig helps developers define and maintain consistent coding styles between different editors and IDEs. The EditorConfig project consists of a file format for defining coding styles and a collection of text editor plugins that enable editors to read the file format and adhere to defined styles. EditorConfig files are easily readable and they work nicely with version control systems.
Via rapporter.
eval-in-repl: Consistent ESS-like eval interface for various REPLs
This package does what ESS does for R for various REPLs, including ielm.
Emacs Speaks Statistics (ESS) package has a nice function called ess-eval-region-or-line-and-step, which is assigned to C-RET. This function sends a line or a selected region to the corresponding shell (R, Julia, Stata, etc) visibly. It also start up a shell if there is none.
This package implements similar work flow for various read-eval-print-loops (REPLs)
Via ess-help.
A progress indicator for code blocks in org-mode
A progress indicator for code blocks in org-mode courtesy
of John Kitchin:
;; give us some hint we are running (defadvice org-babel-execute-src-block (around progress nil activate) (set-face-attribute 'org-block-background nil :background "LightSteelBlue") (message "Running your code block") ad-do-it (set-face-attribute 'org-block-background nil :background "gray") (message "Done with code block"))