Re: [O] [feature] prepend comment char before org-babel-ref

Sorry, I miss typed my header argument `:dir "data/code/src-coderef.rb"`. It should be `:tangle`. [stardiviner] GPG key ID: 47C32433 IRC(freeenode): stardiviner Twitter: @numbchild Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 Blog:

Re: [O] How to dynamically change org-clock-mode-line-total?

Marcin Borkowski writes: > Hi all, > > I want to be able to dynamically switch between various settings of > org-clock-mode-line-total. To this end, I wrote the following code. > > (setq org-clock-mode-line-total-settings > '((current . "time spent in this chunk on the

Re: [O] [feature] prepend comment char before org-babel-ref

Because it is not good for tangling. For example, tangle the bellowing src block, the tangled source code file will has `(ref:hello)` too. ``` #+begin_src emacs-lisp :tangle "data/code/src-coderef.el" (message "hello, world") (ref:hello) #+end_src ``` The tangled source code file looks like this:

[O] How to dynamically change org-clock-mode-line-total?

Hi all, I want to be able to dynamically switch between various settings of org-clock-mode-line-total. To this end, I wrote the following code. --8<---cut here---start->8--- (setq org-clock-mode-line-total-settings '((current . "time spent in this chunk

Re: [O] [RFC] Moving "manual.org" into core

Hello, Yasushi SHOJI writes: > Also, the code converts all lower case "#+title", "+begin_src" and > other "#+"s to > the UPCASE. Is this intended? I thought we are moving away from CAP > to lower? This was changed a few days ago. See commit

Re: [O] executing org-table TBLFM form changes (resets) language settings

Am 25.01.2018 um 20:27 schrieb Nick Dokos: Rainer Stengele writes: All, My current-language-environment is "German". Having an Org table with a TBLFM attached: | IM Startzeit | IM Endezeit | Stunden | delta(x,16) | Anm. |

Re: [O] [RFC] Moving "manual.org" into core

Hi Nicolas, On Wed, Jan 24, 2018 at 8:28 PM, Nicolas Goaziou wrote: > Org Lint is not a formatter. It detects common mistakes or hypothetical > mistakes in an Org document, e.g., invalid links. In particular, it > doesn't detect stylistic issues like those discussed