Hi Martin,
I am rejecting this patch, but only because because I think this issue
is taken care of in org-capture.el Let me know if you do not agree.
Cheers, and thanks for your contribution!
- Carsten
On May 27, 2010, at 11:43 AM, Martin Pohlack wrote:
[resending to get into the patch
On 22.06.2010 15:38, Martin Pohlack wrote:
Is there documentation for migrating from org-remember or will there be
once org-capture shows up in the manual?
Never mind the question, I just saw the exhaustive other mail describing
org-remember :-).
Cheers,
Martin
On 22.06.2010 14:54, Carsten Dominik wrote:
Hi Martin,
I am rejecting this patch, but only because because I think this issue
is taken care of in org-capture.el Let me know if you do not agree.
The documentation for outline path looks promising. Even header paths
are supported -- nice!
On Jun 22, 2010, at 3:38 PM, Martin Pohlack wrote:
On 22.06.2010 14:54, Carsten Dominik wrote:
Hi Martin,
I am rejecting this patch, but only because because I think this
issue
is taken care of in org-capture.el Let me know if you do not agree.
The documentation for outline path looks
[resending to get into the patch tracker]
Hi,
On 15.05.2010 08:42, Carsten Dominik wrote:
On May 14, 2010, at 5:42 AM, Samuel Wales wrote:
On 2010-05-13, Martin Pohlackm...@os.inf.tu-dresden.de wrote:
Is there interest to define remember targets via paths or via ID?
ID would be useful, I
Hi,
On 15.05.2010 08:42, Carsten Dominik wrote:
On May 14, 2010, at 5:42 AM, Samuel Wales wrote:
On 2010-05-13, Martin Pohlackm...@os.inf.tu-dresden.de wrote:
Is there interest to define remember targets via paths or via ID?
ID would be useful, I think.
ID certainly - path could be useful
On May 14, 2010, at 5:42 AM, Samuel Wales wrote:
On 2010-05-13, Martin Pohlack m...@os.inf.tu-dresden.de wrote:
Is there interest to define remember targets via paths or via ID?
ID would be useful, I think.
ID certainly - path could be useful to avoid ambiguities.
- Carsten
Hi,
interest in this problem was indicated to me in private mail, so let my
sum up my findings so far.
I walked through the code in org-remember.el:org-remember-handler.
There seems to be no support for path traversal for the non-interactive
case. The first headline matching is found
On Thu, 13 May 2010 17:48:22 +0200, Martin Pohlack m...@os.inf.tu-dresden.de
wrote:
Hi,
interest in this problem was indicated to me in private mail, so let my
sum up my findings so far.
[...]
I use these two functions for computing the current target headline:
Thanks for these.
On 2010-05-13, Martin Pohlack m...@os.inf.tu-dresden.de wrote:
Is there interest to define remember targets via paths or via ID?
ID would be useful, I think.
--
Q: How many CDC scientists does it take to change a lightbulb?
A: You only think it's dark. [CDC has denied a deadly disease for 25
Let my rephrase the question.
How do I specify the target for a org-remember template such that new
entries become children of b:
* a
** b
*** new entry
If I specify a/b, a new node named a/b is created
* a
** b
* a/b
** new entry
Cheers,
Martin
Hi all,
to practically prevent merge conflicts between the different machines
that I use I want to capture new items not directly under the global
Inbox headline, but under Inbox/$HOSTNAME.
For example, I often capture new items on my desktop and my notebook
and later sync. The new items will
12 matches
Mail list logo
