Bastien writes:
> Hi Richard,
>
> Richard Riley writes:
>
>> ALso it would be really really nice if it would
>> use the existing org file if that file is on the agenda list and I dont
>> specify a path component on the destination file variable in the
>> template.
>
> Mhh... can't parse this, so
Hi Richard,
Richard Riley writes:
> ALso it would be really really nice if it would
> use the existing org file if that file is on the agenda list and I dont
> specify a path component on the destination file variable in the
> template.
Mhh... can't parse this, sorry :/
Can you re-explain agai
Hi Richard,
Richard Riley writes:
> Hi, my head isnt really in org "mode" (oops!) at the moment, how would I
> then implement the template for "files under this directory" as
> originally mentioned?
The in-file and not-in-file conditions use regexp and expanded file
names. You can use your dir
Bastien writes:
> Richard Riley writes:
>
>> I see Bastien and Carsten are in on the thread too, I'll step back and
>> see in what direction this now goes ;) Thanks again for the great
>> feature!
>
> This is how it works right now.
>
> For each agenda custom command or capture template, you can
Richard Riley writes:
> I see Bastien and Carsten are in on the thread too, I'll step back and
> see in what direction this now goes ;) Thanks again for the great
> feature!
This is how it works right now.
For each agenda custom command or capture template, you can define
a context where it wi
Sylvain Rousseau writes:
> It is an org-capture issue. You have to specify the full path of the org file
> in the template even if this file is an agenda
> file. Otherwise org-capture assumes that the file is located in
> `org-directory'.
with no path to use the "existing one" would be a real b
2012/8/23 Carsten Dominik :
> I am wondering if the following feature would be useful as well: Context
> sensitivity sounds most interesting to me if the same key would do different
> things in different contexts. I am not sure if this is possible with the
> current implementation? For exampl
Hi Carsten,
Carsten Dominik writes:
> I am wondering if the following feature would be useful as well: Context
> sensitivity sounds most interesting to me if the same key would do
> different things in different contexts. I am not sure if this is possible
> with the current implementation? For
May be dir local variables could be used?
Carsten Dominik writes:
> Hi Sylvain and Bastien,
>
> this is an interesting idea!
>
> I am wondering if the following feature would be useful as well:
> Context sensitivity sounds most interesting to me if the same key
> would do different things in di
Hi Sylvain and Bastien,
this is an interesting idea!
I am wondering if the following feature would be useful as well: Context
sensitivity sounds most interesting to me if the same key would do different
things in different contexts. I am not sure if this is possible with the
current implemen
Sylvain Rousseau writes:
>> One possible enhancement: allow using only the capture/agenda
>> template instead of the full template in
> `org-context-capture-alist'
>> and `org-context-agenda-alist'.
>
> Good idea! Adding it to my todo list with org-context ;-)
Actually I love your idea so much I
It is an org-capture issue. You have to specify the full path of the org
file in the template even if this file is an agenda file. Otherwise
org-capture assumes that the file is located in `org-directory'.
> Can you advise further? (Looks great regardless btw!)
Thank you, building on Bastien's s
Richard Riley writes:
> Sylvain Rousseau writes:
>
>> Have a look at https://github.com/thisirs/org-context : Context agenda and
>> capture for Org-mode
>>
>> It dynamically adds templates depending on the buffer you are currently
>> editing. New templates are available with the key
>> "c" or
Sylvain Rousseau writes:
> Have a look at https://github.com/thisirs/org-context : Context agenda and
> capture for Org-mode
>
> It dynamically adds templates depending on the buffer you are currently
> editing. New templates are available with the key
> "c" or merged if there is no conflict wi
Sylvain Rousseau writes:
> Have a look at https://github.com/thisirs/org-context : Context agenda and
> capture for Org-mode
>
> It dynamically adds templates depending on the buffer you are currently
> editing. New templates are available with the key
> "c" or merged if there is no conflict wi
> One possible enhancement: allow using only the capture/agenda
> template instead of the full template in `org-context-capture-alist'
> and `org-context-agenda-alist'.
Good idea! Adding it to my todo list with org-context ;-)
If you think this addon deserves to be added to the contrib directory,
Bastien writes:
> allow using only the capture/agenda
> template instead of the full template
Of course, this should read:
... template letter instead of the full template definition.
--
Bastien
Hi Sylvain,
Sylvain Rousseau writes:
> Have a look at https://github.com/thisirs/org-context : Context
> agenda and capture for Org-mode
I *love* it! This would be a great addition to contrib/lisp/ --
doors are open, just ring the bell.
One possible enhancement: allow using only the capture/
Have a look at https://github.com/thisirs/org-context : Context agenda and
capture for Org-mode
It dynamically adds templates depending on the buffer you are currently
editing. New templates are available with the key "c" or merged if there is
no conflict with existing ones.
Hope this helps,
Sy
Currently I maintain a datetree journal capture using a template so
,
| ("j" "journal" entry (file+datetree "journal.org")
| "* %?\n\t:PROPERTIES:\n\t:DateCreated:
%T\n\t:Link: %a\n\t:END:\n")
`
I also use j rockways' eproject set
20 matches
Mail list logo
