i think those are c++ commands.
On 24 mars 2012, at 16:00, Miguel de Benito Delgado <m.debenit...@gmail.com>
wrote:
> Yes I have, although wrongly:
>
> as_string (call ("procedure-source", obj))
>
> I realized what I wanted was again
>
> object_to_string (call ("procedure-source", obj))
>
> And now I see thinks like:
>
> ((lambda () (exec-delayed cmd)))
>
> Which aren't of any help... :,-(
>
> I'll try to find another way of getting what I want, thanks.
>
> Cheers,
> Miguel.
>
> Gubinelli Massimiliano wrote:
>> have you tried to call procedure-source? I think that most of them will be
>> unreadable since generated by some macro code. there is always at least one
>> delayed command in the queue which is the one performing the autosave for
>> the current buffer.
>>
>> best
>> max
>>
>>
>> On 24 mars 2012, at 15:07, Miguel de Benito Delgado wrote:
>>
>>> Hi,
>>>
>>> I'm trying to debug an insidious bug related to the execution of delayed
>>> commands (exec_pending_commands()) and I want to know what those commands
>>> are. Inside object_command_rep::apply() I'd like to add something like
>>>
>>> cout<< "command apply: "<< object_to_string(obj)<< "\n";
>>>
>>> and get something more useful than
>>>
>>> command apply: #<procedure #f ()>
>>>
>>> How can I examine the code of the procedure? Is it even possible at this
>>> stage?
>>> --
>>> ______________
>>> Miguel de Benito.
>>>
>>>
>
> --
> ______________
> Miguel de Benito.
>
>
> _______________________________________________
> Texmacs-dev mailing list
> Texmacs-dev@gnu.org
> https://lists.gnu.org/mailman/listinfo/texmacs-dev
_______________________________________________
Texmacs-dev mailing list
Texmacs-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/texmacs-dev
