emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Leo Vivier <leo.vivier+dev@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [PATCH] org: Update example in docstring to accommodate new name and new format
Date: Mon, 20 Jul 2020 22:23:58 +0200	[thread overview]
Message-ID: <87ft9mgckh.fsf@hidden> (raw)

[-- Attachment #1: Type: text/plain, Size: 242 bytes --]

Hi there,

I’ve spotted an example in a docstring that wasn’t updated when the
command was renamed and moved to another file in

I took the liberty to update it.


Leo Vivier

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-org-Update-docstring.patch --]
[-- Type: text/x-patch, Size: 822 bytes --]

From 83dde9d0735cc6223233aa18c938a4ae14b4c88c Mon Sep 17 00:00:00 2001
From: Leo Vivier <leo.vivier+dev@gmail.com>
Date: Mon, 20 Jul 2020 22:11:15 +0200
Subject: [PATCH] org: Update docstring

* lisp/org.el (org-find-olp): Update example in docstring to
accommodate new name and new format
 lisp/org.el | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lisp/org.el b/lisp/org.el
index 12a853bd6..5900e692a 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -13501,7 +13501,7 @@ If anything goes wrong, throw an error.
 You can wrap this call to catch the error like this:
   (condition-case msg
-      (org-mobile-locate-entry (match-string 4))
+      (org-find-olp (list (match-string 4) t)
     (error (nth 1 msg)))
 The return value will then be either a string with the error message,

             reply	other threads:[~2020-07-20 20:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20 20:23 Leo Vivier [this message]
2020-07-21  5:41 ` [PATCH] org: Update example in docstring to accommodate new name and new format Leo Vivier
2020-07-22  4:27 ` Kyle Meyer
2020-07-22  6:43   ` Leo Vivier
2020-07-23  3:40     ` Kyle Meyer
2020-07-23  5:48       ` Leo Vivier
2020-07-23 23:27         ` Kyle Meyer

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:

  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=87ft9mgckh.fsf@hidden \
    --to=leo.vivier+dev@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).