Re: [PATCH] Fix typos
Stefan Kangas writes: > Please see the attached. Thanks! Applied onto main via 41e19f1d7. Best, Ihor
[PATCH] Fix typos
Please see the attached. From 5ecf4e9613993a520844b78880bf57c04f193880 Mon Sep 17 00:00:00 2001 From: Stefan Kangas Date: Thu, 30 Jun 2022 17:33:03 +0200 Subject: [PATCH] ; Fix typos --- lisp/org-element.el | 14 +++--- lisp/org-fold-core.el| 10 +- lisp/org-persist.el | 14 +++--- lisp/org-src.el | 2 +- lisp/org.el | 2 +- lisp/ox-latex.el | 12 ++-- lisp/ox-texinfo.el | 2 +- testing/lisp/test-org-element.el | 2 +- testing/lisp/test-ox-publish.el | 2 +- 9 files changed, 30 insertions(+), 30 deletions(-) diff --git a/lisp/org-element.el b/lisp/org-element.el index 2a826bdbb..8964770f0 100644 --- a/lisp/org-element.el +++ b/lisp/org-element.el @@ -700,7 +700,7 @@ is cleared and contents are removed in the process." ;; DATUM is i.e. a headline, it's property list (`:title' ;; in case of headline) can contain parsed objects. The ;; objects will contain `:parent' property set to the DATUM - ;; iteself. When copied, these inner `:parent' propery + ;; itself. When copied, these inner `:parent' propery ;; values will contain incorrect object decoupled from ;; DATUM. Changes to the DATUM copy will not longer be ;; reflected in the `:parent' properties. So, we need to @@ -1289,7 +1289,7 @@ parser (e.g. `:end' and :END:). Return value is a plist." (category (catch 'buffer-category (unless org-element-org-data-parser--recurse (org-with-point-at end - ;; Avoid recusrive calls from + ;; Avoid recursive calls from ;; `org-element-at-point-no-context'. (let ((org-element-org-data-parser--recurse t)) (while (re-search-backward "^[ \t]*#\\+CATEGORY:" (point-min) t) @@ -6092,7 +6092,7 @@ completing the request." (log org-element--cache-size 2)) (org-element-cache-reset) (throw 'org-element--cache-quit t))) - ;; Done deleting everthing starting before END. + ;; Done deleting everything starting before END. ;; DATA-KEY is the first known element after END. ;; Move on to phase 1. (org-element--cache-log-message @@ -6664,7 +6664,7 @@ The function returns the new value of `org-element--cache-change-warning'." ;; `org-element--cache-submit-request'). After the edit, we want to ;; look if there was a sensitive removed during edit. ;; FIXME: This is not the most efficient way and we now - ;; have to delete more elemetns than needed in some + ;; have to delete more elements than needed in some ;; cases. A better approach may be storing the warning ;; in the modification request itself. (let ((org-element--cache-change-warning-before org-element--cache-change-warning) @@ -6748,7 +6748,7 @@ that range. See `after-change-functions' for more information." "This variable controls how buffer changes are handled by the cache. By default (when this variable is nil), cache re-parses modified -headlines immidiately after modification preserving all the unaffected +headlines immediately after modification preserving all the unaffected elements inside the headline. The default behaviour works best when users types inside Org buffer of @@ -6870,7 +6870,7 @@ known element in cache (it may start after END)." ;; costly. Instead, we should better re-parse only the ;; headline itself when possible. If a headline is still ;; starting from old :begin position, we do not care that - ;; its boundaries could have extended to shrinked - we + ;; its boundaries could have extended to shrunk - we ;; will re-parent and shift them anyway. (and (eq 'headline (org-element-type up)) (not org-element--cache-avoid-synchronous-headline-re-parsing) @@ -7154,7 +7154,7 @@ The element is: %S\n The real element is: %S\n Cache around :begin:\n%S\n%S\n%S" (cdr (org-element--cache-find (org-element-property :begin real-element) 'both))) (org-element-cache-reset)) -;;; Cache persistance +;;; Cache persistence (defun org-element--cache-persist-before-write (container associated) "Sync cache before saving." diff --git a/lisp/org-fold-core.el b/lisp/org-fold-core.el index 68a777de9..212fa09a8 100644 --- a/lisp/o
Re: [PATCH] Fix typos
Kyle Meyer writes: > Jonas Bernoulli writes: > >> Please consider applying the below patch, which fixes many spelling >> errors. > > Eh, there's some good ones in there. I wish I could say that having a typo in the first sentence of the reply was intentional :/
Re: [PATCH] Fix typos
Jonas Bernoulli writes: > Please consider applying the below patch, which fixes many spelling > errors. Eh, there's some good ones in there. Applied. > In addition to the below typos I also found some things I don't know > how to deal with: > * "visibile" as a supported value of org-s5-control-visibility With a quick scan, I couldn't figure out what the best way to deal with that would be. It looks like org-s5--build-meta-info would put the value into a string as is, so it seems likely that the typo means it doesn't behave as intended. This is in contrib/, so I've added the original author in the cc in case he wants to take a closer look. > * "ded" appearing in doc/orgcard.tex I think that's a shortening of "dedicated", presumably to squeeze things into the card. Thanks.
[PATCH] Fix typos
Please consider applying the below patch, which fixes many spelling errors. I did not write a commit message that lists every file and function/variable that happened to contain a typo. That seems rather unnecessary for this type of change, but if you want that I can do it. In addition to the below typos I also found some things I don't know how to deal with: * "visibile" as a supported value of org-s5-control-visibility * "ded" appearing in doc/orgcard.tex Cheers, Jonas --- README_maintainer | 4 ++-- contrib/lisp/ob-oz.el | 2 +- contrib/lisp/ob-spice.el | 6 +++--- contrib/lisp/ol-notmuch.el| 6 +++--- contrib/lisp/org-annotate-file.el | 2 +- contrib/lisp/org-collector.el | 2 +- contrib/lisp/org-expiry.el| 2 +- contrib/lisp/org-mac-link.el | 2 +- contrib/lisp/org-passwords.el | 2 +- contrib/lisp/org-screenshot.el| 6 +++--- contrib/lisp/org-sudoku.el| 2 +- contrib/lisp/org-toc.el | 2 +- contrib/lisp/orgtbl-sqlinsert.el | 2 +- contrib/lisp/ox-deck.el | 16 contrib/lisp/ox-groff.el | 2 +- contrib/lisp/ox-koma-letter.el| 2 +- contrib/lisp/ox-s5.el | 4 ++-- contrib/scripts/StartOzServer.oz | 4 ++-- doc/.aspell.org.conf | 2 +- doc/doc-setup.org | 2 +- doc/org-guide.org | 2 +- doc/org-manual.org| 10 +- etc/ORG-NEWS | 26 +- lisp/ob-C.el | 6 +++--- lisp/org-agenda.el| 8 lisp/org-attach-git.el| 4 ++-- lisp/org-feed.el | 2 +- lisp/org-plot.el | 2 +- lisp/org-table.el | 2 +- lisp/org.el | 6 +++--- lisp/ox-odt.el| 6 +++--- mk/eldo.el| 2 +- testing/examples/ob-awk-test.org | 4 ++-- testing/lisp/test-ob-sqlite.el| 2 +- testing/lisp/test-org-agenda.el | 2 +- testing/lisp/test-org-attach.el | 2 +- testing/lisp/test-org.el | 8 37 files changed, 83 insertions(+), 83 deletions(-) diff --git a/README_maintainer b/README_maintainer index a5eda1caf..d2e9ada50 100644 --- a/README_maintainer +++ b/README_maintainer @@ -42,7 +42,7 @@ The release number for minor releases look like this: =9.1.7= Minor releases are small amends to main releases. Usually they fix critical bugs discovered in a main release. Minor bugs are usually -not fixed -- they will be adressed in the next main release. +not fixed -- they will be addressed in the next main release. Only the fix to the bug is bundled into a release, without the main development work going on in the master branch. Since the bug fix @@ -194,7 +194,7 @@ The list of all contributors from who we have the papers is kept on Worg at https://orgmode.org/worg/org-contribute.html, so that committers can check if a patch can go into the core. -The assignment process does not allways go smoothly, and it has +The assignment process does not always go smoothly, and it has happened several times that it gets stuck or forgotten at the FSF. The contact at the FSF for this is: mailto:copyright-cl...@fsf.org diff --git a/contrib/lisp/ob-oz.el b/contrib/lisp/ob-oz.el index 626c4f316..46bf536f7 100644 --- a/contrib/lisp/ob-oz.el +++ b/contrib/lisp/ob-oz.el @@ -106,7 +106,7 @@ (require 'mozart nil t) ;; back any results from Oz to Emacs. The following code creates a ;; socket for sending code to the OPI compiler and results are ;; returned by the same socket. On the Oz side, a socket is opened and -;; conected to the compiler of the OPI (via oz-send-string). On the +;; connected to the compiler of the OPI (via oz-send-string). On the ;; Emacs side, a connection to this socket is created for feeding code ;; and receiving results. This additional communication channel to the ;; OPI compiler ensures that results are returned cleanly (e.g., only diff --git a/contrib/lisp/ob-spice.el b/contrib/lisp/ob-spice.el index 24ef3c874..c452c993f 100644 --- a/contrib/lisp/ob-spice.el +++ b/contrib/lisp/ob-spice.el @@ -58,7 +58,7 @@ (defun org-babel-expand-body:spice (body params) (progn ;loop through the words (if (string-match "\\$\\(.*\\)\\[\\(.*\\)\\]" word) (progn - ;; if matchs a vector variable format + ;; if matches a vector variable format (setq varname (match-string 1 word)) (setq varindex (match-string 2 word)) ;; search varname in vars and use the value of varindex to word @@ -75,7 +75,7 @@ (defun org-babel-expand-body:spice (body params) ) ; end of (if (string-match "\\$\\(.*\\)\\[\\(.*\\)\\]" word)) (if (string-match "\\$\\(.*\\)\\." word) ; if variable has a dot in the end (progn -
Re: [O] [PATCH] Fix typos
Hi Adam, Adam Spiers orgm...@adamspiers.org writes: --- lisp/org-agenda.el |2 +- lisp/org-list.el |2 +- lisp/org.el|2 +- 3 files changed, 3 insertions(+), 3 deletions(-) Applied, thanks! -- Bastien
[O] [PATCH] Fix typos
--- lisp/org-agenda.el |2 +- lisp/org-list.el |2 +- lisp/org.el|2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el index 4efb332..7b4bc04 100644 --- a/lisp/org-agenda.el +++ b/lisp/org-agenda.el @@ -408,7 +408,7 @@ where desc A description string to be displayed in the dispatcher menu. cmdAn agenda command, similar to the above. However, tree commands - are no allowed, but instead you can get agenda and global todo list. + are not allowed, but instead you can get agenda and global todo list. So valid commands for a set are: (agenda \\ settings) (alltodo \\ settings) diff --git a/lisp/org-list.el b/lisp/org-list.el index 531cdd5..b865aed 100644 --- a/lisp/org-list.el +++ b/lisp/org-list.el @@ -207,7 +207,7 @@ Valid values are ?. and ?\). To get both terminators, use t. :group 'org-plain-lists :type '(choice (const :tag dot like in \2.\ ?.) (const :tag paren like in \2)\ ?\)) -(const :tab both t))) +(const :tag both t))) (defcustom org-alphabetical-lists nil Non-nil means single character alphabetical bullets are allowed. diff --git a/lisp/org.el b/lisp/org.el index 859748a..22d2208 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -6844,7 +6844,7 @@ This command works around this by showing a copy of the current buffer in an indirect buffer, in overview mode. You can dive into the tree in that copy, use org-occur and incremental search to find a location. When pressing RET or `Q', the command returns to the original buffer in -which the visibility is still unchanged. After RET is will also jump to +which the visibility is still unchanged. After RET it will also jump to the location selected in the indirect buffer and expose the headline hierarchy above. (interactive P) -- 1.7.8.206.g71406
[Orgmode] [PATCH] Fix typos in yasnippet conflict entry
Changed yasnippets to yasnippet and added extra whitespace around functions to be consistent with the rest of the section. --- doc/org.texi |4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/doc/org.texi b/doc/org.texi index 4d696ae..a30d5b6 100644 --- a/doc/org.texi +++ b/doc/org.texi @@ -13465,15 +13465,17 @@ fixed this problem: (define-key yas/keymap [tab] 'yas/next-field-group))) @end lisp -The latest version of yasnippets doesn't play well with Org mode. If the +The latest version of yasnippet doesn't play well with Org mode. If the above code does not fix the conflict, start by defining the following function: + @lisp (defun yas/org-very-safe-expand () (let ((yas/fallback-behavior 'return-nil)) (yas/expand))) @end lisp Then, tell Org mode what to do with the new function: + @lisp (add-hook 'org-mode-hook (lambda () -- 1.7.3.5 ___ 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
Re: [Orgmode] [PATCH] Fix typos in yasnippet conflict entry
Thanks for the patch. It has been applied. Jeffrey Horn jrhorn...@gmail.com writes: Changed yasnippets to yasnippet and added extra whitespace around functions to be consistent with the rest of the section. --- doc/org.texi |4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/doc/org.texi b/doc/org.texi index 4d696ae..a30d5b6 100644 --- a/doc/org.texi +++ b/doc/org.texi @@ -13465,15 +13465,17 @@ fixed this problem: (define-key yas/keymap [tab] 'yas/next-field-group))) @end lisp -The latest version of yasnippets doesn't play well with Org mode. If the +The latest version of yasnippet doesn't play well with Org mode. If the above code does not fix the conflict, start by defining the following function: + @lisp (defun yas/org-very-safe-expand () (let ((yas/fallback-behavior 'return-nil)) (yas/expand))) @end lisp Then, tell Org mode what to do with the new function: + @lisp (add-hook 'org-mode-hook (lambda () ___ 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: [PATCH] Fix typos.
applied, thanks. - Carsten On May 10, 2009, at 4:34 AM, Nick Dokos wrote: From a6eecc2b351e031bff53954772421979a4ae6e0a Mon Sep 17 00:00:00 2001 From: Nick Dokos nicholas.do...@hp.com Date: Sat, 9 May 2009 22:28:21 -0400 --- lisp/org-icalendar.el |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lisp/org-icalendar.el b/lisp/org-icalendar.el index 09ae69b..f07fd2f 100644 --- a/lisp/org-icalendar.el +++ b/lisp/org-icalendar.el @@ -137,7 +137,7 @@ or if they are only using it locally. (defcustom org-icalendar-timezone (getenv TZ) The time zone string for iCalendar export. -When nil of the empty string, use the abbreviation retrived from Emacs. +When nil or the empty string, use the abbreviation retrieved from Emacs. :group 'org-export-icalendar :type '(choice (const :tag Unspecified nil) -- 1.5.4.3 ___ 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
Re: [Orgmode] [PATCH] Fix typos.
Nick Dokos nicholas.do...@hp.com writes: From a6eecc2b351e031bff53954772421979a4ae6e0a Mon Sep 17 00:00:00 2001 From: Nick Dokos nicholas.do...@hp.com Date: Sat, 9 May 2009 22:28:21 -0400 --- lisp/org-icalendar.el |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lisp/org-icalendar.el b/lisp/org-icalendar.el index 09ae69b..f07fd2f 100644 --- a/lisp/org-icalendar.el +++ b/lisp/org-icalendar.el @@ -137,7 +137,7 @@ or if they are only using it locally. (defcustom org-icalendar-timezone (getenv TZ) The time zone string for iCalendar export. -When nil of the empty string, use the abbreviation retrived from Emacs. +When nil or the empty string, use the abbreviation retrieved from Emacs. :group 'org-export-icalendar :type '(choice (const :tag Unspecified nil) Just FYI, I added export TZ=Europe/Berlin to my .xsession (yeah I know wont work on non X machines), did a git pull and works great. Thanks. r. ___ 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
Re: [Orgmode] [PATCH] Fix typos.
Dokos, Nicholas nicholas.do...@hp.com wrote: o put environment variable definitions in a common file. o source the common file both in .xsessionrnc (takes care of display ^ That should be .xsessionrc ___ 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
Re: [Orgmode] [PATCH] Fix typos.
Richard Riley rileyrg...@googlemail.com wrote: Just FYI, I added export TZ=Europe/Berlin to my .xsession (yeah I know wont work on non X machines), did a git pull and works great. Also an FYI: as a consequence of this discussion, I have reorganized my startup files as follows: o put environment variable definitions in a common file. o source the common file both in .xsessionrnc (takes care of display managers and xinit/startx) and in .profile or .bash_profile (takes care of console or ssh logins). In my case, this results in setting the variables twice when I login through gdm, but I don't particularly care. Nick ___ 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
Re: [Orgmode] [PATCH] Fix typos.
Nick Dokos nicholas.do...@hp.com writes: Richard Riley rileyrg...@googlemail.com wrote: Just FYI, I added export TZ=Europe/Berlin to my .xsession (yeah I know wont work on non X machines), did a git pull and works great. Also an FYI: as a consequence of this discussion, I have reorganized my startup files as follows: o put environment variable definitions in a common file. o source the common file both in .xsessionrnc (takes care of display managers and xinit/startx) and in .profile or .bash_profile (takes care of console or ssh logins). In my case, this results in setting the variables twice when I login through gdm, but I don't particularly care. Nick heh, I know what you mean. It's kind of irritating though to set something twice and then also worry if the same thing will work on another distro. Still, TZ is a nice solution. If my anniversaries exported from my org files my blackberry iCal integration would be pretty much complete other than the obvious ability to update from the mobile device. ___ 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
Re: [Orgmode] [PATCH] Fix typos.
Nick Dokos nicholas.do...@hp.com writes: Richard Riley rileyrg...@googlemail.com wrote: Just FYI, I added export TZ=Europe/Berlin to my .xsession (yeah I know wont work on non X machines), did a git pull and works great. Also an FYI: as a consequence of this discussion, I have reorganized my startup files as follows: o put environment variable definitions in a common file. o source the common file both in .xsessionrnc (takes care of display managers and xinit/startx) and in .profile or .bash_profile (takes care of console or ssh logins). In my case, this results in setting the variables twice when I login through gdm, but I don't particularly care. Nick Just in support/alternatively: I has already moved it to .bash_login and the source ~/.bash_login in my ~/.xsession file. It's a bit of a round robin mess out there in Linux startup file land it seems. ___ 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
[Orgmode] [PATCH] Fix typos on website Changes documentation
- Fix minor grammar issues - Fix typos - Fix typo is variable name for example lisp code --- Carsten: This commit is available at git://git.norang.ca/org-mode in the branch fix-website-changelog -Bernt ORGWEBPAGE/Changes.org | 42 +- 1 files changed, 21 insertions(+), 21 deletions(-) diff --git a/ORGWEBPAGE/Changes.org b/ORGWEBPAGE/Changes.org index 5980861..6dcb05d 100644 --- a/ORGWEBPAGE/Changes.org +++ b/ORGWEBPAGE/Changes.org @@ -23,19 +23,19 @@ ** Details *** Yanking subtree with =C-y= now adjusts the tree level -When yanking a cut/copied subtree or a series of trees, even -the nomal yank key =C-y= does now adjust the level of the tree -to make it fit into the current outline position, without -loosing its identity, and without swallowing other subtrees. +When yanking a cut/copied subtree or a series of trees, the +normal yank key =C-y= now adjusts the level of the tree to +make it fit into the current outline position, without losing +its identity, and without swallowing other subtrees. This uses the command =org-past-subtree=. An additional -change in that command has been implemented: Normally, this +change in that command has been implemented: Normally, this command picks the right outline level from the surrounding -*visible* headlines, and uses the smaller on. So it the +*visible* headlines, and uses the smaller one. So if the cursor is between a level 4 and a level 3 headline, the tree -will be pasted as level 3. Now, if the cursor is actually -*at* the beginning of a headline, the level of that headline -will be used. So lets say you have a tree like this: +will be pasted as level 3. If the cursor is actually *at* +the beginning of a headline, the level of that headline will +be used. For example, lets say you have a tree like this: #+begin_src org ,* Level one @@ -48,7 +48,7 @@ insertion. When at (1), the tree will be pasted as level 2. When at (2), it will be pasted as level 1. -If you do not like =C-y= to behave like this, configure the +If you do not want =C-y= to behave like this, configure the variable =org-yank-adjusted-subtrees=. Thanks to Samuel Wales for this idea and a partial implementation. @@ -56,17 +56,17 @@ *** State changes can now be shown in the log mode in the agenda If you configure the variable =org-agenda-log-mode-items=, -you can now request that all logged state changes should also -show up in the agenda when log mode is active. If you find -this too much for normal applications, you can also -temporarily request the inclusion of state changes by -pressing =C-u l= in the agenda. +you can now request that all logged state changes be included +in the agenda when log mode is active. If you find this too +much for normal applications, you can also temporarily +request the inclusion of state changes by pressing =C-u l= in +the agenda. This was a request by Hsiu-Khuern Tang. *** Footnote in HTML export are now collected at the end of the document Previously, footnotes would be left in the document where -they are defined, bow that are all collected and put into a +they are defined, now they are all collected and put into a special =div= at the end of the document. Thanks to Sebastian Rose for this request. @@ -75,15 +75,15 @@ Thanks to Sebastian Rose for pushing this cleanup. -*** The clock can be now resumed after exiting and re-starting Emacs +*** The clock can now be resumed after exiting and re-starting Emacs -If the option =org-clock-resume= is t, and the first clock +If the option =org-clock-in-resume= is t, and the first clock line in an entry is unclosed, clocking into that task resumes the clock from that time. Thanks to James JD Smith for a patch to this effect. -*** Clock-related data can be saved and resumed accross Emacs sessions +*** Clock-related data can be saved and resumed across Emacs sessions The data saved include the contents of =org-clock-history=, and the running clock, if there is one. @@ -113,7 +113,7 @@ Inserting file links with =C-u C-c C-l= was buggy if the setting of `org-link-file-path-type' was `adaptive' (the -default). Absolute file path's were not abbreviated relative +default). Absolute file paths were not abbreviated relative to the users home directory. This bug has been fixed. Thanks to Matt Lundin for the report. @@ -130,7 +130,7 @@ Here is the setup you need: #+begin_src emacs-lisp -(setq org-ling-abbrev-alist '((att . org-attach-expand-link))) +(setq org-link-abbrev-alist '((att . org-attach-expand-link))) #+end_src After this, a link like this will work -- 1.6.0.3.523.g304d0 ___ Emacs-orgmode mailing
[Orgmode] [PATCH] Fix typos and minor grammar issues in the documentation
Cleanup the documentation for remember related functions. --- Carsten, I finally got around to redoing my remember setup and in the process I went through the description of variables and functions and found some items which I tried to improve. I'm now have templates for each org file I use and will try to file (via remember) to the correct org file up front so I can try org-refile next :) Hope this helps, Bernt org.el | 10 +- 1 files changed, 5 insertions(+), 5 deletions(-) diff --git a/org.el b/org.el index a674b6f..3136d1b 100644 --- a/org.el +++ b/org.el @@ -1423,9 +1423,9 @@ You can set this on a per-template basis with the variable Templates for the creation of remember buffers. When nil, just let remember make the buffer. When not nil, this is a list of 5-element lists. In each entry, the first -element is a the name of the template, It should be a single short word. +element is the name of the template which should be a single short word. The second element is a character, a unique key to select this template. -The third element is the template. The forth element is optional and can +The third element is the template. The fourth element is optional and can specify a destination file for remember items created with this template. The default file is given by `org-default-notes-file'. An optional fifth element can specify the headline in that file that should be offered @@ -13472,12 +13472,12 @@ If there is an active region, make sure remember uses it as initial content of the remember buffer. When called interactively with a `C-u' prefix argument GOTO, don't remember -anything, just go to the file/headline where the selected templated usually -stores its notes. With a double prefix arg `C-u C-u', got to the last +anything, just go to the file/headline where the selected template usually +stores its notes. With a double prefix arg `C-u C-u', go to the last note stored by remember. Lisp programs can set ORG-FORCE-REMEMBER-TEMPLATE-CHAR to a character -associated with a template in `org-remember-tempates'. +associated with a template in `org-remember-templates'. (interactive P) (cond ((equal goto '(4)) (org-go-to-remember-target)) -- 1.5.4.rc3 ___ 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
