From: "Sullivan, Gregory \(US SSA\)" <gregory.sullivan@baesystems.com>
To: "Sullivan, Gregory (US SSA)" <gregory.sullivan@baesystems.com>,
emacs-orgmode@gnu.org
Subject: RE: set remember default file to be originating .org file
Date: Wed, 6 Aug 2008 16:54:30 -0400 [thread overview]
Message-ID: <73kku8$832p@dmzms99901.na.baesystems.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2240 bytes --]
OK - I did the following. I allow for functions in the filename
positions of templates, changing org-remember.el as follows:
> diff ../../org-6.05b/lisp/org-remember.el ./org-remember.el
321,322c321
< (file (if (and (nth 1 entry) (stringp (nth 1 entry))
< (string-match "\\S-" (nth 1 entry)))
---
> (file (if (nth 1 entry)
351a351,353
> (when (functionp file)
> (setq file (funcall file))
> (message "after funcall file, file = [%S]" file))
~/emacs/org/lisp
>
So my remember template list includes:
("Todo (local)" ?t "* TODO %? %i\n"
,(lambda () (buffer-file-name
org-select-template-original-buffer))
So if I invoke org-remember and choose "t", it will save the resulting
TODO item in the file from which I invoked remember.
Could be made more robust, but it works for me.
Let me know if you think this might be generally useful.
--Greg
--
Gregory T. Sullivan, Ph.D.
BAE Systems Advanced Information Technologies
6 New England Executive Park, Burlington, MA 01803
781-262-4553 (office), 978-430-3461 (cell)
gregory.sullivan@baesystems.com
________________________________________
From: emacs-orgmode-bounces+gregory.sullivan=baesystems.com@gnu.org
[mailto:emacs-orgmode-bounces+gregory.sullivan=baesystems.com@gnu.org]
On Behalf Of Sullivan, Gregory (US SSA)
Sent: Wednesday, August 06, 2008 11:55 AM
To: emacs-orgmode@gnu.org
Subject: [Orgmode] set remember default file to be originating .org file
If I invoke remember from a .org file, e.g. "foo.org", I would like the
default file to which the remembered note is saved to be that file,
"foo.org".
I work on several projects at a time, and the project mix changes
monthly. While on a project, I generate lots of project-specific notes
and TODOs. So, I like to have project-specific .org files.
Any ideas appreciated.
Thanks.
--Greg
--
Gregory T. Sullivan, Ph.D.
BAE Systems Advanced Information Technologies
6 New England Executive Park, Burlington, MA 01803
781-262-4553 (office), 978-430-3461 (cell)
gregory.sullivan@baesystems.com
[-- Attachment #1.2: Type: text/html, Size: 11099 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
next reply other threads:[~2008-08-06 20:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 20:54 Sullivan, Gregory (US SSA) [this message]
2008-09-03 9:36 ` set remember default file to be originating .org file Carsten Dominik
-- strict thread matches above, loose matches on Subject: below --
2008-08-06 15:54 Sullivan, Gregory (US SSA)
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='73kku8$832p@dmzms99901.na.baesystems.com' \
--to=gregory.sullivan@baesystems.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).