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: How to rename files to numbers in Eshell?
Date: Thu, 30 Sep 2021 09:50:00 +0200 [thread overview]
Message-ID: <87mtnumriv.fsf@zoho.eu> (raw)
In-Reply-To: YVVpRlO9NtwPZVdo@protected.localdomain
Jean Louis wrote:
> For me, shell scripts are in Elisp and usually used in Dired
> rather than Eshell.
>
> Pipes may be replaced by buffers, capturing information in
> a buffer and processing it thereafter.
Elisp and Bash are not close so one might as well start
over ...
If you insist, here are some zsh for you to practice on.
So tell me, what's the Elisp equivalent of:
#! /bin/zsh
create-100-meg-bogus-file () {
local file=${1:-100.data}
rm $file
dd if=/dev/urandom \
of=$file \
count=$(( 1024 * 100 )) \
bs=1024 | sha256sum | ( read rnd _; echo $rnd >> $file )
}
and
#! /bin/zsh
t () {
# check number of arguments
if [[ $# == 0 ]]; then
echo "syntax: $0 COMMAND" >&2
return
fi
local cmd=$1
find-zsh-command $cmd
# use whence; if a path, do 'ls'
local whence_hits
whence_hits=("${(@f)$(whence -ca $cmd | sed "s#$HOME#~#g")}")
local h
for h in $whence_hits; do
echo $h
ls -Ghl --color=auto $h 2> /dev/null
if [ -h $h ]; then
local dest=$(readlink -e $h)
set-fg-color 3
echo -n " * links to: "
reset-color
echo -n $dest '\n '
ls -Ghl --color=auto $dest
fi
done
# if a script, output it
cats $cmd
}
?
The whole file (323 lines)
https://dataswamp.org/~incal/conf/.zsh/files-fs
After that only ~99 more and you are all set :)
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2021-09-30 7:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-11 13:15 How to rename files to numbers in Eshell? Felix E. Klee
2021-09-11 13:40 ` Jean Louis
2021-09-12 8:44 ` Felix E. Klee
2021-09-12 19:03 ` Jean Louis
2021-09-13 9:28 ` Jean Louis
2021-09-13 11:52 ` tomas
2021-09-14 7:42 ` Felix E. Klee
2021-09-14 9:17 ` Jean Louis
2021-09-14 9:32 ` tomas
2021-09-14 11:11 ` Felix E. Klee
2021-09-14 13:37 ` Jean Louis
2021-09-14 15:48 ` Felix E. Klee
2021-09-16 22:37 ` Michael Heerdegen
2021-09-16 22:47 ` Michael Heerdegen
2021-09-17 7:27 ` Felix E. Klee
2021-09-24 7:21 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-25 13:43 ` Jean Louis
2021-09-26 2:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-30 6:38 ` Felix E. Klee
2021-09-30 7:37 ` Jean Louis
2021-09-30 7:50 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-09-30 13:17 ` Felix E. Klee
2021-09-30 15:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-30 21:42 ` Jean Louis
2021-10-01 0:09 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-01 20:51 ` Jean Louis
2021-10-01 21:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-02 7:53 ` Lack of integration in Emacs - it was " Jean Louis
2021-10-03 8:16 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-03 9:27 ` Jean Louis
2021-10-04 3:29 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-04 10:15 ` Jean Louis
2021-10-04 11:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-22 14:46 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-22 14:27 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-16 12:15 ` Felix E. Klee
2021-09-16 15:11 ` Nick Dokos
2021-09-16 16:07 ` Felix E. Klee
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=87mtnumriv.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.
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).