New answers tagged

0

I encountered the same problem as you. I couldn't fix it, but came up with this workaround. Put the ledger code in d:/Ledger/RLbook.dat into a named org source block and save the file as RLbook.org: This entire block here is stored in a file called =RLbook.org=, including this sentence! #+name: include #+begin_src ledger :noweb yes ;; put your ledger ...


0

Ok, this more or less works when put together in an org file: #+BEGIN_SRC emacs-lisp :results none (require 'cl) (defun org-redisplay-ansi-source-blocks () "Refresh the display of ANSI text source blocks." (interactive) (org-element-map (org-element-parse-buffer) 'src-block (lambda (src) (when (equalp "ansi" (org-element-property :language ...


1

What I want to achieve is to export to ODT document with a style which differs from the one use in org mode document. I use a dark theme to work on org mode and I want a light theme in the produced document. ox-odt-9.2.4.251.tar has support for this feature. Please upgrade before tying out the solution below For a step-by-step instructions on how you ...


2

I can reccomend org-tanglesync, which has a much simpler method of syncing than org-babel-detangle Essentially if a block is tangled to an external file, then every time that block is edited, the external file is also checked, and if a diff is detected, the user is prompted to either reject or pull the external changes into the org src block. This also has ...


2

There is also org-tanglesync, which has a much simpler method of syncing than org-babel-detangle Essentially if a block is tangled to an external file, then every time that block is edited the external file is checked also, and if a diff is detected, the user is prompted to either reject or pull the external changes into the org src block. This also has ...


1

Slightly late to the party, but I had the same wish to sync tangled blocks with their external files. For this I can recommend org-tanglesync This package looks for a :tangle <filename> property in the header of an org file and compares the block content to it. A diff is performed in the background, and then the user is prompted to pull or reject the ...


1

Here is a potential solution: (defun org-mode-<>-syntax-fix (start end) (when (eq major-mode 'org-mode) (save-excursion (goto-char start) (while (re-search-forward "<\\|>" end t) (when (get-text-property (point) 'src-block) ;; This is a < or > in an org-src block (put-text-property (point) (1- (point)) ...


2

The reason for the mismatch is the code contains an angled bracket (">") which is treated as a matching paren. I don't know the solution for how to specify that orgmode emacs-elisp should ignore angled brackets when matching parens (but I would like to know a solution). Note: I posted this as an "answer" because I don't have enough reputation points to ...


0

(If you want further help, please raise a issue on my github repo) I installed the alternative odt exporter with the suggested procedure but I now have a new problem: the exportation is not done and an error message is issued: "org-odt-template: OpenDocument export failed with error: ‘Styles file is invalid:". Don't surround your styles file within ...


Top 50 recent answers are included