Programming Language – Page 21

How to debug expanded elisp macros

This video reveals just how amazingly it easy it is to expand and debug macros in elisp using the macrostep package.
Via irreal.

Org-Mode Details To Accompany Questions

The details that are likely to help questions to be answered on the org mailing list.

(print emacs-version)

(print org-version)

(print (pp-to-string org-babel-default-header-args))

(print (pp-to-string org-babel-default-header-args:R))

Eg:

"24.3.1"

"8.2.10"

"((:eval . \"always\")
 (:padline . \"yes\")
 (:noweb . \"no-export\")
 (:exports . \"both\")
 (:results . \"output replace\")
 (:comments . \"noweb\")
 (:session . \"none\")
 (:cache . \"no\")
 (:hlines . \"no\")
 (:tangle . \"no\"))
"

"((:session . \"*R*\"))
"

Set image width in org-mode

Make org and export use the same image width via this post:

#+attr_latex: :width 4in :placement [H]
#+attr_org: :width 400
./images/batch-multiple.png

A must-see of advanced babel usage in org with R

This post is a must-see of advanced babel usage in org with R

Perl regex builder in emacs

Perl regex builder in emacs
- Read the wiki and there are 2 options
- Best is this
- Roughly confirmed that is the best and newest
- Set up an el-get for it tonight
- Played around for while can’t get el-get to load it
- I can’t even load it myself
  - Probably my fault
- Posted ticket on github page here

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)))

R Markdown

R Markdown is an authoring format that enables easy creation of dynamic documents, presentations, and reports from R. It combines the core syntax of markdown (an easy-to-write plain text format) with embedded R code chunks that are run so their output can be included in the final document. R Markdown documents are fully reproducible (they can be automatically regenerated whenever underlying R code or data changes).

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

Let’s you build repositories and archives of repositories.

Via reddit.