Re: [O] conditionally color/format heading
Hi Andreas, Andreas Leha wrote: is it possible to dynamically change the color / typeface of headings? I would be interested to have all my headings with :noexport: tag to be darker, for instance. You could be inspired by http://article.gmane.org/gmane.emacs.orgmode/80850. If not, a fallback solution consists in highlighting differently that particular tag: --8---cut here---start-8--- (setq org-tag-faces '((noexport (:slant italic :foreground #8774AF :background #DED0EA --8---cut here---end---8--- Best regards, Seb -- Sebastien Vauban
Re: [O] verbatim and apostrophes
Hi Nick, Nick Dokos ndo...@gmail.com writes: However, the part about the BORDER regexp is correct I believe: in ~'a ref~, the ~ are the MARKERS; ' and f are the BORDER and a re is the BODY. Thank you, this is it. I had not understood that BORDERs were inside the MARKERs (although the help text is quite clear in that regard). Is there a nice way to customize `org-emphasis-regexp-components'? It does not seem to be exposed to `customize-variable', and copying and tweaking its default value in my configuration file feels ugly. Alan
Re: [O] conditionally color/format heading
Hi Sebastien, Sebastien Vauban sva-n...@mygooglest.com writes: Hi Andreas, Andreas Leha wrote: is it possible to dynamically change the color / typeface of headings? I would be interested to have all my headings with :noexport: tag to be darker, for instance. You could be inspired by http://article.gmane.org/gmane.emacs.orgmode/80850. Thanks a bunch. That has exactly the inspiration I was looking for. If not, a fallback solution consists in highlighting differently that particular tag: (setq org-tag-faces '((noexport (:slant italic :foreground #8774AF :background #DED0EA Thank for this as well, although I'll try to come up with sth from the post you linked to above. Regards, Andreas
Re: [O] org-dblock-write:count
Sebastien Vauban wrote: Adam Spiers wrote: I just had an awesome conversation with Sacha about more effective daily/weekly reviewing with org-mode :-) One of the things we talked about was quantifying the number of tasks (TODO keywords) in any given state, as a means of becoming more aware of your progress over time. I have had some success in the past using the measure what you want to manage maxim[1], and wanted to start applying this to my horribly massive TODO.org file. #+BEGIN:dynamic block #+BEGIN: count :keywords (\NEXT\ \DONE\) :searches (\@phone\ \@home\) | NEXT | 522 | | DONE | 69 | | @phone | 77 | | @home | 182 | #+END: To me, the best thing would be to see that count up-to-date with every custom agenda view. See http://lists.gnu.org/archive/html/emacs-orgmode/2013-09/msg01075.html for a patch I proposed in that direction. However, I had some comments of Bernt saying that some edge cases are not covered (when the block separator is empty). I still have to fix that, and come back with a fully working solution. An alternative could be `org-effectiveness', and having a hook to display the count (in the mode line) at each opening of an Org file... Best regards, Seb -- Sebastien Vauban
[O] beamer export org 8.0.2
Dear All, I have a problem with beamer export. (Org-mode version 8.0.2 (8.0.2-dist @ /home/user/.emacs.d/elpa/org-20140127/) when trying to export a small file I got the following message: org-beamer-export-to-pdf: Wrong number of arguments: (lambda (backend file optional subtreep visible-only body-only ext-plist) Call `org-export-as' with output to a specified file. BACKEND is the back-end used for transcoding, as a symbol. FILE is the name of the output file, as a string. Optional arguments SUBTREEP, VISIBLE-ONLY, BODY-ONLY and EXT-PLIST are similar to those used in `org-export-as', which see. Depending on `org-export-copy-to-kill-ring', add file contents to kill ring. Return output file's name. (if (file-writable-p file) nil (error Output file not writable)) (let ((out (org-export-as backend subtreep visible-only body-only ext-plist))) (let ((temp-buffer (generate-new-buffer *temp*))) (save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn (insert out) (let ((coding-system-for-write org-export-coding-system)) (write-file file))) (and (buffer-name temp-buffer) (kill-buffer temp-buffer) (if (and (org-export--copy-to-kill-ring-p) (org-string-nw-p out)) (progn (org-kill-new out file), 8 Any help is welcome. Thanks
Re: [O] ox-md generates .html links to other org files.
Hello, Mark Janssen mpc.jans...@gmail.com writes: When exporting org files to .md files using the ox-md.el backend, links like [[file:other-file.org]] are translated to other-file.html. I would expect this to be other-file.md instead. As it stands exporting multiple files to markdown doesn't allow easy interlinking between them. This can be worked around by defin-ing: +BEGIN_SRC :html-extension md +END_SRC in the exporting project. But I think this should be fixed in the =org-md-link= function. This should be fixed. Thank you. Regards, -- Nicolas Goaziou
[O] Space around tables in LaTeX export?
I'm trying to export a document to PDF via LaTeX, but my tables appear with no preceding or trailing whitespace, even if I put several blank lines before and after. For example: ---cut---cut---cut---cut---cut---cut---cut---cut---cut---cut---cut---cut--- blah blah blahbeddy-blah and still more blah |+--+| || Some | Stuff | |+--+| | First row | yes | n/a| | 2nd row| no | maybe | |+--+| blah blah blahbeddy-blah and still more blah ---cut---cut---cut---cut---cut---cut---cut---cut---cut---cut---cut---cut--- In the resulting PDF, there's no space between the table and the surrounding text. I couldn't find anything here [[http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-13]] on how to fix this. Thanks! -pd -- Peter Davis The Tech Curmudgeon www.techcurmudgeon.com
Re: [O] Space around tables in LaTeX export?
Peter Davis wrote:
In the resulting PDF, there's no space between the table and the surrounding
text.
how about
#+BEGIN_LATEX
\vspace{/somelength}/
#+END_LATEX
//
---
This email is free from viruses and malware because avast! Antivirus protection
is active.
http://www.avast.com
Re: [O] Space around tables in LaTeX export?
On Fri, Feb 14, 2014 at 12:18:20PM -0500, Charles Millar wrote:
Peter Davis wrote:
In the resulting PDF, there's no space between the table and the surrounding
text.
how about
#+BEGIN_LATEX
\vspace{/somelength}/
#+END_LATEX
Ok, but I was hoping for a more org-mode-y solution.
Thanks!
-pd
--
Peter Davis
The Tech Curmudgeon
www.techcurmudgeon.com
Re: [O] Space around tables in LaTeX export?
Peter Davis p...@pfdstudio.com writes:
On Fri, Feb 14, 2014 at 12:18:20PM -0500, Charles Millar wrote:
Peter Davis wrote:
In the resulting PDF, there's no space between the table and the
surrounding text.
how about
#+BEGIN_LATEX
\vspace{/somelength}/
#+END_LATEX
It will become a float if you give it a caption. That's probably what
you want. You can still force it to be at a particular location.
–Rasmus
--
Hvor meget poesi tror De kommer ud af et glas isvand?
Re: [O] Space around tables in LaTeX export?
Peter Davis wrote:
On Fri, Feb 14, 2014 at 12:18:20PM -0500, Charles Millar wrote:
Peter Davis wrote:
In the resulting PDF, there's no space between the table and the surrounding
text.
how about
#+BEGIN_LATEX
\vspace{/somelength}/
#+END_LATEX
Ok, but I was hoping for a more org-mode-y solution.
Thanks!
-pd
Correction
somehow a couple of / crept in
---
This email is free from viruses and malware because avast! Antivirus protection
is active.
http://www.avast.com
Re: [O] Space around tables in LaTeX export?
On Fri, Feb 14, 2014 at 06:27:28PM +0100, Rasmus wrote: It will become a float if you give it a caption. That's probably what you want. You can still force it to be at a particular location. Ah! Yes, that works, even with a blank caption. Thank you! -pd -- Peter Davis The Tech Curmudgeon www.techcurmudgeon.com
[O] Graph not hierarchical?
Is there any way to have org mode simulate a graph structure rather than always a (folding) hierarchy? You could say a hierarchy is a tree graph, and you could link or give a jump from one entry to another -- even in another org file. It seems plausible to call an entry a node, and a node could have listed in its properties edges leading to other nodes. Has anyone else thought of this? Without knowing anything about how org mode is really coded under the hood, I'm guessing (from reading the documentation) it is simply built on the emacs folding code, i.e., there is no real underlying hierarchy algorithm(s) that you could hack into in order to make org mode more database-like (tree, graph, or otherwise). Some of these thoughts came from the simple examples given in Land of Lisp where a simple nodes and edges representation was given with a-lists: (defparameter *nodes* '(living-room garden attic)) (defparameter *edges* '((living-room (garden west door) (attic upstairs ladder)) (garden (living-room east door)) (attic (living-room downstairs ladder The nodes are living-room, attic, and garden. And the edges are an a-list keyed on the nodes, e.g., living-room has two edges, one connected to the attic (upstairs by way of a ladder), the other to the garden (to the west by way of a door). I guess this is beginning to sound like a weak graph database hack, but as I envisioned it, each node -- an org mode entry -- could be leveraging org mode's big strengths: literate programming and loose, do-it-yourself text data storage. LB North Shore MN
Re: [O] tricky odt export needs
Jambunathan K kjambunat...@gmail.com writes: In the pdf version of Emacs info manuals one typically sees all three of a Section number AND a Description AND a Page number, something like: See Section 3.1 [Tropical Storms], page 24. In Org context, I am wondering whether there is such a need. I have added support for generating page nos. See attachments for sample test file. --8---cut here---start-8--- #+OPTIONS: ':nil *:t -:nil ::t :t H:3 \n:nil ^:t arch:headline #+OPTIONS: author:t c:nil creator:comment d:(not LOGBOOK) date:t #+OPTIONS: e:t email:nil f:t inline:t num:3 p:nil pri:nil prop:nil #+OPTIONS: stat:t tags:t tasks:t tex:t timestamp:t toc:t todo:t |:t #+TITLE: headline #+DATE: 2014-02-12 Wed #+AUTHOR: Jambunathan K #+EMAIL: kjambunat...@gmail.com #+DESCRIPTION: #+KEYWORDS: #+LANGUAGE: en #+SELECT_TAGS: export #+EXCLUDE_TAGS: noexport #+CREATOR: Emacs 24.3.50.20 (Org mode 8.2.5h) #+TOC: headlines * Headline 1 Some text. See [[Headline 2]]. #+PAGEBREAK: * Headline 2 Some more text. --8---cut here---end---8--- Page nos are disabled by default. To enable pagenos, you need to M-x customize-variable org-odt-caption-and-xref-settings and choose a setting as below. [X] Key: :TARGET: Plist: [X] Key: :xref-format Choice: Value Menu TexInfo style INS The TexInfo style is provided more for trial run. A variety of different format strings can be chosen. You can pull my changes from the following ELPA archive: http://repo.or.cz/w/org-mode/org-kjn.git/blob_plain/master:/ See instructions at http://cauvery.nfshost.com/wiki.pl/ODT_Exporter pagenos-after-upate.odt Description: application/vnd.oasis.opendocument.text pagenos.odt Description: application/vnd.oasis.opendocument.text #+OPTIONS: ':nil *:t -:nil ::t :t H:3 \n:nil ^:t arch:headline #+OPTIONS: author:t c:nil creator:comment d:(not LOGBOOK) date:t #+OPTIONS: e:t email:nil f:t inline:t num:3 p:nil pri:nil prop:nil #+OPTIONS: stat:t tags:t tasks:t tex:t timestamp:t toc:t todo:t |:t #+TITLE: headline #+DATE: 2014-02-12 Wed #+AUTHOR: Jambunathan K #+EMAIL: kjambunat...@gmail.com #+DESCRIPTION: #+KEYWORDS: #+LANGUAGE: en #+SELECT_TAGS: export #+EXCLUDE_TAGS: noexport #+CREATOR: Emacs 24.3.50.20 (Org mode 8.2.5h) #+TOC: headlines * Headline 1 Some text. See [[Headline 2]]. #+PAGEBREAK: * Headline 2 Some more text.
