20 minutes ago, Samuel Wales wrote:
> Just a reminder that adding things to the subject line can sometimes
> be an accessibility issue because they take up horizontal real
> estate, which can make subject headers truncate so much that there
> is no useful information left. For example, "Re: [magit] A question
> for magit developers ab". This occurs frequently with large fonts.
> It also happens with small devices and for people who put two
> windows side by side, but those are not as frequently accessibility
> issues.
I have been managing a number of mailing lists for some project, with
a number of subscribers and traffic that is orders of magnitude larger
than the magit list, and I have never heard such an argument brought
up as a problem. On the contrary: the purpose of the subject label is
not to subtract information (by truncating subjects) but to add that
information in a visible way so that you can easily classify it and
deal with your mail. It's not that I haven't heard any accessibility
issues -- I did had such things raised in various contexts.
As a side-note: personally, I can barely read mail on my phone, and
since I use gmail there (where I don't have my procmail add that
label), I have on numerous occasions read magit messages that *looked*
like personal messages because of the lack of a subject tag. I
eventually learned to read through the text blurb (even harder to read
than the subject) to know if it's a magit email. No matter what my
eye sight quality is, that's time that could have been avoided.
Sidenote#2: Yes, in a perfect world I'd have my client show that to me
(unlike what it does now, which is add to the subject) based on
mailing list headers. I could even do that for my own client (VM),
but good luck getting gmail to add that feature.
Sidenote#3: On gmail I could use labels, but doing that for tens of
lists is a project I don't have time to, and it places a higher
workload on subscribing to mailing lists since I'd need to maintain
these rules to match. Their recent feature of different tabs was a
nice approach to address this problem in a more automatic way, but the
quality of the classification was so poor that I gave up on it.
Sidenote#4: I'm well aware of the subject line limitation -- with my
Emacs setup, the line that I see for this email is:
->2983 Samuel Wales Aug 31 1K Re: [magit] RFC let us move to a better
mail
Ie, 32 characters left for the subject after 8 spent on the tag. IMO
it's still worth it.
Sidenote#5: You could say the same on "Re:" labeling, and I've never
heard that raised as an argument. (Including a google search on both
this and the mailing list tags.)
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
--
---
You received this message because you are subscribed to the Google Groups
"magit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
