| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 8 months |
| seen | Nov 30 '12 at 20:12 | |
| stats | profile views | 14 |
|
Nov 27 |
comment |
Building Qt: 'make clean' causes everything to get recompiled? Well, I think my main problem was that I thought what you were trying to explain was "already" a make distcleanand not make clean. I had assumed make clean to be a lot less "drastic". :) Obviously I was wrong. |
|
Nov 27 |
comment |
Building Qt: 'make clean' causes everything to get recompiled? Yeah, you're right: that demos/examples stuff is indeed a very huge part of the story. Saved me lots of time indeed. I knew that already, but thanks for pointing it out anyway. :) |
|
Oct 13 |
revised |
Building Qt: 'make clean' causes everything to get recompiled? added 5 characters in body; edited tags |
|
Oct 13 |
asked | Building Qt: 'make clean' causes everything to get recompiled? |
|
Oct 5 |
comment |
ls: Do not show directories that match same pattern in wildcard searches, only files Ah! I should have thought about greping for ^d. I didn't think of that, obviously. Thank you. |
|
Oct 5 |
accepted | ls: Do not show directories that match same pattern in wildcard searches, only files |
|
Oct 5 |
comment |
ls: Do not show directories that match same pattern in wildcard searches, only files Thanks. That's better than nothing, in any case. |
|
Oct 5 |
comment |
ls: Do not show directories that match same pattern in wildcard searches, only files There is actually nothing much to "edit". So again: I want the tax* files in the current directory to be listed, but the directory "invoices2010" which resides in the same working directory and which also matches the given *2010* wildcard pattern should be skipped in the listing. |
|
Oct 5 |
comment |
ls: Do not show directories that match same pattern in wildcard searches, only files No, it would not be a good start at all. In my example, I wish to have the tax* files listed, whilst your solution would simply list all directories that match the pattern without showing their file content. That's something completely different. |
|
Oct 5 |
revised |
ls: Do not show directories that match same pattern in wildcard searches, only files added 55 characters in body |
|
Oct 5 |
asked | ls: Do not show directories that match same pattern in wildcard searches, only files |
|
Sep 29 |
comment |
What is the purpose of the lost+found folder in Linux and Unix? Valid point, however: these CAN become quite a nuisance anyway. For example, when trying to to a find operation on one or many ext[2|3|4] partition(s) from a non-admin user's account, you will always get these entirely unnecessary "permission denied" errors. Certainly, there are ways to circumvent those kinds of errors - but it's a bit awkward because the standard find . -name '*whatever*' won't do the trick. |
|
Sep 29 |
awarded | Analytical |
|
Sep 29 |
accepted | Passing parsed output of sed to find (in this direction) |
|
Sep 29 |
comment |
Auto-expansion problem with array elements containing an '*' (asterisk) @Serge I was well aware of the grep -v pipe "solution" from the beginning, even before opening this question. However, please try to start thinking of real huge directory trees, and what significant differences in completion time you might eventually be encountering! This could even sum up to whole minutes of difference in the long run. |
|
Sep 29 |
awarded | Scholar |
|
Sep 29 |
accepted | Auto-expansion problem with array elements containing an '*' (asterisk) |
|
Sep 29 |
comment |
Auto-expansion problem with array elements containing an '*' (asterisk) In one word: FANTASTIC! I would never have been able to pull all that off by myself (yet), because I'm still learning the advanced stuff like functions and arrays (after considering myself safe enough in the basics, which took way longer than I had expected). Thank you very much, your approach looks as if taken from a textbook. |
|
Sep 28 |
awarded | Commentator |
|
Sep 28 |
comment |
Auto-expansion problem with array elements containing an '*' (asterisk) Upvote - OK done, but I don't want to put the check-mark on it yet because it might give the impression that the question might be in a sort of "closed" state. Several approaches are usually a better way of learning new things and ways, though. |