Thanks everyone. In a former life I worked as a software developer in an
organization with an _incorrigible_ QA department, so I learned
firsthand the value of good bug reports and the vexation caused by bad
ones.
-sam
On 30 Oct 2017, at 20:59, Paul Sture wrote:
On 18 Oct 2017, at 20:21,
On 18 Oct 2017, at 20:21, John Cooper wrote:
Now this is a great bug report! Takes me back to my early career as a
tester on Aldus PageMaker 5. :)
It takes me back to middleware and OS bugs. Providing the developer(s)
with a simple means of reproducing the problem has resulted in many a
On 18 Oct 2017, at 20:09, Sam Hathaway wrote:
### Actual result ###
* There is a new message in the Drafts folder that contains the state
of the message _at the time that it was converted to Markdown format._
In this example, it will contain `Hello, *world!*` but _not_ `Goodbye,
world!`.
On 18 Oct 2017, at 14:21, John Cooper wrote:
Now this is a great bug report! Takes me back to my early career as a
tester on Aldus PageMaker 5. :)
a PageMaker… now we’re both dating ourselves!
v
___
mailmate mailing list
Now this is a great bug report! Takes me back to my early career as a
tester on Aldus PageMaker 5. :)
Sam Hathaway wrote (at 11:09 on 18 Oct 2017):
## Scenario 1: No Markdown, works as expected ##
### Steps to replicate ###
1. Reply to a text-only message.
2. Type some non-Markdown text.
3.
## Scenario 1: No Markdown, works as expected ##
### Steps to replicate ###
1. Reply to a text-only message.
2. Type some non-Markdown text.
3. Hit Cmd-W to close.
4. Click “Don’t Save”.
### Expected/actual result ###
* No message is added to the Drafts folder.
## Scenario 2: Markdown, draft
