From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: Emanuel Berg <moasenwood@zoho.eu>,
help-gnu-emacs <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 08:24:32 +0800 [thread overview]
Message-ID: <CAGP6POJC2uuhDG3OuhDcCBi1eguDjjPrKfGpLeVibQ_72RqYfg@mail.gmail.com> (raw)
In-Reply-To: <871r6w7vyi.fsf@zoho.eu>
On Sat, Aug 14, 2021 at 7:43 AM Emanuel Berg via Users list for the
GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
> [...]
> 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".)
It's not difficult for me or maybe some others, just too lazy to think
for a while. After all, we have so many convenient uinx tools and the
excellent (but with performance penalty) pipe method at hand. Anyway,
I've presented a comparison between pure AWK and UNIX toolchains as
follows:
$ time awk 'length > max_length { max_length = length; longest_line =
$0 } END { print longest_line }' american-english-exhaustive
correspond with someone about someone or something correspond with
someone about someone or something
real 0m0.255s
user 0m0.255s
sys 0m0.003s
$ time awk '{ print length($0) " " $0; }' american-english-exhaustive
| sort -n | tail -1| cut -d ' ' -f2-
correspond with someone about someone or something correspond with
someone about someone or something
real 0m1.794s
user 0m1.853s
sys 0m0.053s
Obviously, the former is about 6 times faster than the latter.
> 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.
Hongyi
next prev parent reply other threads:[~2021-08-14 0:24 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
2021-08-14 0:24 ` Hongyi Zhao [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGP6POJC2uuhDG3OuhDcCBi1eguDjjPrKfGpLeVibQ_72RqYfg@mail.gmail.com \
--to=hongyi.zhao@gmail.com \
--cc=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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).