In the Pre-Debug window there is the <Report> button that coverts the call stack to text that can be pasted into an email. But when you proceed into the main debugger it seems you lose access to that feature. Would it be worth adding <Report> to the debugger context menu? cheers -ben
Is this functionality actually used? Where do the reports end up? What is contained in the report? Peter On Thu, Nov 2, 2017 at 4:35 AM, Ben Coman <btc@openinworld.com> wrote:
In the Pre-Debug window there is the <Report> button that coverts the call stack to text that can be pasted into an email. But when you proceed into the main debugger it seems you lose access to that feature.
Would it be worth adding <Report> to the debugger context menu?
cheers -ben
I think it is outdated feature and we should remove it to not confuse people. 2017-11-02 9:10 GMT+01:00 Peter Uhnák <i.uhnak@gmail.com>:
Is this functionality actually used? Where do the reports end up? What is contained in the report?
Peter
On Thu, Nov 2, 2017 at 4:35 AM, Ben Coman <btc@openinworld.com> wrote:
In the Pre-Debug window there is the <Report> button that coverts the call stack to text that can be pasted into an email. But when you proceed into the main debugger it seems you lose access to that feature.
Would it be worth adding <Report> to the debugger context menu?
cheers -ben
I've never used it to auto-report to any remote remote server. That part can go. But as I stated, I do find it useful for getting a text representation of the stack for manually pasting into fogbugz issues, instead of having to dig through the halos into the morph contents. Can this part be kept and moved into the stack-context-menu? cheers -ben On Thu, Nov 2, 2017 at 5:59 PM, Denis Kudriashov <dionisiydk@gmail.com> wrote:
I think it is outdated feature and we should remove it to not confuse people.
2017-11-02 9:10 GMT+01:00 Peter Uhnák <i.uhnak@gmail.com>:
Is this functionality actuaat part can golly used? Where do the reports end up? What is contained in the report?
Peter
On Thu, Nov 2, 2017 at 4:35 AM, Ben Coman <btc@openinworld.com> wrote:
In the Pre-Debug window there is the <Report> button that coverts the call stack to text that can be pasted into an email. But when you proceed into the main debugger it seems you lose access to that feature.
Would it be worth adding <Report> to the debugger context menu?
cheers -ben
Maybe we should name and implement it as "copy stack to clipboard"? 2017-11-02 13:19 GMT+01:00 Ben Coman <btc@openinworld.com>:
I've never used it to auto-report to any remote remote server. That part can go. But as I stated, I do find it useful for getting a text representation of the stack for manually pasting into fogbugz issues, instead of having to dig through the halos into the morph contents. Can this part be kept and moved into the stack-context-menu?
cheers -ben
On Thu, Nov 2, 2017 at 5:59 PM, Denis Kudriashov <dionisiydk@gmail.com> wrote:
I think it is outdated feature and we should remove it to not confuse people.
2017-11-02 9:10 GMT+01:00 Peter Uhnák <i.uhnak@gmail.com>:
Is this functionality actuaat part can golly used? Where do the reports end up? What is contained in the report?
Peter
On Thu, Nov 2, 2017 at 4:35 AM, Ben Coman <btc@openinworld.com> wrote:
In the Pre-Debug window there is the <Report> button that coverts the call stack to text that can be pasted into an email. But when you proceed into the main debugger it seems you lose access to that feature.
Would it be worth adding <Report> to the debugger context menu?
cheers -ben
sounds good. cheers -ben On Thu, Nov 2, 2017 at 10:55 PM, Denis Kudriashov <dionisiydk@gmail.com> wrote:
Maybe we should name and implement it as "copy stack to clipboard"?
2017-11-02 13:19 GMT+01:00 Ben Coman <btc@openinworld.com>:
I've never used it to auto-report to any remote remote server. That part can go. But as I stated, I do find it useful for getting a text representation of the stack for manually pasting into fogbugz issues, instead of having to dig through the halos into the morph contents. Can this part be kept and moved into the stack-context-menu?
cheers -ben
On Thu, Nov 2, 2017 at 5:59 PM, Denis Kudriashov <dionisiydk@gmail.com> wrote:
I think it is outdated feature and we should remove it to not confuse people.
2017-11-02 9:10 GMT+01:00 Peter Uhnák <i.uhnak@gmail.com>:
Is this functionality actuaat part can golly used? Where do the reports end up? What is contained in the report?
Peter
On Thu, Nov 2, 2017 at 4:35 AM, Ben Coman <btc@openinworld.com> wrote:
In the Pre-Debug window there is the <Report> button that coverts the call stack to text that can be pasted into an email. But when you proceed into the main debugger it seems you lose access to that feature.
Would it be worth adding <Report> to the debugger context menu?
cheers -ben
Can you open a bug entry? On Thu, Nov 2, 2017 at 4:16 PM, Ben Coman <btc@openinworld.com> wrote:
sounds good. cheers -ben
On Thu, Nov 2, 2017 at 10:55 PM, Denis Kudriashov <dionisiydk@gmail.com> wrote:
Maybe we should name and implement it as "copy stack to clipboard"?
2017-11-02 13:19 GMT+01:00 Ben Coman <btc@openinworld.com>:
I've never used it to auto-report to any remote remote server. That part can go. But as I stated, I do find it useful for getting a text representation of the stack for manually pasting into fogbugz issues, instead of having to dig through the halos into the morph contents. Can this part be kept and moved into the stack-context-menu?
cheers -ben
On Thu, Nov 2, 2017 at 5:59 PM, Denis Kudriashov <dionisiydk@gmail.com> wrote:
I think it is outdated feature and we should remove it to not confuse people.
2017-11-02 9:10 GMT+01:00 Peter Uhnák <i.uhnak@gmail.com>:
Is this functionality actuaat part can golly used? Where do the reports end up? What is contained in the report?
Peter
On Thu, Nov 2, 2017 at 4:35 AM, Ben Coman <btc@openinworld.com> wrote:
In the Pre-Debug window there is the <Report> button that coverts the call stack to text that can be pasted into an email. But when you proceed into the main debugger it seems you lose access to that feature.
Would it be worth adding <Report> to the debugger context menu?
cheers -ben
cool. done. https://pharo.fogbugz.com/f/cases/20631/debugger-copy-stack-to-clipboard cheers -ben On Fri, Nov 3, 2017 at 1:03 AM, Stephane Ducasse <stepharo.self@gmail.com> wrote:
Can you open a bug entry?
On Thu, Nov 2, 2017 at 4:16 PM, Ben Coman <btc@openinworld.com> wrote:
sounds good. cheers -ben
On Thu, Nov 2, 2017 at 10:55 PM, Denis Kudriashov <dionisiydk@gmail.com> wrote:
Maybe we should name and implement it as "copy stack to clipboard"?
2017-11-02 13:19 GMT+01:00 Ben Coman <btc@openinworld.com>:
I've never used it to auto-report to any remote remote server. That
part
can go. But as I stated, I do find it useful for getting a text representation of the stack for manually pasting into fogbugz issues, instead of having to dig through the halos into the morph contents. Can this part be kept and moved into the stack-context-menu?
cheers -ben
On Thu, Nov 2, 2017 at 5:59 PM, Denis Kudriashov <dionisiydk@gmail.com
wrote:
I think it is outdated feature and we should remove it to not confuse people.
2017-11-02 9:10 GMT+01:00 Peter Uhnák <i.uhnak@gmail.com>:
Is this functionality actuaat part can golly used? Where do the
reports
end up? What is contained in the report?
Peter
On Thu, Nov 2, 2017 at 4:35 AM, Ben Coman <btc@openinworld.com> wrote:
In the Pre-Debug window there is the <Report> button that coverts
the
call stack to text that can be pasted into an email. But when you proceed into the main debugger it seems you lose access to that feature.
Would it be worth adding <Report> to the debugger context menu?
cheers -ben
participants (4)
-
Ben Coman -
Denis Kudriashov -
Peter Uhnák -
Stephane Ducasse