From: "David Thole" <firstname.lastname@example.org> To: Matthew Lundin <email@example.com> Cc: firstname.lastname@example.org Subject: Re: Ticket Management integration, muse mode, etc Date: Tue, 20 Jan 2009 15:21:28 -0600 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> [-- 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 <email@example.com> wrote: > > "David Thole" <firstname.lastname@example.org> 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. Emacsemail@example.com http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2009-01-20 21:21 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-01-20 17:33 David Thole 2009-01-20 18:10 ` Paul R 2009-01-20 18:32 ` Matthew Lundin 2009-01-20 21:21 ` David Thole [this message] 2009-01-21 8:48 ` Paul R
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Ticket Management integration, muse mode, etc' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).