emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bastien <bzg@altern.org>
Cc: Jason Dunsmore <emacs-orgmode@dunsmor.com>,
	Org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: [bug] Asterisks in source and example blocks interpreted as headings
Date: Thu, 25 Aug 2011 15:31:52 +0200	[thread overview]
Message-ID: <3B054A88-1404-4C9D-BD55-9AF181C497A0@gmail.com> (raw)
In-Reply-To: <87zkix62pj.fsf@gnu.org>


On Aug 25, 2011, at 3:27 PM, Bastien wrote:

> Hi Jason,
> 
> Jason Dunsmore <emacs-orgmode@dunsmor.com> writes:
> 
>> Bastien <bzg@altern.org> writes:
>> 
>>> Hi Jason,
>>> 
>>> Jason Dunsmore <emacs-orgmode@dunsmor.com> writes:
>>> 
>>>> I noticed that lines with leading asterisks inside of source and example
>>>> blocks are interpreted as headings:
>>> 
>>> The attached patch should fix this -- please confirm.
>> 
>> Hm, I'm still seeing the same issue with both source and example
>> blocks.
> 
> Yes -- my patch only took care of not allowing *manually* folding
> headlines in selected environments.  But those headlines were still
> folded when finding an org file with "#+STARTUP: fold" in it.
> 
> In the meantime, is it okay for you to TAB and have the commas
> automatically added, as Sébastien suggested?


This requires

(setq org-src-tab-acts-natively t)

- Caraten


> 
> -- 
> Bastien
> 

- Carsten

  reply	other threads:[~2011-08-25 13:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-16 18:27 [bug] Asterisks in source and example blocks interpreted as headings Jason Dunsmore
2011-08-16 19:51 ` Bastien
2011-08-16 20:22   ` Jason Dunsmore
2011-08-25 13:27     ` Bastien
2011-08-25 13:31       ` Carsten Dominik [this message]
2011-08-31 19:52       ` Jason Dunsmore
2011-08-17 11:05 ` Daniel Bausch
2011-08-19 12:19   ` Eric Schulte
2011-08-19 19:53     ` Sebastien Vauban

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=3B054A88-1404-4C9D-BD55-9AF181C497A0@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@dunsmor.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).