From: Seamus Tuohy <s2e.lists@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Bugs in org-babel "comments org" property blank spaces and links
Date: Mon, 10 Aug 2015 09:00:27 -0400 [thread overview]
Message-ID: <CAGyxsyjyc8ZKYXEgpnMw2_L-8-Dz57mRYtH_VHmVkvGEQJQx-Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1683 bytes --]
Hello All,
I have encountered what I believe to be two bugs in the way that org-babel
handles exporting using the org based comments.
I am running on Org-mode version 8.3.1 ( 8.3.1-elpaplus ) as pulled from
Cask.
The first is a bug is related to the handling of commenting links. When
links are commented the entire link is not commented. Only the text is
commented. This creates an uncommented string in the source code. Here is
an example.
---source.org---
#+PROPERTY: comments org
** [[http://orgmode.org/][Header links are broken on export]]
[[http://orgmode.org/][Inline links are broken on export]]
---output.el---
[[http://orgmode.org/][;; Header links are broken on export]]
[[http://orgmode.org/][;; Inline links are broken on export]]
------
The second bug causes an error to occur when exporting source blocks that
do not text between them.
---source.org---
#+BEGIN_SRC emacs-lisp
(message "Inline blocks that have no text between them are broken as well.")
#+END_SRC
#+BEGIN_SRC emacs-lisp
(message "I am broken.")
#+END_SRC
---output.el---
(message "Inline blocks that have no text between them are broken as well.")
------
When toggle-debug-on-error is set the following error occurs.
---*Backtrace*---
Debugger entered--Lisp error: (error "Nothing to comment")
signal(error ("Nothing to comment"))
error("Nothing to comment")
comment-region-default(1 3 nil)
comment-region(1 3)
....................
org-babel-spec-to-string((
........................
org-babel-tangle(nil)
----
I have put some files I have used to reproduce the bug at the following
gist.
https://gist.github.com/elationfoundation/0238ecb4e26730bdbab1
Best,
s2e
[-- Attachment #2: Type: text/html, Size: 2266 bytes --]
reply other threads:[~2015-08-10 13:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAGyxsyjyc8ZKYXEgpnMw2_L-8-Dz57mRYtH_VHmVkvGEQJQx-Q@mail.gmail.com \
--to=s2e.lists@gmail.com \
--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).