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: Mon, 07 Dec 2009 11:07:32 +0100	[thread overview]
Message-ID: <87ocmbyu57.fsf@mundaneum.com> (raw)
In-Reply-To: m2hbs6gfhc.fsf@gmail.com

Hi Eric,

"Eric Schulte" wrote:
> Sébastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>>
>> - srcname must be in column 0 for the highlighting to be correct.
>
> The syntax highlighting is really just org-mode comment highlighting,
> and I don't know that it would be desirable to start highlighting
> comments which don't start at the beginning of a line.
>
> Maybe once babel is able to recognize #+source: and #+results: lines
> which don't start at column 0 -- currently it doesn't -- then it would
> make sense from a babel perspective to put some pressure on the syntax
> coloring.

Since version 6.30 or so, comments and code blocks are correctly highlighted
when starting in columns others than 0.

I'm using that feature since then, so that my code is indented accordingly to
its position in the text.


>> - *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:

>> -- no longer display the count message
>> SET NOCOUNT ON
>>
>> SELECT TOP 10
>>        etpNom,
>>        etpID,
>> FROM etp
>> WHERE etpID
>>     IN (SELECT actID
>>         FROM actions
>>         WHERE actID = 338)
>>     AND
>>     -- extra condition                                   << OK
>> pfiAuth = 1                                              << not
>> AND SUBSTRING(etpCPNum, 1, 3) = "111"                    << not
>> ORDER BY pfiID
>> -- CP111.sql ends here

Thanks anyway!

Best regards,
  Seb

-- 
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

  parent reply	other threads:[~2009-12-07 10:07 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 [this message]
2009-12-16 21:17     ` Eric Schulte
2009-12-17  9:05       ` Sébastien Vauban
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=87ocmbyu57.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).