zsh-users
 help / color / mirror / code / Atom feed
From: Christian Heinrich <christian@gladbachcity.de>
To: zsh-users@zsh.org
Subject: Re: Feature request (@M):# with context matches
Date: Sat, 30 Jan 2016 15:38:04 +0100	[thread overview]
Message-ID: <1454164684.1526.25.camel@gladbachcity.de> (raw)
In-Reply-To: <CAKc7PVAe0N2bp2XS5U4mOKnTgxQRsj4UGy7NQpHput9VsbnAJw@mail.gmail.com>

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

Hi Sebastian,

I'm not sure what you want to do, but I my guts tells me that you want
to re-invent the wheel as you stated that you want to replace several
tools with ZSH. If you can achieve your goal by calling a GNU tool, you
should do that. These are mature tools and there is nothing wrong about
using them. (And it's certainly a benefit that you don't have to
maintain them.)

Calling "grep" is also more understandable by everyone than the pattern
you gave in your first email.

Best regards
Christian

> The idea is to confront Bash Advanced Scripting Guide coders, BASG
> coders for short. Every sed, awk, grep can be replaced by Zsh code.
> No
> need for `` / $() what Bash coders love (not all, could name at least
> one that doesn't, is present at #zsh IRC channel). However, grep -C
> is
> not very possible to replace with Zsh code. I plan to write
> Markdown/PDF  document where every GNU utility will be coded via
> native Zsh code, without forks, and the grep -C is one problem that I
> can perceive now.
> 
> Best regards,
> Sebastian Gniazdowski

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2016-01-30 14:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29 10:15 Sebastian Gniazdowski
2016-01-30 12:13 ` Sebastian Gniazdowski
2016-01-30 14:38   ` Christian Heinrich [this message]
2016-01-30 15:34     ` Sebastian Gniazdowski
2016-01-30 16:54   ` Bart Schaefer
2016-01-30 20:42     ` Bart Schaefer
     [not found]   ` <160130085456.ZM9730__49922.0612728552$1454172936$gmane$org@torch.brasslantern.com>
2016-02-07  0:22     ` min() max() math functions (was: Re: Feature request (@M):# with context matches) Daniel Shahaf
2016-02-07  1:00       ` Bart Schaefer
     [not found]       ` <160206170040.ZM1927__13399.3204137825$1454806909$gmane$org@torch.brasslantern.com>
2016-02-09  3:23         ` Daniel Shahaf

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=1454164684.1526.25.camel@gladbachcity.de \
    --to=christian@gladbachcity.de \
    --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).