From: Thomas Holst <Thomas_Holst@gmx.de>
To: Thomas Holst <thomas.holst@de.bosch.com>
Cc: Bastien <bzg@gnu.org>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
Thomas Holst <Thomas_Holst@gmx.de>
Subject: Re: [patch] capture property table-line-pos can be a function
Date: Mon, 17 Mar 2014 17:58:30 +0100 [thread overview]
Message-ID: <87a9co4v9l@gmx.de> (raw)
In-Reply-To: <ywodd2hl46df@de.bosch.com> (Thomas Holst's message of "Mon, 17 Mar 2014 08:43:56 +0100")
[-- Attachment #1: Type: text/plain, Size: 736 bytes --]
Hi,
> Hi Bastien,
>
> · Bastien <bzg@gnu.org> wrote:
>> Thomas Holst <Thomas_Holst@gmx.de> writes:
>>
>>> Given a table with several sections and a capture template for entries
>>> in this table. The sections are dynamic, so a static value for
>>> table-line-pos does not help. With this patch table-line-pos can be:
>>>
>>> - a string like "II-2"
>>> - a varialbe containing a string
>>> - or a function
>>> The function has to return a string which qualifies for table-line-pos
>>>
>>> This serves me well and I am using it for more than one year now.
>>
>> This sounds useful. Could you also provide a patch for the
>> documentation?
>>
>> Thanks in advance!
ok here is the patch for documentation.
--
Bis neulich ...
Thomas
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: patch for new fatures for table-line-pos --]
[-- Type: text/x-diff, Size: 1150 bytes --]
From 436e5adb0a9d0bc9ac37352bd90018c973dfdabf Mon Sep 17 00:00:00 2001
From: Thomas Holst <Thomas_Holst@gmx.de>
Date: Mon, 17 Mar 2014 09:01:40 +0100
Subject: [PATCH] docu change for table-line-pos new feature
* org.texi: document new features of `table-line-pos' in capture
templates
---
doc/org.texi | 7 ++++---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index b53b668..2bebae4 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -7095,9 +7095,10 @@ narrow it so that you only see the new material.
@item :table-line-pos
Specification of the location in the table where the new line should be
-inserted. It should be a string like @code{"II-3"} meaning that the new
-line should become the third line before the second horizontal separator
-line.
+inserted. It can be a string, a variable holding a string or a function
+returning a string. The string should look like @code{"II-3"} meaning that
+the new line should become the third line before the second horizontal
+separator line.
@item :kill-buffer
If the target file was not yet visited when capture was invoked, kill the
--
1.7.9
next prev parent reply other threads:[~2014-03-17 16:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 20:07 [patch] capture property table-line-pos can be a function Thomas Holst
2014-03-17 0:51 ` Bastien
2014-03-17 7:43 ` Thomas Holst
2014-03-17 16:58 ` Thomas Holst [this message]
2014-03-18 16:12 ` Bastien
2014-03-18 18:27 ` Thomas Holst
2014-03-19 8:36 ` Bastien
2014-03-19 9:53 ` Thomas Holst
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=87a9co4v9l@gmx.de \
--to=thomas_holst@gmx.de \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=thomas.holst@de.bosch.com \
/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).