find files based on extension but display name without extension no basename, sed, awk, grep or ; allowed

Question

I need to write a script that lists all the files with a .gif extension in the current directory and all its sub-directories BUT DO NOT use ANY of:

basename
grep
egrep
fgrep
rgrep
&&
||
;
sed
awk

AND still include hidden files.

I tried find . -type f -name '*.gif' -printf '%f\n' which will succesfully display .gif files, but still shows extension. Here's the catch: if I try to use cut -d . -f 1 to remove file extension, I also remove hidden files (which I don't want to) because their names start with ".".

Then I turned to use tr -d '.gif' but some of the files have a 'g' or a '.' in their name.

I also tried to use some of these answers BUT all of them include either basename, sed, awk or use some ";" in their script.

With so many restrictions I really don't know if it's even possible to achieve that but I'm supposed to.

How would you do it?

Why are you not allowed to use `;` ? looks odd requirement. Is it homework ? — Gilles Quénot, Feb 16 '23 at 06:15
`tr` is completely wrong; your command will remove all occurrences of `.` or `g` or `i` or `f` — tripleee, Feb 16 '23 at 06:23
Please review [homework guidance](https://meta.stackoverflow.com/questions/334822/how-do-i-ask-and-answer-homework-questions) — tripleee, Feb 16 '23 at 06:35

Gilles Quénot · Accepted Answer · 2023-02-16T06:30:57.320

1

files/dirs structure:

$ tree -a
.
├── bar
├── bar.gif
├── base
│   └── foo.gif
├── foo
│   └── aaa.gif
└── .qux.gif

3 directories, 4 files

Code

find -type f -name '*.gif' -exec bash -c 'printf "%s\n" "${@%.gif}"' bash {} +

Output

./bar
./.qux
./foo/aaa
./base/foo

Explanations

Parameter Expansion expands parameters: $foo, $1. You can use it to perform string or array operations: "${file%.mp3}", "${0##*/}", "${files[@]: -4}". They should always be quoted. See: http://mywiki.wooledge.org/BashFAQ/073 and "Parameter Expansion" in man bash. Also see http://wiki.bash-hackers.org/syntax/pe.

edited Feb 16 '23 at 06:30

answered Feb 16 '23 at 05:48

Gilles Quénot

173,512
41
224
223

The thing is, the for loop has a ";" in it, and I'm not allowed to use that character in my script. I forgot to mention the script should be one line long. – Darvid Feb 16 '23 at 05:49
Code edited accordingly – Gilles Quénot Feb 16 '23 at 06:02
Using `+` instead of `;` is kind of cheating I guess; but the question is so bad it probably deserves it. – tripleee Feb 16 '23 at 06:34

Jetchisel · Answer 2 · 2023-02-16T06:07:54.193

0

Something like:

find . -name '*.gif' -type f -execdir bash -c 'printf "%s\n" "${@%.*}"' bash {} +

edited Feb 16 '23 at 06:07

answered Feb 16 '23 at 05:52

Jetchisel

7,493
2
19
18

1

I read that it's best to avoid using anything other than "bash" as a placeholder (`_` here). It's about error handling – Gilles Quénot Feb 16 '23 at 06:07
Then `bash` it is! :-) – Jetchisel Feb 16 '23 at 06:08

score 0 · Answer 3 · answered Feb 16 '23 at 06:45

0

Using perl:

perl -MFile::Find::Rule -E '
    say s/\.gif$//r for File::Find::Rule
        ->file()
        ->name(qr/\.gif\z/)
        ->in(".")
'

Output:

bar
.qux
foo/aaa
base/foo

answered Feb 16 '23 at 06:45