[-- Attachment #1.1: Type: text/plain, Size: 1091 bytes --] Hey, This is the first time I ever posted to this list - but did search the archive, and google significantly before posting so I hope this hasn't been asked yet. Right now I use org-mode to manage my tasks. I built scripts to pull from Redmine (a ticket tracking system), and pull it in. That's all working, but there are some notes I really would rather have locally on my disk - like my own notes and all. The problem I'm thinking is that I wouldn't mind pulling this information in my script down to the disk, into muse-mode - so creating my own TOC, and my own files for each issue (say, [[Issue1000]]) What I'd like to do, though, is in the org-file, to have [[Issue1000]] in the file (e.g. ** TODO: [[Issue 1000]]) or maybe a subitem, (e.g. *** [[Issue1000]]) and have it link to the muse mode file itself. Muse works well indepently and I can do this pretty easy, org-mode integration for the link in doing this isn't possible yet. Does anyone know a good option on how to get this working? Is there a workflow thing that may be better for me to do instead? Thanks, David [-- Attachment #1.2: Type: text/html, Size: 1183 bytes --] [-- Attachment #2: Type: text/plain, Size: 204 bytes --] _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Hi David, David> Muse works well indepently and I can do this pretty easy, David> org-mode integration for the link in doing this isn't possible David> yet. Does anyone know a good option on how to get this working? David> Is there a workflow thing that may be better for me to do David> instead? I wished I understood what your problem precisely is, because it sounds really interesting, but I really don't manage to get it. Could you maybe reformulate it please ? -- Paul
"David Thole" <dthole@gmail.com> writes:
>
> The problem I'm thinking is that I wouldn't mind pulling this information in
> my script down to the disk, into muse-mode - so creating my own TOC, and my
> own files for each issue (say, [[Issue1000]]) What I'd like to do, though, is
> in the org-file, to have [[Issue1000]] in the file (e.g. ** TODO: [[Issue
> 1000]]) or maybe a subitem, (e.g. *** [[Issue1000]]) and have it link to the
> muse mode file itself.
Why doesn't the following work for you?
,----
| *** [[file:/path/to/muse/Issue1000][Issue1000]]
`----
You can type C-u C-c C-l within org for a prompt to link to a file.
Or you can type C-c l in the Muse file to store the link and C-c C-l
<up> in org-mode to insert the link.
The manual has a very clear section on hyperlinks.
That said, is there a compelling reason for you to keep your notes in
muse rather than org-mode? Org-mode was created to handle both
ticket/task management and note taking in the same file. You could
keep all the relevant notes (and any data pairs as properties) under
each issue headline. E.g.
,----
| *** TODO Issue 1000
|
| Notes and subheadings go here.
`----
Feel free to let me know if I am misunderstanding the nature of the
problem.
Best,
Matt
[-- Attachment #1.1: Type: text/plain, Size: 2579 bytes --] Thank you to the both of you for responding so quickly. Basically the reasoning why I' doing all this is to try and take more detailed notes on stuff that maybe the end user should not see in the ticket - which right now I kinda have to do. I still want to capture this information, so muse-mode kinda made partial sense for documentation needs. The goal again is really to have my own "private notes" in the end. Matthew hit it right on the head about what I was trying to do - and that's using the file. I apologize for my newbieness with org-mode (I admit while I've used it awhile, I never really scratched much more than the bare surface of this extension), and yes the following would work perfectly fine. The only problem is that a lot of my stuff is automatically generated in one of the files - so keeping notes in the same file complicate matters a bit when it comes to my matching those notes in regard to the next entry. I don't know if I'm being clear about what I'm bringing up, but Matt's post really helped in explaining how to get by with what I feel I need now - but I think I'll need to spend some time and reconsider all this. Thanks, David On Tue, Jan 20, 2009 at 12:32 PM, Matthew Lundin <mdl@imapmail.org> wrote: > > "David Thole" <dthole@gmail.com> writes: > > > > The problem I'm thinking is that I wouldn't mind pulling this information > in > > my script down to the disk, into muse-mode - so creating my own TOC, and > my > > own files for each issue (say, [[Issue1000]]) What I'd like to do, > though, is > > in the org-file, to have [[Issue1000]] in the file (e.g. ** TODO: [[Issue > > 1000]]) or maybe a subitem, (e.g. *** [[Issue1000]]) and have it link to > the > > muse mode file itself. > > Why doesn't the following work for you? > > ,---- > | *** [[file:/path/to/muse/Issue1000][Issue1000]] > `---- > > You can type C-u C-c C-l within org for a prompt to link to a file. > > Or you can type C-c l in the Muse file to store the link and C-c C-l > <up> in org-mode to insert the link. > > The manual has a very clear section on hyperlinks. > > That said, is there a compelling reason for you to keep your notes in > muse rather than org-mode? Org-mode was created to handle both > ticket/task management and note taking in the same file. You could > keep all the relevant notes (and any data pairs as properties) under > each issue headline. E.g. > > ,---- > | *** TODO Issue 1000 > | > | Notes and subheadings go here. > `---- > > Feel free to let me know if I am misunderstanding the nature of the > problem. > > Best, > Matt > [-- Attachment #1.2: Type: text/html, Size: 3153 bytes --] [-- Attachment #2: Type: text/plain, Size: 204 bytes --] _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Hi, David> Thank you to the both of you for responding so quickly. Basically David> the reasoning why I' doing all this is to try and take more David> detailed notes on stuff that maybe the end user should not see in David> the ticket - which right now I kinda have to do. I still want to David> capture this information, so muse-mode kinda made partial sense David> for documentation needs. The goal again is really to have my own David> "private notes" in the end. David> Matthew hit it right on the head about what I was trying to do - David> and that's using the file. I apologize for my newbieness with David> org-mode (I admit while I've used it awhile, I never really David> scratched much more than the bare surface of this extension), and David> yes the following would work perfectly fine. The only problem is David> that a lot of my stuff is automatically generated in one of the David> files - so keeping notes in the same file complicate matters David> a bit when it comes to my matching those notes in regard to the David> next entry. Ok, I think I'm understanding it now. So you have a script that download the issues list from redmine and convert it to an org-mode list of entries. Then you want to have a local file dedicated to each issue, possibly in muse-mode because you like it. What matt proposed would work, but he is also right about the fact that keeping everything in a single org file would give good results as well. Let us know how it turns, bridging BTS and org is very interesting. -- Paul