From: Ian Kelling <ian@iankelling.org>
To: emacs-orgmode@gnu.org
Subject: bug: in source block, titles are not seen as source
Date: Tue, 27 May 2014 21:13:11 -0700 [thread overview]
Message-ID: <87lhtm7d7s.fsf@treetowl.lan> (raw)
I've had this bug me a few times when I work with here documents in bash.
#+begin_src sh
some-command <<'EOF'
* some text
EOF
#+end_src
the line beginning with * is treated as a title and folded. The same
goes for example blocks, and perhaps other things.
as a workaround, I can insert a tab char, and change the redirection
operator to <<- to strip leading tabs
some-command <<-'EOF'
* some text
EOF
- Ian
next reply other threads:[~2014-05-28 4:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 4:13 Ian Kelling [this message]
2014-05-28 7:02 ` bug: in source block, titles are not seen as source Albert Krewinkel
2014-05-28 14:52 ` Ian Kelling
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=87lhtm7d7s.fsf@treetowl.lan \
--to=ian@iankelling.org \
--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).