emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo)
To: emacs-orgmode@gnu.org
Subject: [PATCH] org.texi: Fix typo
Date: Tue, 25 Aug 2015 15:23:24 -0400	[thread overview]
Message-ID: <87bndvp3yr.fsf@yale.edu> (raw)

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

Hi, I think that the correct option for the comments header 
argument is "link" not "links".

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-org.texi-Fix-typo.patch --]
[-- Type: text/x-diff, Size: 1039 bytes --]

From bb7824dfab8dc2855a6f02d49f271b63ec251cfc Mon Sep 17 00:00:00 2001
From: "Jorge A. Alfaro Murillo" <jorge.alfaro-murillo@yale.edu>
Date: Tue, 25 Aug 2015 15:12:43 -0400
Subject: [PATCH] org.texi: Fix typo

* doc/org.texi (Extracting source code): Fix typo.
---
 doc/org.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/org.texi b/doc/org.texi
index 7818d18..ed808be 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -14950,7 +14950,7 @@ The @code{org-babel-tangle-jump-to-org} function provides this jumping from
 code to Org-mode functionality.  Two header arguments are required for
 jumping to work, first the @code{padline} (@ref{padline}) option must be set
 to true (the default setting), second the @code{comments} (@ref{comments})
-header argument must be set to @code{links}, which will insert comments into
+header argument must be set to @code{link}, which will insert comments into
 the source code buffer which point back to the original Org-mode file.
 
 @node Evaluating code blocks
-- 
2.5.0


[-- Attachment #3: Type: text/plain, Size: 20 bytes --]


Best,
-- 
Jorge. 


             reply	other threads:[~2015-08-25 19:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25 19:23 Jorge A. Alfaro-Murillo [this message]
2015-08-27 18:56 ` [PATCH] org.texi: Fix typo Nicolas Goaziou

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=87bndvp3yr.fsf@yale.edu \
    --to=jorge.alfaro-murillo@yale.edu \
    --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).