Hi Mike et al
Some additional items, and replies inline.
Note, all caps isn't yelling-- it's in lieu of italic or underline. I assume the list is plain-text.
---
it's unclear the purpose of the mutli-arrows under quoted excerpts. I'm guessing they are to reveal/collapse long quotes, but with short quotes they're pointless. They should only display when needed-- Just like window scroll bars don't display unless a window is longer than display area. (i'm not saying there's a relationship between scrollbars and the collapse arrows-- that was a simile)
---
Bug:
re geary asking for keyring on every launch: this is still happening. BUT: this only happens if geary is in Application Autostart. That is, when geary launches itself on boot, i get asked for keyring and gmail passwords.
However, if i remove geary from Application Autostart, and manually launch geary after OS has settled, then i DON'T get asked for any passwords.
Seems clear the OS just isn't quite ready-- geary starts too soon. It's normal and to be expected that the OS needs to finish booting before the OS is ready.
Correct me if i'm wrong-- i believe geary put itself into Application Autostart during installation. Right? If so, then I would call that a geary bug, not an OS bug. Geary should know the OS isn't ready--
- either put a delay in geary's start (or wait until some OS "ready" event fires).
- or, don't put geary into Application Autostart during installation.
Maybe your devs have faster machines than mine. Not everyone has a fast machine. As a programmer, i always test code on low-resource machines. Please consider doing that.&nbs
p;
---
Request: Items in message list: too tall. Plz give a compact view or option. It REDUCES MY PRODUCTIVITY to see so FEW messages at a glance.
- show just 1-line preview, instead of 2 lines.
- less white space above/below text
- Reduce left-padding in message-list, which will widen the text area horizontally. The wide left-padding is very wasteful, serves no purpose-- I can drag pane width if i want more space.
---
Bug? This video shows highlight-drag doing a copy instead of expected move.
---
Bug? vid shows insertion-point stuck at end of a line, while hitting enter repeatedly.
---
Bug:
Received "error saving" during auto-save. This makes geary unusable.
I'd give a stack trace, but wasn't running under debug at the time symbols. If continues to happen, i'll do a trace. But this error is intermittent, so hard to catch it.
Since this bug make geary unusable, i prolly won't continue using it anyway. Last time was 3 years ago. I'll come back in another 3 years to see how it's going. Seems a lot to fix.
---
Suggestion: put link to stack-trace instructions in Help, under "Think you've found a bug?"
On Tue, Jul 31, 2018 at 9:57 PM, Michael Gratton <mike vee net> wrote
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!
Plz see my comments below about me filing bug reports.
---
- 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.
Does that mean, if i don't file a bug, then you won't look at it? Oh well.
Your request above, that i file a bug, is exactly what i was refering to in another comment, which it seems you misread. your reply seems to indicate that you did not understand (or read) my comment. Here it is again:
** 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 tro
uble of posting first to the list, and then --> --> REposting to gitlab ** That's DUPLICATE EFFORT.**
you replied:
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.
That answer doesn't seem to fit my comment.
My feeling is: i've done my part, by reporting this to the list. I've already annoyed people by posting stuff on your gitlab you don't want there.
And you want users less technical than me opening tickets on gitlab? Just imagine all the annoying wrong tickets you'll get then.
---
Michael wrote: "Geary checks spelling"
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".
I consider that a flip response, and not a solution for general users. They won't even know it's not working, until they send out a message to their boss with misspellings. That won't make geary popular.
Imo, unless you are 100% sure spell-check is working on all platforms, you should give some visual cue to users, just as you do when saving. But, if you are not targeting general users, don't worry about it.
It's not about trusting you-- it's about trusting the software. It has some other issues (eg red squigglies).
---the process for reporting bugs and requesting new features is outlined on this page: https://wiki.gnome.org/Apps/Geary/ReportingABug
I read it. It says to put feature requests on gitlab. I may be incorrect, but it seems you were unhappy when i put non-bug feature-requests on gitlab. So i'll just avoid gitlab.
---at 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.
Here's a screenshot showing g and p legs getting cut off. http://i.imgur.com/fsWmvX8.png
As mentioned above, i'm reticent to post anything on your gitlab.
- you're asking me to duplicate my effort.
- i've annoyed people by posting the wrong stuff there.
- i prefer to let y'all do the gitlab part.
Unless you'r
e looking to hire a software tester. Really :)
---
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.
I didn't even notice the search folder, but i see what you mean. i think you're not being senstive to users.
- As mentioned, i didn't notice the search folder.
- When geary starts, there is not search box. Once opened, it says open forever. That's weird. Your design seems to be:
- Before my first search, i never need to search. Ever.
- After my first search, i always need to search. Constantly.
That's not how people work.
You don't display the search box on launch. That means,
"i'm not in search mode."
Then i do a search. Search box is visible.
Then i switch to another folder. Search box is STILL visible.
That means, when searching:
- search box is visible
and when i'm NOT searching:
- search box is NOT visible before my first search
- search box IS visible after my first search.
Ie., search box is visible in two scenarios:
- When searching
- When NOT searching
Non-intuitive, convoluted, and confusing as f, to me.
---- i want to save without closing-- no way to.
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
No, that was a different issue. That discussion was about alert-verbiage at time of closing a draft, and about geary deleting the draft as soon as user starts editing it.
THIS issue is about what kind of button to put in the Draft editor.
---
- "Geary will automatically save the message as you type."
-- WHEN???
After a 10 second typing pause.
Suggestion: Please explain that in Help file. Thx. That's related to "i don't know what's happening."
User might not notice the "Saving" alerts (i didn't until you told me).
---
- I inserted the image.
- 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.
Please see my comments above about me reporting bugs.
---
Request: Is there a "find" function in compose window?
Please file a new feature request for this if you cannot find one already in Gitlab/Bugzilla.
Same.
---Pre-lighting active components is a standard way of indicating a point of interaction
But there's no interaction yet. I didn't click it yet.
For example, with buttons, the appearance of a button A
S A BUTTON is a standard way of indicating that a button is a button WITHOUT HAVING TO HOVER YOUR MOUSE OVER IT. On the web, a button format might change a bit when you hover, but it still looks like a button even when you're NOT hovering.
It's not just about interaction-- it's formatting. Even if it WASN'T clickable, the header should be formatted differently than the body of the message, to differentiate it. It's a different STRUCTURAL area.
---
This video show bug on trying to backspace. First time it happened. When i backspace on the second line, it should move up to the previous line. It didn't. Intermittent issue. Can't tell you how to reproduce.
https://youtu.be/dy-NF0pLo1g
---
This video shows can't "paste without formatting".
https://youtu.be/F69EliplyZU
---
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.
I'm sorry i cannot "reliably duplicate", but both have happened a few times. Some bugs are INTERMITTENT, and difficult to "reliably duplicate".
---- 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
Plz see my comments above about me reporting bugs.
---We still get email if you comment on an issue without adding anything useful, so it still costs us time.
Then I assume whomever gets the list emails are different people than those who get gitlab emails. Both are emails.
But no worries-- per my comments above, i'll restrict my communications to the list. In a few years.
---
In general, A user should never feel like "i have no frigging idea what happened/is happening/is going to happen."
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.
The various issues i've reported are intended to be specific examples of not knowing what's happening.
Looking forward to geary's continued development. Is there anyone i can ask to give you more resources to work on it?
Thx and regards,
Johny
Happy Colorado Day!
