[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GNU make troubleshooting
From: |
Bruno Haible |
Subject: |
Re: GNU make troubleshooting |
Date: |
Mon, 10 Jul 2023 21:18:29 +0200 |
Paul Smith wrote:
> It's not acceptable (to me) to only show the one newest file, not all
> files that are newer than the target, because often you want to know
> all the newer files.
You say "It's not acceptable (to me) to only show the one newest file",
and I say "A tool that shows me 3.7 KB worth of file names in one line
is useless to me, because that is information overload, and I don't
have good filtering skills".
It's a bit like one gdb user saying "I want to see the values of all
local variables on the stack, because I often need them" and another
person saying "If the output is 100 lines long or longer, you lost me".
How about introducing _options_ whose goal is not to produce maximal
information, but small-sized and still useful information?
Bruno
- GNU make troubleshooting, Bruno Haible, 2023/07/10
- Re: GNU make troubleshooting, Bruno Haible, 2023/07/10
- Re: GNU make troubleshooting, Paul Smith, 2023/07/10
- Re: GNU make troubleshooting, Bruno Haible, 2023/07/10
- Re: GNU make troubleshooting, Paul Smith, 2023/07/10
- Re: GNU make troubleshooting, Bruno Haible, 2023/07/10
- Re: GNU make troubleshooting, Paul Smith, 2023/07/10
- Re: GNU make troubleshooting, Bruno Haible, 2023/07/10
- Re: GNU make troubleshooting,
Bruno Haible <=
- Re: GNU make troubleshooting, Paul Smith, 2023/07/10
Re: GNU make troubleshooting, Paul Smith, 2023/07/10
Re: GNU make troubleshooting, Jeffrey Walton, 2023/07/10