Andreas Schwab wrote:
> Jim Meyering writes:
>> @@ -2424,11 +2424,11 @@ pr invocation
>> Optional argument @var{number-separator} is the character appended to
>> the line number to separate it from the text followed. The default
>> separator is the TAB character. In a strict sense a TAB is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[please don't top-post]
According to Aaron Peterson on 12/7/2008 10:59 AM:
> Thanks for the sed tip.
> One of the requirements is ability to edit the list.
> I think there is an escape all unusual characters option in ls..
- --quote-name, --quoting-s
Thanks for the sed tip.
One of the requirements is ability to edit the list.
I think there is an escape all unusual characters option in ls.. I
didn't see one for find.
I forgot that backspace, etc are keys... joy. I need it fully escaped
from the beginning.
-AP
On Sun, Dec 7, 2008 at 6:17 AM,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[Please keep the list in the loop, and please don't top-post]
According to Aaron Peterson on 12/7/2008 3:35 AM:
> Yes, scripts can be made. I'm pretty much sure that the guy on the
> debian list was planning to manually prune the files listed. I just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Aaron Peterson on 12/6/2008 3:05 PM:
> Ultimately, I find it annoying that more options are needed than this:
>find "*want*" | du
> For the utilities to work properly they would need to know their
> context and I believe that everybody
Aaron Peterson wrote:
> I had no idea that this specifically was a security risk.
It isn't this specifically. It is this generally. :-)
> I do remember one of my friends explaining how other characters could
> be used as seporators,
There are two characters which are invalid within a filename.
I had no idea that this specifically was a security risk.
I do remember one of my friends explaining how other characters could
be used as seporators, and that if I have files with dashes in them
and do a * that the shell expands that it tries to interpret it as an
option...
It looks like the doc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 12/6/2008 8:06 AM:
>> this by determining what the (possibly multi byte) newline sequence is
>> and make a --from-files work?
>
> --from-files0 (although, the way getopt works, you can use unambiguous
> abbreviations, so --f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Aaron Peterson on 12/6/2008 2:16 AM:
> Wow, You guys seem to really care.
>
> 6.10 is the version of du that I'm using. (Ubuntu Ibex)
6.12 is the latest stable version, and 7.0 is also available for testing.
> So, I understand that ne
Wow, You guys seem to really care.
6.10 is the version of du that I'm using. (Ubuntu Ibex)
I understand enough now to get my task done using existing tools, and
it looks like ya'll fixed some documentation as well.
(There are many newer messages that I'm not reading fully)
So, I understand th
Hello Pádraig,
Pádraig Brady draigBrady.com> writes:
> Note `make check` took about 2 hours due to the very slow msgmerge,
> and I checked in anyway as I thought I couldn't break anything
> with a simple doc emhancement :)
Use msgmerge from CVS gettext. It is roughly 10 times faster for
coreuti
Pádraig Brady wrote:
> Jim Meyering wrote:
>> No problem.
>> BTW, I've already fixed it, but forgot to mention it in the log text.
>
> Noticed that, thanks.
>
> On a related note, would the attached patch be useful,
> as I found inconsistent descriptions of ASCII NUL
> throughout the info doc.
O
Jim Meyering wrote:
>
> No problem.
> BTW, I've already fixed it, but forgot to mention it in the log text.
Noticed that, thanks.
On a related note, would the attached patch be useful,
as I found inconsistent descriptions of ASCII NUL
throughout the info doc.
cheers,
Pádraig.
>From 3557a0e286fe
Jim Meyering <[EMAIL PROTECTED]> writes:
> @@ -2424,11 +2424,11 @@ pr invocation
> Optional argument @var{number-separator} is the character appended to
> the line number to separate it from the text followed. The default
> separator is the TAB character. In a strict sense a TAB is always
> -
Pádraig Brady <[EMAIL PROTECTED]> wrote:
> Jim Meyering wrote:
>> Pádraig Brady <[EMAIL PROTECTED]> wrote:
>>> I also did a non user visible change to the info docs while I was
>>> at it to standardize on using lower-case @var{file}:
>>>
>>> http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=co
Jim Meyering wrote:
> Pádraig Brady <[EMAIL PROTECTED]> wrote:
>> I also did a non user visible change to the info docs while I was
>> at it to standardize on using lower-case @var{file}:
>>
>> http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=1ce9d86c308d7daa6271a2e87629984b153ee9
Pádraig Brady <[EMAIL PROTECTED]> wrote:
> I also did a non user visible change to the info docs while I was
> at it to standardize on using lower-case @var{file}:
>
> http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=1ce9d86c308d7daa6271a2e87629984b153ee9da
Thanks!
For a general
Aaron Peterson wrote:
> Hi,
> A feature request for du, a way to sum from a list of files without
> doing tr \n \0
Supporting --files-from would be less general.
Is `tr '\n' '\0'` that onerous?
> I had to sort some files and and needed to know how large the group of
> files that I had found we
Aaron Peterson wrote:
> I spend many hours trying to figure this out / and searching for solution.
> It turns out that the \0 delimited list requirement was very painful.
> I wish I could cat the output of find into du and get the total
It's meant to be used like:
$ find . -type f -print0 | du
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Aaron Peterson on 11/30/2008 5:16 PM:
> Hi,
> A feature request for du, a way to sum from a list of files without
> doing tr \n \0
Thanks for the report. You didn't mention which version of du you are
using. du has supported the optio
20 matches
Mail list logo
