Allan Odgaard 6042bc86d6 Log current key event in diagnostic reports ...

When a C++ exception is thrown from code invoked via a menu item then the menu item dispatcher will catch the exception and abort, this means the report doesn’t show the actual exception or contain any of the involved code.

By logging the key event in the report we should be able to deduce what action was invoked.

Adding info to diagnostic reports “documentation” from http://mjtsai.com/blog/2013/02/27/application-specific-crash-report-information/

2013-03-01 16:41:01 +01:00

..

bl

Use dispatch queues when updating bundle sources

2012-09-30 23:06:58 +02:00

decompile_as

Use @autoreleasepool blocks

2012-09-25 12:30:12 +02:00

gtm

Use std::string over char const*

2012-09-20 12:22:21 +02:00

indent

Initial commit

2012-08-09 16:25:56 +02:00

mate

Change text::format → std::to_string (C++11)

2013-02-08 11:20:34 +01:00

NewApplication

Convert strings files to UTF-8

2013-01-02 01:46:48 +01:00

pretty_plist

Let the pretty_plist CLI tool accept file name

2013-01-13 11:56:06 +01:00

PrivilegedTool

Use path::is_absolute instead of custom code

2013-02-25 15:25:17 +01:00

scmls

Change scm::status::versioned → none

2012-09-02 17:53:50 +02:00

TextMate

Log current key event in diagnostic reports

2013-03-01 16:41:01 +01:00

tm_query

Exclude variables when dumping all settings

2012-09-24 22:57:50 +02:00

.tm_properties

Initial commit

2012-08-09 16:25:56 +02:00

target

Only set -fobjc-link-runtime for app targets

2013-02-25 15:28:37 +01:00