From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?S=C3=A9bastien_Vauban?= Subject: Re: [babel] Tiny "problems" Date: Thu, 17 Dec 2009 15:24:25 +0100 Message-ID: <87vdg5lluu.fsf@mundaneum.com> References: <87vdgpzf9i.fsf@mundaneum.com> <87ocmbyu57.fsf@mundaneum.com> <87zl5im0mb.fsf@mundaneum.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Hi Eric, S=C3=A9bastien Vauban wrote: > "Eric Schulte" wrote: >> >> [...] >> >> 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. > > [...] > > So, the only solution would be to indent the inserted block by the number= of > spaces in front of the `<<>>' sequence. Will be interested hav= ing > that fixed, even if that's (only) medium priority. In fact, a better specification is: copy whatever (any character) is in fro= nt of `<<>>' in front of every line of the referenced block (same amount of characters, be it spaces or something else). That way, a commented SQL source block like the following would be correctly outputted: --8<---------------cut here---------------start------------->8--- -- -- set flag -- UPDATE dossier -- SET DossierSentToSector =3D @now -- WHERE ID -- IN (SELECT actID_fk -- FROM actions -- WHERE (actID =3D 338 AND actEtat =3D 3)) -- AND F1SignDate < @firstDayOfThisMonth -- AND DossierSentToSector IS NULL -- AND -- <> --8<---------------cut here---------------end--------------->8--- Currently, the first line of the "condition" block is commented, the others not, resulting in incorrect code being tangled. With the above "spec", I guess all cases are covered. What do you think? Best regards, Seb --=20 S=C3=A9bastien 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