As stated above, whenever I type a diacritic accent on a mac laptop sunning high sierra, the email composition window stops working and I have to close it (or mailspring itself) in order to continue writing the message.
I write emails in three languages, two of these three have accents, like this Ă©.
I am a paying customer and haven't received support after filing a bug. Pretty annoying.
...
...
...
--
Bug?
...
...
...
--
Feature Request?
...
Wow that's pretty crazy indeed. I'll see if I can reproduce this—could you elaborate on how the composer stops working? It just "locks" and won't accept any more text?
Hmm, so I've been able to reproduce an odd issue where sometimes I type a diatric character (´) and then the cursor jumps to /before/ the character instead of after it, so when I type the next character (e), it doesn't have the diatric. Once I do that, I'm not able to press backspace or move the cursor until I type another diatric mark (`). Is that what you're seeing? Definitely odd behavior... I'll see if I can get to the bottom of it.
exactly that and the app does not allow me to edit the message unless i restart it. It happens every minute to me as I write in Spanish and Portuguese, which use lots of diacritics (I just apply them unconsciously and cannot afford to type with spelling errors!).
Also, restarting the app seems to erase some bits of the draft.
I want to process a refund for my use of the app until this issue is fixed. I will still continue to pay as I need the receipt alert and cannot stop using the app. However it is not on a usable state.
On Feb 26 2018, at 7:57 pm, Ben Gotow notifications@github.com wrote:
>
Hmm, so I've been able to reproduce an odd issue where sometimes I type a diatric character (´) and then the cursor jumps to /before/ the character instead of after it, so when I type the next character (e), it doesn't have the diatric. Once I do that, I'm not able to press backspace or move the cursor until I type another diatric mark (`). Is that what you're seeing? Definitely odd behavior... I'll see if I can get to the bottom of it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (https://link.getmailspring.com/link/[email protected]/0?redirect=https%3A%2F%2Fgithub.com%2FFoundry376%2FMailspring%2Fissues%2F718%23issuecomment-368628023&recipient=reply%2B0144ecd2ebfdd39e7ec8954e7fae719b9ec2a105f0a8908c92cf0000000116ac277992a169ce11d89f5e%40reply.github.com), or mute the thread (https://link.getmailspring.com/link/[email protected]/1?redirect=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAUTs0qZ7PX3IIp2jpEB0TG01Juo6Jtdzks5tYwt5gaJpZM4SPjai&recipient=reply%2B0144ecd2ebfdd39e7ec8954e7fae719b9ec2a105f0a8908c92cf0000000116ac277992a169ce11d89f5e%40reply.github.com).
Same problem here. I need to close the composer window, go to Draft and double click into the email and start again.
It’s so frustrating, and Mailspring has no customer support, even though I am a paying customer!
This app feels like a scam ripoff of a once noble open source project called nylas mail.
On 6 Mar 2018, at 18:07, Gustavo Azambuja notifications@github.com wrote:
Same problem here. I need to close the composer window, go to Draft and double click into the email and start again.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Foundry376/Mailspring/issues/718#issuecomment-370873696, or mute the thread https://github.com/notifications/unsubscribe-auth/AUTs0lDFVM3KIjYLsDZyRLhpDTCwTp66ks5tbtBfgaJpZM4SPjai.
I have the same problem on MacOS and the US International - PC keyboard layout. It's definitely intermittent, and it definitely goes away if I switch to the regular US keyboard layout. It got better (i.e. less frequent) a few patches ago.
Is it something to do with how MacOS handles these key replacement layouts? I know it's different than how windows handles it. In MacOS, using the special diacritic keys first inputs the character (with some visual signal that it's tentative, like making it underlined), then it deletes that character on the next keystroke while inputting the correct character. Windows and Linux both just skip the first two steps, providing no visual feedback that the diacritic keystroke has been pressed before inputting the correctly accented character. Is that process of inputting, signaling, then deleting the character conflicting with some other character watching process in the composer window?
Thanks Ben!
PS - I'm also a paying "customer" but don't feel entitled to your attention/time. You're doing a great job irmĂŁo and mailspring is turning out fantastic!
IrmĂŁo,
No need for the passive aggressivity. It’s like saying you don’t feel entitled to occupy the flat you are paying rent for. I don’t feel entitled, at least I feel like I shouldn’t be charged £8 monthly for a half baked app. I know the process is going well but this is about ethics, not about feelings. In that case, it’s fine if the customer support is clear about its limitations, and the app is rightly branded as a beta version that is being charged. The thing that is annoying me the most is the fact that I opted out to continue the payment and got disconnected from a full month for the service I had paid. No answer as of now, and so I feel like I can rightly be frustrated.
Saudações,
M.
Sent from mobile device
On 8 Mar 2018, at 01:34, Justin Michael Doran notifications@github.com wrote:
I have the same problem on MacOS and the US International - PC keyboard layout. It's definitely intermittent, and it definitely goes away if I switch to the regular US keyboard layout. It got better (i.e. less frequent) a few patches ago.
Is it something to do with how MacOS handles these key replacement layouts? I know it's different than how windows handles it. In MacOS, using the special diacritic keys first inputs the character (with some visual signal that it's tentative, like making it underlined), then it deletes that character on the next keystroke while inputting the correct character. Windows and Linux both just skip the first two steps, providing no visual feedback that the diacritic keystroke has been pressed before inputting the correctly accented character. Is that process of inputting, signaling, then deleting the character conflicting with some other character watching process in the composer window?
Thanks Ben!
PS - I'm also a paying "customer" but don't feel entitled to your attention/time. You're doing a great job irmĂŁo and mailspring is turning out fantastic!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Hey folks—finally got to the bottom of this over here: https://github.com/ianstormtaylor/slate/issues/1708, and it'll be fixed in the next release of Mailspring (early next week). This turned out to be pretty subtle and I'm hoping the folks working on Slate can make changes to prevent this sort of bug from ever happening again. Stay tuned—
Just to follow up, this seems fixed for me now after the update. It might by psychosomatic, but the composer also just feels way snappier and more stable with this update. Great job and thank you!
Hey folks! Sorry I never closed this ticket — this shipped a while back. Thanks to everyone for reporting this and submitting feedback.
Most helpful comment
Hey folks—finally got to the bottom of this over here: https://github.com/ianstormtaylor/slate/issues/1708, and it'll be fixed in the next release of Mailspring (early next week). This turned out to be pretty subtle and I'm hoping the folks working on Slate can make changes to prevent this sort of bug from ever happening again. Stay tuned—