From: Matthew Lundin <mdl@imapmail.org>
To: David Thole <dthole@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Ticket Management integration, muse mode, etc
Date: Tue, 20 Jan 2009 12:32:32 -0600 [thread overview]
Message-ID: <87ljt5n7zz.fsf@fastmail.fm> (raw)
In-Reply-To: <b7b383410901200933r129868cbv3099005cf7bbcd87@mail.gmail.com> (David Thole's message of "Tue\, 20 Jan 2009 11\:33\:31 -0600")
"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
next prev parent reply other threads:[~2009-01-20 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 17:33 Ticket Management integration, muse mode, etc David Thole
2009-01-20 18:10 ` Paul R
2009-01-20 18:32 ` Matthew Lundin [this message]
2009-01-20 21:21 ` David Thole
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 \
--in-reply-to=87ljt5n7zz.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=dthole@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public 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).