emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [babel] Tiny "problems"
Date: Thu, 17 Dec 2009 10:05:32 +0100	[thread overview]
Message-ID: <87zl5im0mb.fsf@mundaneum.com> (raw)
In-Reply-To: m2hbrq4o11.fsf@gmail.com

Hi Eric,

"Eric Schulte" wrote:
> Sébastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>> "Eric Schulte" wrote:
>>> Sébastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>
> [...]
>
>>>> - *after* =C-c '= forth and back, all the blank lines in my source block
>>>>   (in my example, the one between "SET NOCOUNT ON" and "SELECT TOP 10")
>>>>   are filled with an amount of whitespaces (and, in my Emacs config,
>>>>   highlighted as useless spaces).
>>>>
>>>> - the condition block is not indented properly in the tangled output
>>>>   file; only the first line is:
>>>>
>>>
>>> Maybe the above two issues could be fixed by setting the
>>> `org-src-preserve-indentation' variable's value to t. Since I only need
>>> this in some org-mode buffers I set it as a buffer local variable by
>>> placing a line like the following at the top of these buffers.
>>>
>>> # -*- org-src-preserve-indentation: t -*-
>>>
>>> again this should/will be in the documentation somewhere...
>>
>> That's not it (already tried before posting). That variable, when set,
>> makes Org removes the minimum common number of whitespaces.
>>
>> That does not fix the problem of useless whitespaces in blank lines, and
>> has no impact on the indentation of tangled blocks:
>
> I misunderstood your indentation issue earlier. Currently I don't think we
> support indentation to the level of the noweb reference in the original
> source-code block. At first glance that does however seem to be a better
> default behavior. I'll look into this. As a work-around you may want to try
> the attached version of your file
>
> [...]
>
> which results in this following sql file
>
> [...]

It indeed could be some sort of workaround. Though, the first line remains
badly placed according to all the other lines of the source block...

So, the only solution would be to indent the inserted block by the number of
spaces in front of the `<<<code here>>>' sequence. Will be interested having
that fixed, even if that's (only) medium priority.

Best regards,
  Seb

PS- Did you take a look at the comparison I made between Org and Nuweb (with
    the results in PDF)?

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2009-12-17  9:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02 13:17 [babel] Tiny "problems" Sébastien Vauban
2009-12-05  5:24 ` Eric Schulte
2009-12-05 17:57   ` Dan Davison
2009-12-07 10:10     ` Sébastien Vauban
2009-12-07 10:07   ` Sébastien Vauban
2009-12-16 21:17     ` Eric Schulte
2009-12-17  9:05       ` Sébastien Vauban [this message]
2009-12-17 14:24         ` Sébastien Vauban
2009-12-17 16:58           ` Eric Schulte
2009-12-17 18:23             ` Eric Schulte
2009-12-18  9:12               ` Sébastien Vauban
2009-12-18 18:48                 ` Eric Schulte

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=87zl5im0mb.fsf@mundaneum.com \
    --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).