Hi Sébastien,
"Sebastien Vauban" writes:
> Hi Bastien,
>
> "Sebastien Vauban" wrote:
>>> You can also go back to the *Messages* buffer and check from there.
>>>
>>> Maybe another option is to silent `org-id-update-id-locations' when called
>>> from `org-id-find'? Does the attached patch against
"Sebastien Vauban"
writes:
> That said, I still find we should be able to refer to tables names whose
> TBLNAME keyword could be spelled both:
>
> - in downcase version (#+tblname: abc) and
> - in uppercase version (#+TBLNAME: xyz).
This should be doable -- please test this patch:
http://patch
Hello,
"Sebastien Vauban"
writes:
> That said, I still find we should be able to refer to tables names whose
> TBLNAME keyword could be spelled both:
>
> - in downcase version (#+tblname: abc) and
> - in uppercase version (#+TBLNAME: xyz).
More importantly, we should also be able to refer to
Hi Bastien,
"Sebastien Vauban" wrote:
>> You can also go back to the *Messages* buffer and check from there.
>>
>> Maybe another option is to silent `org-id-update-id-locations' when called
>> from `org-id-find'? Does the attached patch against master improves the
>> situation for you?
>
> In all
Hi Bastien,
Bastien wrote:
> "Sebastien Vauban" writes:
>
>>> (I don't like using sit-for, it's often worse than getting an error...)
>>
>> I don't like it that much either, but, here, it's the only way to see the
>> message before being flooded by the "Finding ID location..." messages.
>
> You c
Hi Sébastien,
"Sebastien Vauban" writes:
>> (I don't like using sit-for, it's often worse than getting an error...)
>
> I don't like it that much either, but, here, it's the only way to see the
> message before being flooded by the "Finding ID location..." messages.
You can also go back to the
Hi Bastien,
Bastien wrote:
> thanks for the patch.
>
> I wonder if we should trigger an error instead -- why a message?
Because it's not an error... When a reference (I guess it always must be an
ID, then) is not found locally, Org will search for it in external known
files.
The problem is you s
Hi Sébastien,
thanks for the patch.
I wonder if we should trigger an error instead -- why a message?
(I don't like using sit-for, it's often worse than getting an error...)
About the patch itself, thanks for the effort in adding a ChangeLog,
it's close to perfect: just think of starting sentenc
2012-04-05 Sebastien Vauban
* org-table.el (org-table-get-remote-range): when a reference to a
remote table is not found locally, display a message for 1 second,
then go on searching within all known locations
>From 432a57390d8a103d440017664b8a594de61281a4 Mon Sep 1