[O] Re: [Orgmode] Re: Automatic noexport tag based on rules?
John Hendy jw.he...@gmail.com writes: On Sun, Mar 27, 2011 at 2:37 PM, Samuel Wales samolog...@gmail.com wrote: That is indeed an excellent solution if you want to add a tag for a todo kw. However, I wonder if there is a direct approach, where the exporter simply does not export if it is a certain todo kw. Is the solution to have the exporter delete anything with that todo kw? Or is there a way to have it skip? I think that was Carsten's suggestion a bit back, but I'm not sure. I think I asked if it was just deleting as it channeled through the export function but didn't get a response. Looking back, though, I'm sure that's what it was and my question was probably a bit silly :) You are correct. The export hook that Carsten provided deletes items in a temporary buffer, not in your org files. In fact, you can use the export hooks to do almost anything to this temporary buffers before they are exported; your original org files will not be touched. And yes, I have turned this off as I find adding :noexport: to ever todo in addition to whatever tags I already use to ID the project/task is annoying and ugly. I've toyed with simply having a * Tracking headline at the beginning of each file where I dump todos via capture and track time and then having that have a top level noexport tag to take care of things. That's pretty much nice, but I still like todos created during meeting minutes or in the context of some other project notes to stay where they make sense rather than separating them from their location and putting them elsewhere. So I've got some solutions but am not quite happy yet. I should re-visit Carsten's solution to strip it on export. That would probably be the ticket. Yes, that would be the easiest solution, requiring no additional markup. Best, Matt
Re: [O] Re: [Orgmode] Re: Automatic noexport tag based on rules?
On 29.3.2011, at 20:40, Matt Lundin wrote: John Hendy jw.he...@gmail.com writes: On Sun, Mar 27, 2011 at 2:37 PM, Samuel Wales samolog...@gmail.com wrote: That is indeed an excellent solution if you want to add a tag for a todo kw. However, I wonder if there is a direct approach, where the exporter simply does not export if it is a certain todo kw. Is the solution to have the exporter delete anything with that todo kw? Or is there a way to have it skip? I think that was Carsten's suggestion a bit back, but I'm not sure. I think I asked if it was just deleting as it channeled through the export function but didn't get a response. Looking back, though, I'm sure that's what it was and my question was probably a bit silly :) You are correct. The export hook that Carsten provided deletes items in a temporary buffer, not in your org files. In fact, you can use the export hooks to do almost anything to this temporary buffers before they are exported; your original org files will not be touched. And yes, I have turned this off as I find adding :noexport: to ever todo in addition to whatever tags I already use to ID the project/task is annoying and ugly. I've toyed with simply having a * Tracking headline at the beginning of each file where I dump todos via capture and track time and then having that have a top level noexport tag to take care of things. That's pretty much nice, but I still like todos created during meeting minutes or in the context of some other project notes to stay where they make sense rather than separating them from their location and putting them elsewhere. So I've got some solutions but am not quite happy yet. I should re-visit Carsten's solution to strip it on export. That would probably be the ticket. Yes, that would be the easiest solution, requiring no additional markup. I have a good patch for this lined up - will check it in tomorrow. - Carsten
Re: [O] Re: [Orgmode] Re: Automatic noexport tag based on rules?
On 29.3.2011, at 23:05, Carsten Dominik wrote: On 29.3.2011, at 20:40, Matt Lundin wrote: John Hendy jw.he...@gmail.com writes: On Sun, Mar 27, 2011 at 2:37 PM, Samuel Wales samolog...@gmail.com wrote: That is indeed an excellent solution if you want to add a tag for a todo kw. However, I wonder if there is a direct approach, where the exporter simply does not export if it is a certain todo kw. Is the solution to have the exporter delete anything with that todo kw? Or is there a way to have it skip? I think that was Carsten's suggestion a bit back, but I'm not sure. I think I asked if it was just deleting as it channeled through the export function but didn't get a response. Looking back, though, I'm sure that's what it was and my question was probably a bit silly :) You are correct. The export hook that Carsten provided deletes items in a temporary buffer, not in your org files. In fact, you can use the export hooks to do almost anything to this temporary buffers before they are exported; your original org files will not be touched. And yes, I have turned this off as I find adding :noexport: to ever todo in addition to whatever tags I already use to ID the project/task is annoying and ugly. I've toyed with simply having a * Tracking headline at the beginning of each file where I dump todos via capture and track time and then having that have a top level noexport tag to take care of things. That's pretty much nice, but I still like todos created during meeting minutes or in the context of some other project notes to stay where they make sense rather than separating them from their location and putting them elsewhere. So I've got some solutions but am not quite happy yet. I should re-visit Carsten's solution to strip it on export. That would probably be the ticket. Yes, that would be the easiest solution, requiring no additional markup. I have a good patch for this lined up - will check it in tomorrow. In fact, I just now pushed it. To export without DONE tasks, use #+OPTION: donetasks:nil - Carsten
Re: [O] Re: [Orgmode] Re: Automatic noexport tag based on rules?
On Tue, Mar 29, 2011 at 4:15 PM, Carsten Dominik carsten.domi...@gmail.com wrote: On 29.3.2011, at 23:05, Carsten Dominik wrote: On 29.3.2011, at 20:40, Matt Lundin wrote: John Hendy jw.he...@gmail.com writes: I have a good patch for this lined up - will check it in tomorrow. In fact, I just now pushed it. To export without DONE tasks, use #+OPTION: donetasks:nil - Carsten Thanks! Not to be all annoying... but how hard would this be? ,--- | #+OPTION: tasks:nil `--- I don't ever export *any* tasks since it's always my work notes -- I have to keep good records for Intellectual Property purposes and my todos are never pertinent. Perhaps users would find both of these options helpful? John
Re: [O] Re: [Orgmode] Re: Automatic noexport tag based on rules?
On 29.3.2011, at 23:48, John Hendy wrote: On Tue, Mar 29, 2011 at 4:15 PM, Carsten Dominik carsten.domi...@gmail.com wrote: On 29.3.2011, at 23:05, Carsten Dominik wrote: On 29.3.2011, at 20:40, Matt Lundin wrote: John Hendy jw.he...@gmail.com writes: I have a good patch for this lined up - will check it in tomorrow. In fact, I just now pushed it. To export without DONE tasks, use #+OPTION: donetasks:nil - Carsten Thanks! Not to be all annoying... but how hard would this be? Not hard at all. It is done. - Carsten ,--- | #+OPTION: tasks:nil `--- I don't ever export *any* tasks since it's always my work notes -- I have to keep good records for Intellectual Property purposes and my todos are never pertinent. Perhaps users would find both of these options helpful? John
Re: [O] Re: [Orgmode] Re: Automatic noexport tag based on rules?
On Tue, Mar 29, 2011 at 5:49 PM, Carsten Dominik carsten.domi...@gmail.com wrote: On 29.3.2011, at 23:48, John Hendy wrote: On Tue, Mar 29, 2011 at 4:15 PM, Carsten Dominik carsten.domi...@gmail.com wrote: On 29.3.2011, at 23:05, Carsten Dominik wrote: On 29.3.2011, at 20:40, Matt Lundin wrote: John Hendy jw.he...@gmail.com writes: I have a good patch for this lined up - will check it in tomorrow. In fact, I just now pushed it. To export without DONE tasks, use #+OPTION: donetasks:nil - Carsten Thanks! Not to be all annoying... but how hard would this be? Not hard at all. It is done. 1) I figured it probably wasn't hard, but just asked politely anyway :) 2) Thanks a ton. This is fantastic. John - Carsten ,--- | #+OPTION: tasks:nil `--- I don't ever export *any* tasks since it's always my work notes -- I have to keep good records for Intellectual Property purposes and my todos are never pertinent. Perhaps users would find both of these options helpful? John
Re: [O] Re: [Orgmode] Re: Automatic noexport tag based on rules?
On 30.3.2011, at 00:50, John Hendy wrote: On Tue, Mar 29, 2011 at 5:49 PM, Carsten Dominik carsten.domi...@gmail.com wrote: On 29.3.2011, at 23:48, John Hendy wrote: On Tue, Mar 29, 2011 at 4:15 PM, Carsten Dominik carsten.domi...@gmail.com wrote: On 29.3.2011, at 23:05, Carsten Dominik wrote: On 29.3.2011, at 20:40, Matt Lundin wrote: John Hendy jw.he...@gmail.com writes: I have a good patch for this lined up - will check it in tomorrow. In fact, I just now pushed it. To export without DONE tasks, use #+OPTION: donetasks:nil - Carsten Thanks! Not to be all annoying... but how hard would this be? Not hard at all. It is done. 1) I figured it probably wasn't hard, but just asked politely anyway :) 2) Thanks a ton. This is fantastic. I was to fast, the implementations was not good. Now there is only one variable, org-export-with-tasks. It can be nil to remove all tasks, `todo' to remove the DONE tasks, or a list of tasks to keep for export. For example #+OPTIONS: tasks:todo or #+OPTIONS: tasks:(TODO WAITING) I think this is much cleaner. - Carsten
[O] Re: [Orgmode] Re: Automatic noexport tag based on rules?
That is indeed an excellent solution if you want to add a tag for a todo kw. However, I wonder if there is a direct approach, where the exporter simply does not export if it is a certain todo kw. Is the solution to have the exporter delete anything with that todo kw? Or is there a way to have it skip? One advantage of this approach is that there might be a lot of contexts in which you don't need the noexport tag.
[O] Re: [Orgmode] Re: Automatic noexport tag based on rules?
On Sun, Mar 27, 2011 at 2:37 PM, Samuel Wales samolog...@gmail.com wrote: That is indeed an excellent solution if you want to add a tag for a todo kw. However, I wonder if there is a direct approach, where the exporter simply does not export if it is a certain todo kw. Is the solution to have the exporter delete anything with that todo kw? Or is there a way to have it skip? I think that was Carsten's suggestion a bit back, but I'm not sure. I think I asked if it was just deleting as it channeled through the export function but didn't get a response. Looking back, though, I'm sure that's what it was and my question was probably a bit silly :) And yes, I have turned this off as I find adding :noexport: to ever todo in addition to whatever tags I already use to ID the project/task is annoying and ugly. I've toyed with simply having a * Tracking headline at the beginning of each file where I dump todos via capture and track time and then having that have a top level noexport tag to take care of things. That's pretty much nice, but I still like todos created during meeting minutes or in the context of some other project notes to stay where they make sense rather than separating them from their location and putting them elsewhere. So I've got some solutions but am not quite happy yet. I should re-visit Carsten's solution to strip it on export. That would probably be the ticket. I happen to hate how inline tasks look. That's just me, though! One advantage of this approach is that there might be a lot of contexts in which you don't need the noexport tag. John
[Orgmode] Re: Automatic noexport tag based on rules?
Reviving this as I can't believe the following solution was overlooked! On Tue, Feb 8, 2011 at 6:29 PM, John Hendy jw.he...@gmail.com wrote: Hi, My apologies if this has been discussed. I couldn't find it. I write everything from work in org-mode for several reasons. Primarily, it's my documentation system for research in order to properly document Intellectual Property (IP) information. It's also for todos and contacts. When it comes to exporting my notes into PDF for use in an IP notebook... I dont' want my todos in there. Is there a way to automatically tag TODOs with :noexport:? YES! While perusing Bernt Hanson's page ( http://doc.norang.ca/org-mode.html#ToDoStateTriggers) I noticed the following: ,- | I have a few triggers that automatically assign tags to tasks based on | state changes. If a task moves to CANCELLED state then it gets a CANCELLED tag. | Moving a CANCELLED task back to TODO removes the CANCELLED tag. | These are used for filtering tasks in agenda views which I'll talk about later. | ... then he shows the code used to set =org-todo-state-tags-triggers= `- Sweetness, I thought. In experimenting: ,- | (setq org-todo-state-tags-triggers | (quote ((TODO (noexport . t) `- works *perfectly*. Well, that is in my 0.2 seconds of experimentation, it worked. New headline - C-c C-t - ** TODO whatever :noexport: I'm a happy camper. I had resolved to arranging my file with a separate =* Tasks= top level item at the top of each file to store all todos (I may still do this) and then I could just tag the whole headline with :noexport: to keep all the todos out of the export since I'm often typing notes or something and the TODO seems to fit better in the context of the notes rather than having to stuff it into a bucket at the top with TODOs from all kinds of other stuff.. At least if I don't do this, I have some options. Adding a todo in place will keep it from being exported when I print out my reports. The world is safe again... Best regards, John Or simply add the TODO category to the noexport category altogether? I haven't turned up anything quite along these lines. One post suggested using TODO keyword COMMENT [1], but that just seems to perhaps exclude from export (didn't try) but I know for sure it removes it from agenda view. I want TODOs in agenda but don't want them showing up with my LaTeX export. I typically print out my work to-date each month or so and have to comb through my org file for that month, manually adding :noexport: to my TODOs. Even if I still do this for a few things here and there... it will save me a lot of time. I suppose I could keep a separate TODO.org file, but I really like the process of being able to add them anywhere -- it seems more natural to do that in the flow, particularly in meetings, than to constantly switch buffers or even use remember to keep sending things related to the current topic away to their own island. I'm 80% confident that the answer is ridiculously simply and I just haven't searched the right thing. Thanks for enlightening me! Thanks, John ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
