From: Axel Kielhorn <org-mode@axelkielhorn.de>
To: Org-Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Columnview *** is exported as <b>*<b>
Date: Wed, 27 Jan 2016 19:08:02 +0100 [thread overview]
Message-ID: <D8D2DD2A-DBCB-443B-AECF-CED5BFE96785@axelkielhorn.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 758 bytes --]
Hi,
I use org to track time and money spend on a project.
This project has several sub levels that are assigned to certain workers.
To view and edit the time and money spend, I use columnview which works fine.
When I want to report about our effort I want to export a columnview table.
In this table the tasks are shown with *, **, and *** to indicate the level.
In the export the *** is rendered as a bold *.
Right now I insert a space between the ** but that is not really efficient.
Is there a way to render the different level via different indenting as it is done for clocktables?
I looked at the code for clocktable but that is above my understanding of elisp.
I’m using org-mode 8.3.3-17 from ELPA with emacs 24.5.
Axel
[-- Attachment #2: ECM-Columnview.html --]
[-- Type: text/html, Size: 8984 bytes --]
[-- Attachment #3: ECM-Columnview.org --]
[-- Type: application/octet-stream, Size: 1814 bytes --]
#+TITLE: ECM
#+AUTHOR: Axel Kielhorn
#+LANGUAGE: de
#+OPTIONS: toc:nil
#+OPTIONS: tags:nil
#+OPTIONS: todo:t
#+OPTIONS: pri:t
#+OPTIONS: p:t
* Top Level
:PROPERTIES:
:COLUMNS: %40ITEM(Baugruppe) %6Zeit{+} %6Effort(Plan){+} %6Kosten{+} %10Fällig %Fertig{X/} %8TAGS(Verant.):
:END:
#+BEGIN: columnview :hlines 1 :id local
| Baugruppe | Zeit | Plan | Kosten | Fällig | Fertig | Verant. |
|----------------------+------+------+--------+------------+--------+---------|
| * Top Level | 24 | 44.0 | 1050 | | [2/4] | |
| ** Sub level 1 | 12 | 2d | 500 | 2016-03-12 | [ ] | :MA1: |
| ** Sub level 2 | 12 | 28 | 550 | 2016-03-12 | [2/3] | |
| *** Sub sub level 2a | 4 | 8 | 100 | 2016-03-12 | [X] | :MA2: |
| *** Sub sub level 2b | 4 | 8 | 400 | 2016-03-12 | [X] | :MA2: |
| *** Sub sub level 2c | 4 | 12 | 50 | 2016-03-12 | [ ] | :MA1: |
#+END:
** Sub level 1 :MA1:
:PROPERTIES:
:Effort: 2d
:Zeit: 12
:Kosten: 500
:Fällig: 2016-03-12
:Fertig: [ ]
:END:
** Sub level 2
:PROPERTIES:
:Effort: 28
:Zeit: 12
:Kosten: 550
:Fällig: 2016-03-12
:END:
*** Sub sub level 2a :MA2:
:PROPERTIES:
:Effort: 8
:Zeit: 4
:Kosten: 100
:Fällig: 2016-03-12
:Fertig: [X]
:END:
*** Sub sub level 2b :MA2:
:PROPERTIES:
:Effort: 8
:Zeit: 4
:Kosten: 400
:Fällig: 2016-03-12
:Fertig: [X]
:END:
*** Sub sub level 2c :MA1:
:PROPERTIES:
:Effort: 12
:Zeit: 4
:Kosten: 50
:Fällig: 2016-03-12
:Fertig: [ ]
:END:
next reply other threads:[~2016-01-27 18:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 18:08 Axel Kielhorn [this message]
2016-02-04 22:10 ` Columnview *** is exported as <b>*<b> Nicolas Goaziou
2016-02-05 11:12 ` Michael Brand
2016-02-05 23:07 ` Nicolas Goaziou
2016-02-06 8:07 ` Michael Brand
2016-02-11 20:41 ` Axel Kielhorn
2016-02-11 23:46 ` Nicolas Goaziou
2016-02-12 13:41 ` Axel Kielhorn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D8D2DD2A-DBCB-443B-AECF-CED5BFE96785@axelkielhorn.de \
--to=org-mode@axelkielhorn.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).