Eike | 20 Sep 14:42 2014

simple expense tracking with org

Hello there,

I thought to share a little elisp thingy that I wrote to track my
expenses with org. I use the org's capture mechanism to add expense
items to some files and the following code only searches through all
these files and creates summaries of all found expenses. It is possible
to search by date, tags etc.

You can have a look here: https://github.com/eikek/org-expenses


gpg: AD7AC35E
finger print: 137F BB0B 1639 D25F DC5D  E59C B412 C5F5 AD7A C35E

Aaron Ecay | 19 Sep 21:17 2014

[RFC] [PATCH] [babel] read description lists as lists of lists

Hello all,

The attached patch makes babel read description lists as lists of the
following format: (("term" "description") ...).  The present default is
to simply read in the text of each list item, yielding:
("term :: description" ...).

Of course, it’s possible to interconvert between the two formats, but I
think the greater structure of this proposal makes things easier for
babel authors.  (Another way of thinking of the proposal is that it
treats description lists like two-column tables.)

What do people think?



Aaron Ecay
Aaron Ecay | 19 Sep 21:12 2014

[RFC] [PATCH] Warn about unexpanded macros on export

Hello all,

Currently, if a macro is not defined, it will silently produce an empty
string while exporting.  This situation could arise for example if a
macro name is acidentally mistyped.  I think it’s desirable to warn the
user in this case.  The attached patch introduces a function to do so,
and shows how it would be integrated in the latex backend.  This raises
several questions:

1. Should the warning be a “message” (allows the export process to
   continue) or a “user-error” (stops the export process)?  Or, should
   this be configurable?

2. Since this is a feature that many backends will want to use, should
   we introduce a new “abstract” backend from which other backends can
   inherit, which incorporates this feature, and others like it in the
   future?  The idea would be similar to prog-mode in emacs, the major
   mode from which programming-language modes can derive.  The
   alternative is adding the (macro . org-export-macro-warn) entry
   manually to all the relevant backends, and relying on future backend
   authors to do the same.

3. Should this even be implemented as part of the backend’s
   translate-alist, or at a lower level?



Aaron Ecay
(Continue reading)

Grant Rettke | 19 Sep 19:51 2014

How to tangle contents of a noweb-ref block that as source block indicators in it?

Good afternoon,

I work in:

│ (print emacs-version)
│ (print org-version)

│ "24.3.1"
│ "8.2.7c"

My `org' configuration specifies source blocks like this:

│ (setq org-babel-noweb-wrap-start "«")
│ (setq org-babel-noweb-wrap-end "»")

When I tangle this block the output is bit for bit.

When I tangle this other block:

│ (wrap-region-add-wrapper "«" "»" "w" 'org-mode) ;; noweb blocks

(Continue reading)

Richard Lawrence | 19 Sep 17:49 2014

Re: Changed behaviours of LaTeX exporter in version 8.0+

Hi Joseph,

"Kyeong Soo (Joseph) Kim" <kyeongsoo.kim <at> gmail.com> writes:

> Great thanks for your answering my two questions, especially sharing your
> experience for cross-referencing in LaTeX export.
> Though your suggestion for cross-referencing is an excellent workaround, I
> wonder whether there is any benefit using org-mode in writing papers in
> this case; for instance, manual setting of CUSTOM_ID would be a hassle,
> considering that it can be easily & automatically done in LaTeX with
> AUCTeX/RefTeX's label function.

Don't you need to make sure that your sections have a consistent label
in order to refer to them?

At any rate, one of the reasons I use this solution is that I want to be
able to easily use plain LaTeX at points where I discover that I can't
make Org do everything I want.  One of the cases I was worried about,
for example, is having a section reference inside an embedded LaTeX
block.  If you don't know the label ahead of time, you can't use a raw
\ref command inside #+BEGIN_LATEX...#+END_LATEX.  So I like being able
to set the labels via CUSTOM_ID on an as-needed basis. (I don't do it
for every section.)

You might be able to get away with less; it looks to me like the
[[*Foo][Section Foo]] still produces a link to a headline in LaTeX
output.  Does that not work for you?

> I still don't know why the new export engine has brought so many
(Continue reading)

hymie! | 19 Sep 16:46 2014

inconsistency -- agenda, jump to specific day

So I think I found an inconsistency in the agenda and/or in the docs.
Maybe it's just my lack of understanding as usual, but here goes.

Emacs  : GNU Emacs 24.3.1 (i386-mingw-nt6.1.7601) of 2013-03-17 on MARVIN
Package: Org-mode version 8.2.7c (8.2.7c-dist  <at>  c:/ProgramData/Microsoft/Windows/Start Menu/Programs/emacs-24.3/lisp/org/)

According to the docuemntation:
>v d or short d     (org-agenda-day-view)
>v w or short w     (org-agenda-week-view)
>v t     (org-agenda-fortnight-view)
>v m     (org-agenda-month-view)
>v y     (org-agenda-year-view)
>v SPC     (org-agenda-reset-view)
>    Switch to day/week/month/year view. When switching to day or
>    week view, this setting becomes the default for subsequent agenda
>    refreshes. Since month and year views are slow to create, they do not
>    become the default. A numeric prefix argument may be used to jump
>    directly to a specific day of the year, ISO week, month, or year,
>    respectively. For example, 32 d jumps to February 1st, 9 w to ISO
>    week number 9.

"d", however, does not work that way.  Using a numberic prefix before
"d" jumps to that specific day of the **month**, not of the year.
So when I'm looking at the current agenda (for week 15 Sep - 21 Sep),
"5d" takes me to Sept 5th, "26d" takes me to Sept 26th, 35d takes me
to October 5th (the 35th "day of September").

Note that the "current month" had changed, so now, "5d" takes me to
October 5th, not September 5th any more.  To me that's another
inconsistency, but I could see where it's a "feature" and not a "bug".
(Continue reading)

Oleh | 19 Sep 14:23 2014

issue with `org-insert-heading'

Hi all,

I just wanted to point out what I think is a bug in `org-insert-heading'.
The abridged code:

#+begin_src elisp
(let ((adjust-empty-lines t))
  ;; code that does not change `adjust-empty-lines'
  (when adjust-empty-lines
    (if (or (not blank)
            (and blank (not (org-previous-line-empty-p))))
        (org-N-empty-lines-before-current (if blank 1 0)))))

So at the very least there's test that always returns t.

The effect of this code is that when I do "M-RET" 3 times in a blank
file, the first two stars don't get a space after them and get
highlighted differently than the third.
Calling `outline-previous-heading' from the third star moves point to
the first star and not the second, which means that they're not
recognized as proper headings.

What I think 3 "M-RET" should do is to insert a space after each star.
That way they are proper headings with empty headlines.

best regards,

(Continue reading)

Rainer M Krug | 19 Sep 12:59 2014

header arguments, inheritance, and noweb expansion Was: «Macro» expansion in source blocks; code-sharing between blocks

Andreas Kiermeier <andreas.kiermeier <at> gmail.com> writes:

> Thanks Rainer,
> but unfortunately this isn't working. I'm sure I'm doing something
> wrong ... somewhere.
> In case this makes any difference I have in the document header:
> #+PROPERTY: header-args:R :session *R*
> #+PROPERTY: header-args :results output graphics :exports results
> I've now changed the source block header to ":exports none :eval no"
> but now there really is nothing in the output.
> In fact, the corresponding .tex file now contains:
> \begin{table}[h]
> \label{tbl:refyear}
> \caption{Separation outcomes (death or any type of discharge) by
> reference year.}
> nil
> \end{table}
> and in the *Message* buffer I now have:
> Evaluation of this R code-block (tbl-refyear) is disabled.
> org-babel-exp processing...
> Evaluation of this R code-block (tbl-refyear) is disabled.
> executing Latex code block...
(Continue reading)

Rainer M Krug | 19 Sep 12:04 2014

Creating new org headers from code blocks


I have some R code which generates several graphics. I would now like to
generate in R text which is then interpreted by org, upon export, as
normal org code. Furthermore, I would like to create new org headers from
the R code. Imagine I have the R code block below. Executed, I get the
results below:

--8<---------------cut here---------------start------------->8---
* Some code block
#+begin_src R :results raw :wrap :exports both
c("** New header", "[[./graph1.pdf]]", "", "** and second header", "and some text" )

,** New header

,** and second header
and some text
--8<---------------cut here---------------end--------------->8---

I can leave the :wrap, but then the results are not overwritten, but
appended - otherwise it works as expected.

How can I achieve that I get 

(Continue reading)

Rainer M Krug | 19 Sep 11:18 2014

CV in orgmode for export to pdf (and html?)


I am looking for examples / templates for CVs written using org, as I
decided to ose org for my CV.

I fund this oldish conversation


and these two templates for using org to write a CV:


as well this CV without .org file


Also, there does not seem to be anything on worg.

- Can somebody give any further info on org and CVs? 
- How do you do it (I don't assume you write your CVs in Word?), or are
you using LaTeX directly?
- Any other examples and templates online?

If I get enough, I will compile a summary for worg, but I need examples
and information.


(Continue reading)

hymie! | 19 Sep 00:47 2014

list of agenda files in a file


I'd like to add my _archive files to my agenda.  I don't need the entries
clogging up my day-to-day .org files, but I want the items to still
appear in my agenda.

I found this in the org manual:

>The information to be shown is normally collected from all agenda files,
>the files listed in the variable org-agenda-files[98].
>[98] If the value of that variable is not a list, but a single file name,
>then the list of agenda files will be maintained in that external file.

So based on that, I put this in my .emacs file:
  (setq org-agenda-files (quote ("~/org/agenda.file.list")))
but I cannot seem to get this to work.

When that file has a plain old list of filenames in it, I get an error
Agenda file ~/org/agenda.file.list is not in `org-mode'

When that file is empty, then there is nothing in my agenda.  I then
tried using C-c [ to add a file to the list, and I end up with
 '(org-agenda-files (quote ("~/org/file.org" "~/org/agenda.file.list")))
in my .emacs file.

Am I misunderstanding?  The manual sounds like I can maintain a file
that contains a list of files that the agenda should use.  But I can't
seem to make that happen, either automatically or manually.

(Continue reading)