Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: "Carlos E. R." <robin_listas@es.invalid>
Newsgroups: comp.os.linux.misc
Subject: Quoting [Was: tint2 keeps crashing]
Date: Tue, 14 Nov 2023 21:56:07 +0100
Lines: 44
Message-ID: <kri577Fbjm2U10@mid.individual.net>
References: <uitv16$s9av$1@dont-email.me> <87v8a515hg.fsf@usenet.ankman.de> <87zfzglr8j.fsf@lenovo.lan> <uivfdf$168a2$3@dont-email.me> <uivj4g$16ks7$2@dont-email.me> <20231114120846.7503cf14@archie.localdomain> <uivkm7$16ks8$2@dont-email.me> <20231114122156.1cd886ed@archie.localdomain> <uj0cpr$1b16a$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net nkuS5kGX2BDzajiCaszRQwSLGZtDmE+zHDYdHnpBd46/zeFfuk
Cancel-Lock: sha1:DfpCSCaHUg1+40QlAYhlDw49NmE= sha256:nbstdt5jNc/Ojfp46/QGJWWuwMcnJwVFYIf4tdWXaTU=
User-Agent: Mozilla Thunderbird
Content-Language: en-CA, es-ANY
In-Reply-To: <uj0cpr$1b16a$1@dont-email.me>
Xref: csiph.com comp.os.linux.misc:43730

On 2023-11-14 19:09, Nuno Silva wrote:
> On 2023-11-14, vamastah wrote:
>> On Tue, 14 Nov 2023 12:12:07 +0100
>> Joerg Lorenz <hugybear@gmx.net> wrote:

...

> Now, as I think others are already mentioning, there's a difference
> between quoting everything and narrowing it down to what is
> relevant. Perhaps (in the first block of quoted text above) I could have
> removed Joerg's reply, but it looked to me that it helped put your
> latest reply in context. I personally usually put "[...]" when I narrow
> down by removing lines in the middle, but that's up to you: I've seen
> "<snip/>" used too, and there will surely be other examples. (I mean
> doing something like:
> 
> On 2023-11-14, vamastah wrote:
> 
>>> On 14.11.23 12:08, vamastah wrote:
>>>> btw, is it better to quote the original message or not? im quite
>>>> confused when i read netiequette and see the actual customs.
> [...]
>> well, i find it superfluous and sometimes even messy but let it be
>> *eot*
> 
> )
> 
> (If you find it superfluous, you could try looking at news clients or
> extensions for news clients that offer the ability to collapse quoted
> text by default. It's possible such a feature will have issues in corner
> cases, or with less usual quoting indicators, but should work well
> enough most of the time? (But I don't use a feature like that myself,
> hopefully someone else will be able to give you more or better advice on
> this topic.))

I would advise against collapsing quotes by default, unless you find an 
IA for doing it. Yes, the quoted part can be overly too large often, but 
hiding it all removes the entire context for the answer and may lead the 
reader to understand it wrongly. I have seen it happen.

-- 
Cheers,
        Carlos E.R.