From: Carsten Dominik <firstname.lastname@example.org> To: Carsten Dominik <email@example.com> Cc: Bernt Hansen <firstname.lastname@example.org>, Matt Lundin <email@example.com>, firstname.lastname@example.org Subject: Re: Re: Questions about org-capture templates and usage Date: Mon, 6 Dec 2010 15:27:20 +0100 [thread overview] Message-ID: <4AF90AC3-9244-4074-BAF8-9A2E4D87F670@gmail.com> (raw) In-Reply-To: <DD780C55-6DE7-4836-B443-FCEC8EEF439C@gmail.com> On Dec 6, 2010, at 9:20 AM, Carsten Dominik wrote: > > On Dec 6, 2010, at 6:02 AM, Alan E. Davis wrote: > >> I am at much greater ease due to these two messages. They solve >> several of my befuddlements about capture. >> >> On Mon, Dec 6, 2010 at 1:59 PM, Bernt Hansen <email@example.com> wrote: >> I visit newly captured items all the time. If you capture >> something (I >> have C-M-r bound to org-capture) and store it with C-c C-c you can >> visit >> it immediately with a double prefix C-u C-u C-M-r as stated in the >> org-capture docstring: >> >> This is exactly what I was looking for in the manual. > > Wow, I cannot believe I forgot to put these into the manual! Crazy. > They are in not (git version). Sigh, one of my many standard typos: They are in NOW. - Carsten > > >> In fact, I think my comment about the manual was partly a response >> to being unable to find this item in the manual, when I know I >> had seen reference to it somewhere. Maybe in my request for items >> to be included in the manual, the docstrings in org-capture.el >> would be scanned. I missed this on my cursory search of that >> file. I will search for it myself, and work on (believe it or not) >> org-help.org, that I use as a helpmate. >> >> I have org-capture assigned to C-c, so C-u C-u C-c c goes straight >> to the last stored item. Perfect. >> >> | >> | (org-capture &optional GOTO KEYS) >> | >> I THINK I understand that GOTO here refers to the prefix C-u ? And >> C-u C-u circumvents this? >> >> | When called interactively with a C-u prefix argument GOTO, don't >> capture >> | anything, just go to the file/headline where the selected template >> | stores its notes. With a double prefix argument C-u C-u, go to >> the last note >> >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> | stored. >> ^^^^^^ >> >> This is it! What I was looking for. >> >> I think, thought it may seem crazy, I would like to still have a >> way to specify in the template that one would remain with the newly >> captured item in its environment, after finalizing. Just the >> same, thinking about that it's an indirect buffer, it makes more >> sense how it works now... > > You can just widen during capture if you wish: C-x n w will show you > the entire buffer. > You still need to finalize at some point with C-c C-c though. > >> >> Awe, heck, these two methods solve my problem well enough... >> >> | >> | When called with a `C-0' (zero) prefix, insert a template at point. >> | >> >> This is a great feature... >> >> | Lisp programs can set KEYS to a string associated with a template >> in >> | `org-capture-templates'. In this case, interactive selection >> will be >> | bypassed. >> `---- >> >> This is something I'd like to see an example of. > > (defun my-capture-k () > (interactive) > (org-capture nil "k")) > > will directly get you into capture template k. > > - Carsten > - Carsten
next prev parent reply other threads:[~2010-12-06 14:27 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-05 6:28 Alan 2010-12-05 11:58 ` Matt Lundin 2010-12-06 3:59 ` Bernt Hansen [not found] ` <firstname.lastname@example.org> 2010-08-30 3:31 ` LaTeX export: Skip headline lines? "Paragraph" sectioning? Alan E. Davis 2010-08-30 4:06 ` Nick Dokos 2010-08-30 5:14 ` Scot Becker 2010-08-30 5:46 ` Nick Dokos 2010-08-30 6:54 ` Thomas S. Dye 2010-08-30 14:22 ` Scot Becker 2010-08-30 16:20 ` Thomas S. Dye 2010-08-30 22:05 ` Scot Becker 2010-08-31 0:04 ` Alan E. Davis 2010-08-30 16:40 ` Alan E. Davis 2010-08-30 17:04 ` Nick Dokos 2010-08-31 1:09 ` Alan E. Davis 2010-08-31 1:43 ` Alan E. Davis 2010-08-31 1:59 ` Thomas S. Dye 2010-08-31 2:01 ` Nick Dokos 2012-03-15 17:24 ` Mail composed using emacs --- saving a copy in an org file Alan E. Davis 2012-03-15 17:34 ` Jos'h Fuller 2012-03-15 17:48 ` Peter Salazar 2012-03-15 17:55 ` brian powell 2012-03-15 18:05 ` brian powell 2012-03-15 19:19 ` Nick Dokos 2012-03-15 19:48 ` brian powell 2012-03-16 9:32 ` Karl Voit 2012-03-16 13:46 ` brian powell 2012-03-16 16:07 ` Memacs and Gnowsis (was: Mail composed using emacs --- saving a copy in an org file.) Karl Voit 2010-12-06 5:02 ` Questions about org-capture templates and usage Alan E. Davis 2010-12-06 8:20 ` Carsten Dominik 2010-12-06 14:27 ` Carsten Dominik [this message] 2010-12-06 8:33 ` Carsten Dominik 2010-12-06 14:10 ` Bernt Hansen 2010-12-06 14:48 ` Nick Dokos 2010-12-06 16:48 ` Nathan Neff 2010-12-06 17:53 ` Carsten Dominik [not found] ` <email@example.com> 2010-12-06 18:08 ` Carsten Dominik 2010-12-07 3:14 ` Štěpán Němec 2010-12-07 19:33 ` Nick Dokos 2010-12-06 21:35 ` Alan Davis 2010-12-05 21:44 ` Charles Cave
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=4AF90AC3-9244-4074-BAF8-9A2E4D87F670@gmail.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Re: Questions about org-capture templates and usage' \ /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).