Jim Jackson <
[email protected]> wrote:
References: <[email protected]> <lEIKM.585771$[email protected]> <udgb2d$3obdi$[email protected]> <udgujh$3udev$[email protected]> <C4HLM.1176633$[email protected]>
Followup-To:
On 2023-09-11, rdh <[email protected]ute> wrote:
On 9/9/23 00:08, Rich wrote:
Typically you get your editor pre-loaded with quoted text from the
article and you enter your responses (and clip out parts that no longer
need to remain).
That last bit doesn't happen as much as it should.
Yes indeedy. But why?
Ok the obvious - idleness, in a hurry, lack of focus.
The not obvious - how many "editors" in non-text apoplications make it difficult? The one's I've come across need you to highlight the bit to delete, then hit delete. While text mode editors have mark/line delete keyboard functions which work quite quick (for those that use them). I'm happy using vi or emacs type keys for delete and finds it really quick.
The quick line delete is particularly useful.
Or, in the case of google groups users it is that the GG web interface
hides all the quoted text initially behind a small (IIRC) grey "plus to
expand here" icon that can be easily overlooked. So many of them are completely unaware that there is even quoted text to trim.
And, I think when reading in GG, it also hides the quoted text, because
the actual article content is "just above" in their web view. So not
only do they have no reminder to trim when writing, but they don't see
the mess they make when they fail to trim, because the web ui hides
that mess from them behind another little "expand this" icon.
If other builtin newsreader editors do anything similar, then another
reason can be because the user didn't pay attemtion, and their editor
defaults (and/or reader defaults) hid from them most of the view
necessary to remind them to trim.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)