emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: John Wiegley <jwiegley@gmail.com>
Cc: emacs-orgmode@gnu.org, nicholas.dokos@hp.com,
	Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: Change in org-babel with indenting code blocks?
Date: Fri, 09 Sep 2011 19:49:03 +0200	[thread overview]
Message-ID: <8739g57gj4.fsf@gnu.org> (raw)
In-Reply-To: <m2sjo64m8h.fsf@gmail.com> (John Wiegley's message of "Thu, 08 Sep 2011 19:01:50 -0500")

Hi John,

John Wiegley <jwiegley@gmail.com> writes:

>>>>>> John Wiegley <jwiegley@gmail.com> writes:
>
>> In the current Org (updated today), this problem now affects *all*
>> non-drawer text in entries, including code blocks, lists, and log entries!
>> This is makes entry shifting completely useless to me.  What do I need to
>> revert to make it work again?
>
> Actually, it even worse: This affects all refiled blocks as well, resulting in
> the indentation of the refiled entry being the same as the original level it
> was captured in.  I just went through my entire Org file by eye and found a
> huge number of indentation problems resulting from this bug.  Help!

I couldn't fix this correctly, so I simply reverted commit 6b04bef for
now.  I will provide a better fix later.

Thanks,

-- 
 Bastien

      parent reply	other threads:[~2011-09-09 17:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-29 21:07 Change in org-babel with indenting code blocks? John Wiegley
2011-08-30  6:40 ` Sebastien Vauban
2011-08-30 20:25 ` Nicolas Goaziou
2011-08-31  2:25   ` John Wiegley
2011-08-31  7:38     ` Nicolas Goaziou
2011-08-31  8:02       ` Nick Dokos
2011-08-31 15:57         ` John Wiegley
2011-08-31 16:32           ` Nick Dokos
2011-09-08 23:54         ` John Wiegley
2011-09-09  0:01           ` John Wiegley
2011-09-09  6:04             ` Bastien
2011-09-09  6:17               ` John Wiegley
2011-09-09 17:49             ` Bastien [this message]

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=8739g57gj4.fsf@gnu.org \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=jwiegley@gmail.com \
    --cc=n.goaziou@gmail.com \
    --cc=nicholas.dokos@hp.com \
    /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).