[Orgmode] Re: Problem with 7.02 - org-capture-templates not set from init file
One thing I noticed that changed in org-install.el from 7.01h to 7.02 - in 7.02 is being explicitly defined in org-install.el as nil, that wasn't happening before. 7.01h: ;;;### (autoloads (org-capture-import-remember-templates org-capture-insert-template-here ;; org-capture) org-capture lisp/org-capture.el (19549 1164)) ;;; Generated autoloads from lisp/org-capture.el (autoload 'org-capture org-capture \ Capture something. \\org-capture-mode-map This will let you select a template from `org-capture-templates', and then file the newly captured information. The text is immediately inserted at the target location, and an indirect buffer is shown where you can edit it. Pressing \\[org-capture-finalize] brings you back to the previous state of Emacs, so that you can continue your work. When called interactively with a \\[universal-argument] 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 \\[universal-argument] \\[universal-argument], go to the last note stored. When called with a `C-0' (zero) prefix, insert a template at point. Lisp programs can set KEYS to a string associated with a template in `org-capture-templates'. In this case, interactive selection will be bypassed. \(fn optional GOTO KEYS) t nil) 7.02 ;;;### (autoloads (org-capture-import-remember-templates org-capture-insert-template-here ;; org-capture org-capture-templates) org-capture lisp/org-capture.el ;; (19658 27920)) ;;; Generated autoloads from lisp/org-capture.el (defvar org-capture-templates nil \ Templates for the creation of new entries. Each entry is a list with the following items: keys The keys that will select the template, as a string, characters only, for example \a\ for a template to be selected with a single key, or \bt\ for selection with two keys. When using several keys, keys using the same prefix key must be together in the list and preceded by a 2-element entry explaining the prefix key, for example (\b\ \Templates for marking stuff to buy\) The \C\ key is used by default for quick access to the customization of the template variable. But if you want to use that key for a template, you can. description A short string describing the template, will be shown during selection. type The type of entry. Valid types are: entry an Org-mode node, with a headline. Will be filed as the child of the target entry or as a top-level entry. itema plain list item, will be placed in the first plain list at the target location. checkitem a checkbox item. This differs from the plain list item only is so far as it uses a different default template. table-line a new line in the first table at target location. plain text to be inserted as it is. target Specification of where the captured item should be placed. In Org-mode files, targets usually define a node. Entries will become children of this node, other types will be added to the table or list in the body of this node. Valid values are: (file \path/to/file\) Text will be placed at the beginning or end of that file (id \id of existing org entry\) File as child of this entry, or in the body of the entry (file+headline \path/to/file\ \node headline\) Fast configuration if the target heading is unique in the file (file+olp \path/to/file\ \Level 1 heading\ \Level 2\ ...) For non-unique headings, the full path is safer (file+regexp \path/to/file\ \regexp to find location\) File to the entry matching regexp (file+datetree \path/to/file\) Will create a heading in a date tree (file+function \path/to/file\ function-finding-location) A function to find the right location in the file (clock) File to the entry that is currently being clocked (function function-finding-location) Most general way, write your own function to find both file and location template The template for creating the capture item. If you leave this empty, an appropriate default template will be used. See below for more details. Instead of a string, this may also be one of (file \/path/to/template-file\)
Re: [Orgmode] Re: Problem with 7.02 - org-capture-templates not set from init file
On Nov 2, 2010, at 3:29 PM, Jeffrey DeLeo wrote: One thing I noticed that changed in org-install.el from 7.01h to 7.02 - in 7.02 is being explicitly defined in org-install.el as nil, that wasn't happening before. That is right. However, when org-capture gets loaded, the value will change to the customize value - I hope. Greetings - Carsten 7.01h: ;;;### (autoloads (org-capture-import-remember-templates org-capture- insert-template-here ;; org-capture) org-capture lisp/org-capture.el (19549 1164)) ;;; Generated autoloads from lisp/org-capture.el (autoload 'org-capture org-capture \ Capture something. \\org-capture-mode-map This will let you select a template from `org-capture-templates', and then file the newly captured information. The text is immediately inserted at the target location, and an indirect buffer is shown where you can edit it. Pressing \\[org-capture-finalize] brings you back to the previous state of Emacs, so that you can continue your work. When called interactively with a \\[universal-argument] 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 \\[universal- argument] \\[universal-argument], go to the last note stored. When called with a `C-0' (zero) prefix, insert a template at point. Lisp programs can set KEYS to a string associated with a template in `org-capture-templates'. In this case, interactive selection will be bypassed. \(fn optional GOTO KEYS) t nil) 7.02 ;;;### (autoloads (org-capture-import-remember-templates org-capture- insert-template-here ;; org-capture org-capture-templates) org-capture lisp/org- capture.el ;; (19658 27920)) ;;; Generated autoloads from lisp/org-capture.el (defvar org-capture-templates nil \ Templates for the creation of new entries. Each entry is a list with the following items: keys The keys that will select the template, as a string, characters only, for example \a\ for a template to be selected with a single key, or \bt\ for selection with two keys. When using several keys, keys using the same prefix key must be together in the list and preceded by a 2-element entry explaining the prefix key, for example (\b\ \Templates for marking stuff to buy\) The \C\ key is used by default for quick access to the customization of the template variable. But if you want to use that key for a template, you can. description A short string describing the template, will be shown during selection. type The type of entry. Valid types are: entry an Org-mode node, with a headline. Will be filed as the child of the target entry or as a top-level entry. itema plain list item, will be placed in the first plain list at the target location. checkitem a checkbox item. This differs from the plain list item only is so far as it uses a different default template. table-line a new line in the first table at target location. plain text to be inserted as it is. target Specification of where the captured item should be placed. In Org-mode files, targets usually define a node. Entries will become children of this node, other types will be added to the table or list in the body of this node. Valid values are: (file \path/to/file\) Text will be placed at the beginning or end of that file (id \id of existing org entry\) File as child of this entry, or in the body of the entry (file+headline \path/to/file\ \node headline\) Fast configuration if the target heading is unique in the file (file+olp \path/to/file\ \Level 1 heading\ \Level 2\ ...) For non-unique headings, the full path is safer (file+regexp \path/to/file\ \regexp to find location \) File to the entry matching regexp (file+datetree \path/to/file\) Will create a heading in a date tree (file+function \path/to/file\ function-finding- location) A function to find the right location in the file (clock) File to the entry that is currently being clocked (function function-finding-location) Most general way, write your own function to find both file and location template The template for creating the capture item. If you leave this empty, an
[Orgmode] Re: Problem with 7.02 - org-capture-templates not set from init file
OK, I found the problem. In my emacs init file, further down I had: (require 'gnus-load) ;; for dev gnus (require 'message) (require 'bbdb) (require 'org-install) (require 'org-icalendar) (require 'org-mobile) ... Removing these requires results in working org and not stomping on org-capture-templates. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Problem with 7.02 - org-capture-templates not set from init file
Jeffrey DeLeo jeff.de...@rigpa.org writes: OK, I found the problem. In my emacs init file, further down I had: (require 'gnus-load) ;; for dev gnus (require 'message) (require 'bbdb) (require 'org-install) (require 'org-icalendar) (require 'org-mobile) ... Removing these requires results in working org and not stomping on org-capture-templates. I am somewhat confused here. Why would removal of the `require' statements fix the problem? Should we not *have* (require 'org-install) in order to have the latest org-mode be activated and loaded? Actually, I am having the same problem here after upgrading to 7.02. Hitting C-cc does run `org-capture' correctly, but the value of `org-capture-templates' (which was set using the customize interface, and has been saved to a separate emacs-custom.el file) does not have the set value. Using C-h v on `org-capture-templates', I get: , | org-capture-templates is a variable defined in `org-capture.el'. | Its value is nil | | Documentation: | Templates for the creation of new entries. ` Specifically, the value of this variable remains as `nil', and attempting to view the value via `customize-variable' returns a state of CHANGED outside Customize. However, the actual value is empty. , | Org Capture Templates: | INS | State: CHANGED outside Customize; operating on it here may be unreliable. | Templates for the creation of new entries. ` I am running GNU Emacs 23.2.50 and org-version does confirm org-7.02. BTW, whats with the org-7.3 on http://orgmode.org? Regards, -- Anupam Sengupta ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
