From: Timm Lichte <timm.lichte@mailbox.org>
To: Christian Egli <christian.egli@sbs.ch>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org mode for meeting minutes
Date: Wed, 25 Mar 2020 23:39:22 +0100 [thread overview]
Message-ID: <57ea3939-e89f-7846-fb4d-e63b3798998f@mailbox.org> (raw)
In-Reply-To: <87k13axe5q.fsf@sbs.ch>
Hi Christian,
Am 24.03.20 um 11:04 schrieb Christian Egli:
> Hi Timm
>
> Timm Lichte writes:
>
>> Just for your amusement: I've developed a very different but effective
>> way of taking minutes with org-mode that uses just lists and
>> enumerations. I have been using this solution for more than a year on
>> a daily basis and I'm really happy with it (and colleagues don't
>> complain). Speed, simplicity and readability for non-emacsers is
>> critical in my job, so the solutions you are proposing would be
>> overkill.
>
> This is really interesting! I can see that you are very efficient with
> this. I think my solution is more using the standard org-mode
> infrastructure, I don't define any export for example.
Glad you find it interesting. I think both ways of taking notes have
their merits and use cases. In small productive project meetings, I'd
rather use more of the org-mode infrastructure. When there is a larger
event with changing participants and its really important to document
and keep track of what is going on, simple annotated lists fare better
in my experience.
>> You can have a look at the style and code here:
>>
>> https://github.com/timmli/org-minutes-dev
>
> If I understand correctly you are defining some kind of extra list
> markup (is something a task or a decision, etc) and the you wrote a
> custom exporter that produces fancy LaTeX for the minutes (well, if I
> understand correctly it really is a custom exporter that generates
> org-mode and then LaTeX from there).
Yes, I'm basically extending the syntax for descriptions and overlaying
it with some convenient font-lock. My custom exporter pushes everything
in a temporary buffer and replaces the minutes notation with LaTeX
expressions and then starts the regular org-export. This probably looks
awkward but gives me full flexibility.
> I don't quite understand how the LaTeX works. Is this some kind of two
> column layout or do you keep the action item markers and the assignees
> in the margin? Can you post the produced LaTeX?
The LaTeX template builds on the article documentclass and basically
puts some of the item types also on the regular margin with \marginnote
from the marginnote package. Some of the important types are also shown
in the outline using \addcontentsline.
The LaTeX document is just a list of sections with nested itemize
environments. One item would look like this:
\item \ActionTag{Peter}{::} \ActionTagMargin{Peter}Something to do.
I've pushed the TeX file of the example to the repository. Hope this
makes it clearer.
>> Any feedback is greatly appreciated. But keep in mind that the code is
>> not polished at all -- this is a hobby project of an elisp dilettante.
>
> It would be good to package this. The code would get more usage and
> you'd get more feedback.
I'm really hesitant to make this a MELPA package right away, if this is
what you mean. The font-lock and everything is really individual and
non-generic. But I'll think about it.
Best,
Timm
>
> Thanks
> Christian
>
> --
> Christian Egli
> Swiss Library for the Blind, Visually Impaired and Print Disabled
> Grubenstrasse 12, CH-8045 Zürich, Switzerland
>
next prev parent reply other threads:[~2020-03-25 22:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 14:03 Org mode for meeting minutes Christian Egli
2019-10-31 15:49 ` Fraga, Eric
2019-10-31 17:11 ` Ken Mankoff
2020-03-23 9:36 ` Christian Egli
2020-03-23 11:39 ` Eric S Fraga
2020-03-23 13:33 ` Axel Kielhorn
2020-03-23 13:47 ` Carsten Dominik
2020-03-23 18:09 ` Pankaj Jangid
2020-03-23 22:00 ` Nick Dokos
2020-03-24 10:09 ` Pankaj Jangid
2020-03-23 20:03 ` Timm Lichte
2020-03-24 10:04 ` Christian Egli
2020-03-25 22:39 ` Timm Lichte [this message]
2020-03-26 8:28 ` Christian Egli
2020-03-24 11:19 ` Eric S Fraga
2020-03-24 12:00 ` Eric S Fraga
2020-03-25 17:55 ` Bob Newell
2020-03-25 19:02 ` Diego Zamboni
2019-11-01 12:49 ` John Kitchin
2019-11-03 20:49 ` @name-tags instead of TODO keywords to assign people (was: Org mode for meeting minutes) Karl Voit
2019-11-03 21:03 ` Tim Cross
2020-02-12 9:12 ` Org mode for meeting minutes Bastien
2020-07-07 11:44 ` Adam Spiers
2020-07-07 16:21 ` Alexander Adolf
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=57ea3939-e89f-7846-fb4d-e63b3798998f@mailbox.org \
--to=timm.lichte@mailbox.org \
--cc=christian.egli@sbs.ch \
--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).