From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: `[[ -n $VAR ]]` equal to `[[ $VAR ]]`?
Date: Mon, 13 Apr 2015 09:52:33 -0700 [thread overview]
Message-ID: <552BF451.4080701@eastlink.ca> (raw)
In-Reply-To: <mg7p91$7mp$1@ger.gmane.org>
On 04/09/2015 11:06 PM, Thorsten Kampe wrote:
>
> (please don't top post, it's a lot of work to fix the mail before replying)
>
>> We lost the battle of top versus bottom posting twenty years ago. Move on.
> I kind of agree. The bad thing is that top-posting and not snipping
> the parts you are responding to, massively decreases the readibility
> and usefullness of email.
>
> You just read the first paragraph of an email and ignore all the
> rest. I do it, the person I'm responding to does it. Kind of like a
> lose-lose situation. Of course, the person that seeks help loses
> more.
My two cents is that each has it's place. If I'm replying to an email
in the most 'general'
way--something like "Ok, thanks."--I top post, but if replying to
specific points, then I
always interleave or bottom post--doing anything else seems strange.
What I myself
can't stand is the eternally incrementing email that you see more and
more of.
next prev parent reply other threads:[~2015-04-13 17:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 1:23 Thorsten Kampe
2015-04-10 1:31 ` Kurtis Rader
2015-04-10 1:39 ` Thorsten Kampe
2015-04-10 2:02 ` Kurtis Rader
2015-04-10 2:05 ` Kurtis Rader
2015-04-10 2:46 ` Mikael Magnusson
2015-04-10 2:59 ` Kurtis Rader
2015-04-10 4:00 ` Mikael Magnusson
2015-04-10 6:06 ` Thorsten Kampe
2015-04-13 16:52 ` Ray Andrews [this message]
2015-04-13 17:36 ` Roman Neuhauser
2015-04-13 23:58 ` Ray Andrews
2015-04-14 1:27 ` Bart Schaefer
2015-04-14 15:06 ` Ray Andrews
2015-04-10 3:21 ` Kurtis Rader
2015-04-10 2:01 ` Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=552BF451.4080701@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).