zsh-users
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: Announcing zsh-scan, a zsh-linter
Date: Tue, 31 Jan 2023 07:37:39 +0000	[thread overview]
Message-ID: <CAKc7PVBbMo6cBuUkpDW4sT+z0u4O6RXLNCQH0VnDW3gj0cxMbw@mail.gmail.com> (raw)
In-Reply-To: <CAKc7PVBWGoj-+c5d8sLXShqLdpjkQiSAT2RxGQdqLMoWA63C9g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]

Also added: reporting on exact missing setopt options – till now it was
showing all recommended options, now it filters out the already given.

On Sat, 28 Jan 2023 at 20:26, Sebastian Gniazdowski <sgniazdowski@gmail.com>
wrote:

> Added warncreateglobal like checking but statically
>
> sob., 28 sty 2023, 10:19 użytkownik Sebastian Gniazdowski <
> sgniazdowski@gmail.com> napisał:
>
>> Hi,
>> a zsh linter with 7 checks currently:
>>
>> https://github.com/psprint/zsh-scan
>>
>> The checks are:
>> - whether emulate -L -o … or setopt has been used,
>> - whether fun-name() { preamble exists within an autoload function (it's
>> good practice to help Ctags recognizing the function),
>> - whether certain, useful options has been given, like localoptions,
>> typesetsilent, extendedglob, etc.
>> - whether -F option has been given to zparseopts (toggles error
>> detection),
>> - whether -U option has been given to autoload,
>> - whether 0=… assignment exists,
>> - and whether 0= has a standard form,
>> - also, if variable being array is appended without (…), ie. arr+=elem
>> instead  of arr+=(elem)
>>
>> Does someone have any idea of some new checks to add?
>>
>> --
>> Best regards,
>> Sebastian Gniazdowski
>>
>>

-- 
Best regards,
Sebastian Gniazdowski

[-- Attachment #2: Type: text/html, Size: 3588 bytes --]

  reply	other threads:[~2023-01-31  7:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28  9:19 Sebastian Gniazdowski
2023-01-28 20:26 ` Sebastian Gniazdowski
2023-01-31  7:37   ` Sebastian Gniazdowski [this message]
2023-01-31 14:09     ` Ray Andrews

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=CAKc7PVBbMo6cBuUkpDW4sT+z0u4O6RXLNCQH0VnDW3gj0cxMbw@mail.gmail.com \
    --to=sgniazdowski@gmail.com \
    --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).