Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7801893
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 2, 20262026-06-02T01:05:18+00:00 2026-06-02T01:05:18+00:00

In bash, when I want to iterate in a recursive list of pdf files,

  • 0

In bash, when I want to iterate in a recursive list of pdf files, without the extension, I could do the following:

for file in `find mypath -type f -name '*.pdf' -printf "%f\n"`
do
    echo "${file%.*}"
done

This works perfectly, and I get a list of the pdf files without the extension.

But if I try to do the same in a Makefile, I get empty output:

my_test:
    @for file in `find mypath -type f -name '*.pdf' -printf "%f\n"`; \
    do \
        echo "${file%.*}"; \
    done; \

do you have an idea why this is happening?
thanks in advance

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-02T01:05:21+00:00Added an answer on June 2, 2026 at 1:05 am

    Just put in an extra $:

    echo "$${file%.*}"; \
    

    In your command Make expands the first $, interprets ${ as nothing, and things unravel fast. With $$, the first $ escapes the second and the ${...} gets passed to the shell.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

i want that my bash script does the following: It finds a file, for
In bash script, I want to iterate over a list of values that I
I want to execute a bash script on a list of text files (using
I want to parse XML in bash and xpath could do it. (To get
I want to run the following bash command in Python 3: ls -l I
I want to define a bash alias named kill3000 to automate the following task:
I want to use bash to process a tab delimited file. I only need
In a bash script, I want to iterate over all the directories in the
In bash I want to return file name (and the path to the file)
I want to add a variable ${date} in the following bash script: ffmpeg -i

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.