all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Too fine design granularity leads to numerous macro/function/command existed in Emacs.
Date: Sat, 14 Aug 2021 01:42:45 +0200	[thread overview]
Message-ID: <871r6w7vyi.fsf@zoho.eu> (raw)
In-Reply-To: AM9PR09MB4977A06DDBC5CD965208218896FA9@AM9PR09MB4977.eurprd09.prod.outlook.com

Arthur Miller wrote:

> You don't believe that programming shell script requires at
> least some programming fluency AND some inside knowledge hot
> the particular tools works, their options, streams etc?
> It just comes out of itself? :)

This isn't a script really but a shell function and this
function in particular is just a wrapper so no, you don't need
to know much more than the chaining of GNU tools there...

>> Everyone that writes it can also combine a bunch of shell
>> tools, but everyone who can combine a bunch of shell tools
>> can't write that - many of them can't program at
>> all, actually.
>
> I don't think I or anyone else claimed that "everyone who
> writes it" (it = shellscripts?)

Putting together a bunch of shell tools with pipes in between
to do some parsing, that's much more easy than to write Elisp.

Shell tools are on the user level, not on the
programmer/engineer level.

> By the way, you do realize that we write this in context of
> Emacs and Elisp and not some random unix tooling context?

Yes but no, what?

> Yes, unix command line tools and piping are like lego blocks, that
> was by design, it does not mean that *everyone* can write shell
> scripts. Everyone *can learn* to write shell scripts, but not everyone
> can write shellscripts.

Forget about the shell script, it is just a wrapper, an
interface for convenience. No, what it amounts to is the use
and combination of 3 tools. (BTW I didn't get the other guy's
suggestion to work, that which only used awk and nothing else
- well, that might be better (I agree) but as for how
difficult it is it is probably *more* difficult than mine
because his requires some understanding of awk beyond the
most basic "pile together a bunch of common tool with their
common/very simple and familiar options".)

So again there is no shell programming, just awk (gawk(1)),
sort(1) and tail(1).

  $ awk '{ print length($0) " " $0; }' $file | sort -n | tail -1

> I hope you realize the difference. And that hypothetical
> *everyone* can also learn how to write elisp if they choose
> so. By the way you know what is also like lego blocks?
> Lisp functions :).

True but that Lego is too difficult for a lot of people while
everyone can pipe together three shell tools.

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2021-08-13 23:42 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-13  7:12 Too fine design granularity leads to numerous macro/function/command existed in Emacs Hongyi Zhao
2021-08-13  7:25 ` Eli Zaretskii
2021-08-14  0:46   ` Hongyi Zhao
2021-08-14  6:18     ` Eli Zaretskii
2021-08-14  6:29       ` Hongyi Zhao
2021-08-14  7:18         ` Eli Zaretskii
2021-08-14  7:25           ` Hongyi Zhao
2021-08-14  7:47             ` Eli Zaretskii
2021-08-13  7:57 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-13  8:34   ` Hongyi Zhao
2021-08-13  8:56     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-13  9:20       ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-13  9:26 ` Arthur Miller
2021-08-13 10:11   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-13 13:00     ` [OFF TOPIC] Algorithms (was: Re: Too fine design granularity leads to numerous macro/function/command existed in Emacs.) 2QdxY4RzWzUUiLuE
2021-08-13 13:07       ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-13 13:17         ` Yuri Khan
2021-08-13 13:26           ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-13 13:48     ` Too fine design granularity leads to numerous macro/function/command existed in Emacs Arthur Miller
2021-08-13 18:21       ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-13 20:47         ` Arthur Miller
2021-08-13 23:42           ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-08-14  0:24             ` Hongyi Zhao
2021-08-14  0:42               ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-14  1:02                 ` Hongyi Zhao
2021-08-14  2:18                   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-14  1:46             ` Arthur Miller
2021-08-13 23:49         ` Hongyi Zhao
2021-08-13 23:54           ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-13 14:15   ` Eli Zaretskii
2021-08-13 14:42     ` Arthur Miller
2021-08-13 15:59       ` Eli Zaretskii
2021-08-13 17:09         ` Arthur Miller
2021-08-13 18:16       ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-13 23:40       ` Hongyi Zhao
2021-08-13 23:45         ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-13 23:57           ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-13 23:47         ` Emanuel Berg via Users list for the GNU Emacs text editor

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=871r6w7vyi.fsf@zoho.eu \
    --to=help-gnu-emacs@gnu.org \
    --cc=moasenwood@zoho.eu \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.