GNOME.org
 

Re: [Geary] Follow-ups & new issues

Hi Johny,
On Wed, Aug 1, 2018 at 12:37 PM, Johny Why via geary-list <geary-list gnome org> wrote:
Andre wrote: "please file your bugs with Linux Mint in the issue tracker of Linux Mint." Now running 0.12.3. On Mint, the only way i could get it was PPA. Mint forum tells me they offer whatever version is in Ubuntu. Will you now tell me this is Ubuntu's fault? Please consider that users will get whatever version their repo gives them, so just MAYBE it's the geary-team's job to make sure the right version is out there. Maybe.
We have essentially zero say in what version linux distros package, it's entirely up to them. If you want to stay up to date, install from Flatpak or from the PPA.
Note also that unless Mint uses their forums for bug tracking, asking in forums isn't going to create any effective change for you. You may wish to consulte this guide for effective bug reporting for Mint: <https://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/>
Why is flatpak geary so HUGE? ~1.5GB. That's nuts! (that's why i used PPA).
It's not, it's about 7MB. If you have not installed another Flatpak app before, it will also need to download a runtime as well, which is probably what you are seeing.
I don't get red squigglies on the misspellings below. But if i right-click them, then i do get spelling suggestions. So it seems the spell-check is working, but red squigglies are not.
This is a bug in WebKitGTK. Please report it there: https://webkitgtk.org and let us know what the bug number is so we can keep track of it. Thanks! 


Some comments about replies:
- After deleting all previous text in a reply, the text-area from the deleted text is still there.
Yep, we should fix that. If you can file a bug about that in Geary's bug tracker, we'll take a look at it.
Question: Is it not possible to completely rip out the spell-check feature from geary? (i assume yes). Ok, that's a way to turn it off-- not a realistic one, of course. So, shy of removing the feature, is it not possible to disable the feature? There must be. So there's your "check now" button-- keep spell-check disabled until user enables it with "Check now" button. It's not really a check-now button-- it's an enable/disable button.
WebKitGTK does not work like that, unfortunately. We can of course disable then re-enable spell checking as you suggest, but enabling it will not automatically check the whole document, only changes made after enabling it. Again, this is WebKitGTK-specific, so please file a bug there if you would like this to change.
Michael wrote: "Geary checks spelling as you type it, so there is no need for either of the buttons. If that does not work..." If it's not working, how will the user know? There should be some kind of visual, such as a status bar message: "checking spelling".
As I mentioned to you already, if you are unwilling to trust us, type "asd".
There's a feature-request template in your gitlab, on the issue-compose screen. Maybe you should remove that template, if you don't want feature requests there.
As I have mentioned to you several times already, the process for reporting bugs and requesting new features is outlined on this page: https://wiki.gnome.org/Apps/Geary/ReportingABug 

Please read it.
I'm now typing this line at the bottom of this message. Since your compose screen goes to the very bottom of my display, the legs of p's and g's are getting cut off.
Please report a new bug for this in Geary's bug tracker, and attach a screenshot of the problem so we can look into it. 


Request: Clear and remove search-box when changing folders:

[snip]
3. Searchbox still contains old search string, even though messages are no longer filtered to search-string.
This is by design. As for other folders, it is indicated by the search folder no longer being selected.
Request: Scroll list to top after submitting search string. Not currently happening. I know you have a ticket for that after fetching, but not sure you have a ticket for that after searching.
This should be happening. If it is not and if you can reliably reproduce it, please file a new bug with instructions on how to do so. 


Request: In popout mode, change 'Save and Close' to "Save".
- i want to save without closing-- no way to.
- Redundant: There's already a close button.
We've had this discussion already in bugzilla, we don't need to rehash it again: https://bugzilla.gnome.org/show_bug.cgi?id=749918 


If you're doing auto-save, plz indicate!
- "Saving..." or "Saved" in statusbar.


We already do this in the composer toolbar.
- Your help says "For mail servers that support drafts, Geary will automatically save the message as you type." -- WHEN??? I've been composing for several minutes in this popout window, but the draft in the main window conversation-thread is still not updated. 

After a 10 second typing pause.
Your "quote/unquote" icons are too similar to the standard indent/outdent icons. Also, normal people don't know that greater-than symbol mean "quote". Normal people think the quote-symbol means quote.
We use the stock GTK icon names for this, so this not something we can fix. If you don't like the buttons please contact whoever created your icon theme about it. 


Bug? I think so:

- I inserted the image above.
- Then i removed it.
- Then, in my OS, i edited the image, and saved. The new image is much smaller. 
- Then came back here and inserted the image again.
- i got the old, unedited image, instead of the new edited image. Got the big one. 

Please file a bug about this with these steps to reproduce.
Request: Is there a "find" function in compose window? That would be extremely helpful when composing a long message.
Please file a new feature request for this if you cannot find one already in Gitlab/Bugzilla.
Request: Plz give message headers in conversation lists a stronger background color. I'm getting light gray headers in my theme. On my LCD screen, grays render much lighter near the bottom of the screen than near the top. Gray headers near the bottom of the screen a practically invisible. Can't see 'em.
As I have mentioned to you before, we don not have any control over colours, since that is the job of the GTK widget theme. Please file a bug with them about it.
- Request: Show header colors without mouse-hover. It's confusing that headers change color on hover. What's the point of that? I want to see where the headers are without having to go hunting with my mouse. Bad ue.
Pre-lighting active components is a standard GTK feature, this is not something Geary does. In any case, it is a standard way of indicating a point of interaction, so this is not going to change.
If you're asking people to post first to list before filing a bug, no probs. However, consider that end users will not go to the trouble of posting first to the list, and then REposting to gitlab after you say, "oh that's a new bug, please file a bug report on gitlab." DUPLICATE EFFORT.
Many bugs are filed that are either not a problem with Geary itself (see above for example), or are support requests such as "how do I do X". Asking people to post to the list first is the most efficient way of helping people work this out.
Bug: Extended fields sometimes show when Extended fields checkbox isn't checked. 
---
Bug: On shrink main window, sometimes shrunk window is too wide for display, and cannot be made narrow. Maximize restores windows to fit my display.
If you can reliably reproduce these, please file bugs with instructions on how to do so. 


Bug? Inconsistent paste (this message):
- In docked-draft-mode, pasting text is rich text.
- In popped-out mode, pasting text is plain text.
Per the link above, please search for existing bugs in case it is already known: https://bugzilla.gnome.org/show_bug.cgi?id=730495
I was asked not to add comments to closed gitlab issues, because devs will waste time going to read it. Suggestion: Assume if someone adds a comment to a gitlab issue WITHOUT re-opening the issue, then devs can assume they DON'T need to go read it.
You were asked to not continue commenting issues that were closed because were effectively support requests for problems that are not Geary's fault, and hence Geary developers are unable to fix, after the issue was closed as such, but despite this you kept adding comments.
We still get email if you comment on an issue without adding anything useful, so it still costs us time.
In general, A user should never feel like "i have no frigging idea what happened/is happening/is going to happen." But i feel like that ALL THE TIME while using geary. If your goal is ease-of-use, then please consider that.
We can't help you out if you make vague, general statements like this. If you can be specific, then we can help resolve these issues. 

//Mike

--
⊨ Michael Gratton, Percept Wrangler.
⚙ <http://mjog.vee.net/>
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]