Hi,
while we are discussing a new org-remember facility. I've been missing
an option to clock the time I've taken to write down my remember note.
E.g. I use remember to make a small protocoll of a telephone call or
some discussion with a colleague. It would help me alot to if that
time would be cl
Yes, good concept.
> yes
>
>> - possibility to 'pick file/topic first then remember'
>
> No. The idea would be that you refile then or later.
No problem for me. I don't remember a case, when I had to change the
tempalte or target after filling it.
And still, there is `org-remember-goto-last-s
> - 'throw it into the bucket for later'.
>
> what does that mean?
Kind of works as remember now. Currently you have a 'default save to
point' for a particular template. I would guess that most people just
throw it all into the one 'bucket' and sort it out later.
>
>> - org - remember keymap
>
>
On Sep 30, 2009, at 4:45 PM, Tim O'Callaghan wrote:
+1, can we keep/have:
- the templates,
yes
- possibility to 'pick file/topic first then remember'
No. The idea would be that you refile then or later.
- 'throw it into the bucket for later'.
what does that mean?
- org - remember ke
+1, can we keep/have:
- the templates,
- possibility to 'pick file/topic first then remember'
- 'throw it into the bucket for later'.
- org - remember keymap
- local fontification?
- remove need to have remember package installed?
Tim.
2009/9/30 Carsten Dominik :
> I don't know what the others th
I don't know what the others think
... but I think this is a brilliant idea.
- Carsten
On Sep 29, 2009, at 10:48 PM, Samuel Wales wrote:
Hi Carsten,
Here is an idea for a much simpler remember architecture that
simultaneously solves Alan's problem.
1) To me also, a more complicated way
At Tue, 29 Sep 2009 13:48:53 -0700,
Samuel Wales wrote:
>
> Hi Carsten,
>
> Here is an idea for a much simpler remember architecture that
> simultaneously solves Alan's problem.
[...]
> 5) Here is my idea: discard the concept of remember
> buffers entirely.
> - Create the entry at t
Hi Carsten,
Here is an idea for a much simpler remember architecture that
simultaneously solves Alan's problem.
1) To me also, a more complicated way to deal with
remember buffers feels wrong.
2) If there is more than one thing you are working on, the
power of the org hierarchy feel
