From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Change in org-babel with indenting code blocks?
Date: Tue, 30 Aug 2011 08:40:10 +0200 [thread overview]
Message-ID: <80aaarxv05.fsf@somewhere.org> (raw)
In-Reply-To: m2k49w53m2.fsf@gmail.com
Hi John,
John Wiegley wrote:
> I don't have any org-babel variables customized. I have a code block like
> this:
>
> *** NOTE Assets:Receivable:CEG
> #+begin_src sh :results value :exports results
> ledger reg --inject=Expected '^income:ceg'
> ledger reg --sort date -b 2007 receivable:CEG
> #+end_src
> :PROPERTIES:
> :ID: 8BEF6C42-8B23-495B-9421-3810B58907A1
> :VISIBILITY: folded
> :CREATED: [2010-06-18 Fri 07:37]
> :END:
>
> When I put my cursor on the '*' in the heading and hit 'r', I was used to
> the whole entry, including the code block, getting indented by one space.
> Now everything *but* the code block gets indented.
>
> Is this new behavior? How do I get back to the old behavior? I don't want my
> code blocks sticking to a fixed column.
Could it be due to the patch around "Extra space inserted in repeated tasks'
date line"?
See http://lists.gnu.org/archive/html/emacs-orgmode/2011-08/msg00634.html
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2011-08-30 6:40 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 [this message]
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
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=80aaarxv05.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).