Hi Seb,
Sébastien Vauban writes:
[...]
>
> Simply perfect!
>
> The only impact is that we cannot expect a multi-line block to be correctly
> exported in the following case:
>
> -- set flag
> UPDATE dossier
> SET DossierSentToSector = @now
> WHERE ID
> IN (SELECT actID_fk
> FROM action
Hi Eric,
"Eric Schulte" wrote:
>> Sébastien Vauban writes:
>>>
>>> In fact, a better specification is: copy whatever (any character) is in
>>> front of `<<>>' in front of every line of the referenced block
>>> (same amount of characters, be it spaces or something else).
>>>
>>> That way, a commen
I just pushed up a commit which should implement your idea mentioned
below.
Please try it out and let me know if it doesn't work as expected.
Best -- Eric
"Eric Schulte" writes:
> Hi Sébastien,
>
> Sébastien Vauban writes:
> [...]
>>
>> In fact, a better specification is: copy whatever (any c
Hi Sébastien,
Sébastien Vauban writes:
[...]
>
> In fact, a better specification is: copy whatever (any character) is in front
> 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
Hi Eric,
Sébastien 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.
>
> [.
Hi Eric,
"Eric Schulte" wrote:
> Sébastien Vauban writes:
>> "Eric Schulte" wrote:
>>> Sébastien Vauban 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
Sébastien Vauban writes:
> Hi Eric,
>
> "Eric Schulte" wrote:
>> Sébastien Vauban 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 white
Hi Dan,
Dan Davison wrote:
> "Eric Schulte" writes:
>> Sébastien Vauban writes:
>>
>>> Here the "problems" (details, though) I've observed:
>>>
>>> - *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")
Hi Eric,
"Eric Schulte" wrote:
> Sébastien Vauban 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 st
