zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: Feature request: a new warning option
Date: Wed, 9 Oct 2019 07:07:23 -0700	[thread overview]
Message-ID: <2e1cbea2-ef25-3e36-2a3a-34cf4decb6c6@eastlink.ca> (raw)
In-Reply-To: <CAKc7PVBQnt_ZE3X=8gz5R_VURwaTL3mDL=X-7H__yYqAjvXoWA@mail.gmail.com>

On 2019-10-09 6:41 a.m., Sebastian Gniazdowski wrote:
> but I'm seeing your point. This is like commenting or not the code – I
> was for a long long time pro-commenting, to just drop it recently,
> actually finding pleasure in writing a condensed, I could agree –
> (less /un)readable code.
>
Just a comment from the unwashed:

Maybe I'm the only one, but it has always seemed to me that in the 
entire cycle of developing software, the time spent entering keystrokes 
is a tiny fraction.  You save a few seconds typing a line, but come back 
to it a while later and you spend hours figuring out your own code.  Zsh 
has incredibly compact syntax already, and if I don't comment every 
line, since I can go months without writing anything, when I come back, 
I've forgotten the syntax and must refer to my comments.  They say that 
with Perl, every keystroke needs a sentence of comment to understand 
it.  My notion of the ideal language would be quite verbose and 
self-explanatory.  IMHO the last thing zsh needs is more terse syntax.  
Just my two cents.


  reply	other threads:[~2019-10-09 14:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09  4:02 Sebastian Gniazdowski
2019-10-09  8:45 ` Roman Perepelitsa
2019-10-09  8:49   ` Peter Stephenson
2019-10-09 11:56   ` Sebastian Gniazdowski
2019-10-09 12:08     ` Roman Perepelitsa
2019-10-09 13:17       ` Sebastian Gniazdowski
2019-10-09 13:24         ` Peter Stephenson
2019-10-09 13:41           ` Sebastian Gniazdowski
2019-10-09 14:07             ` Ray Andrews [this message]
2019-10-09 15:19               ` Peter Stephenson
     [not found]           ` <CAKc7PVBQnt_ZE3X=8gz5R_VURwaTL3mDL=X-7H__yYqAjvXoWA__41912.055101578$1570628583$gmane$org@mail.gmail.com>
2019-10-09 14:04             ` Stephane Chazelas
2019-10-09 13:40         ` Roman Perepelitsa
2019-10-09 17:36           ` Daniel Shahaf
2019-10-09 18:15 ` Bart Schaefer
2019-10-10  3:29   ` Sebastian Gniazdowski

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=2e1cbea2-ef25-3e36-2a3a-34cf4decb6c6@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).