Delicious Library's bug reporter assumes that I'm using Mail.app.
I have an easily reproducible bug in Delicious Library 2 and wanted to send it in using the crash reporter, but it launches Mail.app. I don't use Mail.app (indeed, I rather dislike it); it seems like it would be rather nice if DL2 could check and see if I'm using Mail and, if I'm not, just open my e-mail program rather than Mail.app with the special bug reporter window.
5
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?Noted. Unfortunately right now we're still working on fixing those bugs that are triggering Mail to launch in the first place, and working on an iPhone app, but I'll definitely take your complaint into consideration.
The company says
this solves the problem
-
Inappropriate?Worse yet, it doesn't actually seem to be sending anything - at least not according to the Sent Mail folder.
-
And, I just noticed that "the company" thinks this problem is solved. Not. -
Inappropriate?Well, you could -try- the following. Go to the Applications folder, then:
1) rename Mail to something else, e.g. AppleMail
2) make an alias to your preferred mail app, e.g. select your app and then invoke "File" -> "Make Alias"
3) rename the new alias to "Mail" -
Inappropriate?I was just noting in the notes for the new version about using the "default mail app".
Why not just submit crash data and feedback directly to a database using an HTTP POST? I don't use a local mail app on my computer at all -- I either use a mail app inside a browser, or in a terminal window. (You can have my PINE when you pry it from my cold dead hands.) Skipping the mail app entirely seems like it would greatly simplify the process of submission.
I think my crashes have all been getting submitted to Apple, but not DM, because the OS has a feature where it pops up a window that sends along crash data, and asks for any comments on what you were doing when things went wrong. This seems like the correct paradigm for that feature.
I’m unimpressed.
Loading Profile...




EMPLOYEE


