Re: [PATCH] ob-core: Avoid table conversion warning for empty results

[Kyle Meyer]

Colin Baxter writes:

> >> This patch would squelch the inappropriate warning you report
> >> while not hiding other warnings.
>
> > Thank you. I'll apply the patch to my org-mode and report back.
>
> I have now applied the patch to my local org-mode git repository and it
> works with no reported errors. Thanks again.

Thanks for trying it out.  Applied (7bc18ebbe).

Re: [PATCH] ob-core: Avoid table conversion warning for empty results

[Colin Baxter]

Dear Kyle,

> Kyle Meyer  writes:

>> Kyle Meyer writes:
>>> Thanks for reporting.  The _display_ of this warning starts with
>>> my 14878f3f9 (ob-core: Display warning on failure to read
>>> results, 2020-05-21).  Here's the associated thread on the
>>> mailing list:
>>> .
>>> 
>>> On that commit's parent (eecee2266), the error is triggered and
>>> caught in the same way, but "Error reading results:
>>> (beginning-of-buffer)" is buried in the messages buffer rather
>>> than being displayed as a warning.
>>> 
>>> I'll need to take a closer look at what's going on, though I
>>> wouldn't be surprised if it's been around for a long time.

>> This patch would squelch the inappropriate warning you report
>> while not hiding other warnings.

> Thank you. I'll apply the patch to my org-mode and report back.

I have now applied the patch to my local org-mode git repository and it
works with no reported errors. Thanks again.

Best wishes,

Colin Baxter.


Colin Baxter
URL: http://www.Colin-Baxter.com
-
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8
-

Re: [PATCH] ob-core: Avoid table conversion warning for empty results

[Colin Baxter]

Dear Kyle,

> Kyle Meyer  writes:

> Kyle Meyer writes:
>> Thanks for reporting.  The _display_ of this warning starts with
>> my 14878f3f9 (ob-core: Display warning on failure to read
>> results, 2020-05-21).  Here's the associated thread on the
>> mailing list:
>> .
>> 
>> On that commit's parent (eecee2266), the error is triggered and
>> caught in the same way, but "Error reading results:
>> (beginning-of-buffer)" is buried in the messages buffer rather
>> than being displayed as a warning.
>> 
>> I'll need to take a closer look at what's going on, though I
>> wouldn't be surprised if it's been around for a long time.

> This patch would squelch the inappropriate warning you report
> while not hiding other warnings.

Thank you. I'll apply the patch to my org-mode and report back.

Best wishes,

Colin Baxter.