Simon Josefsson <[EMAIL PROTECTED]> wrote:
> Here are updated tests. They test several corner cases, but still not
> comprehensive.
Thank you!
Applied.
2006-02-27 Jim Meyering <[EMAIL PROTECTED]>
* tests/misc/base64: Factor out a long constant string.
Split lines to stay withi
Jim Meyering <[EMAIL PROTECTED]> writes:
> Simon Josefsson <[EMAIL PROTECTED]> wrote:
>
>> Jim Meyering <[EMAIL PROTECTED]> writes:
>>
>>> Simon Josefsson <[EMAIL PROTECTED]> wrote:
Here are updated tests. They test several corner cases, but still not
comprehensive.
>>>
>>> Thank you!
>
Why all the duplicate deliveries today?
Cheers,
Phil
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
Jim Meyering <[EMAIL PROTECTED]> writes:
>>> Would you please write a test script to go along with that?
>>> I'd prefer that you model the new file, say tests/misc/base64,
>>> after one of the existing ones that uses the Coreutils.pm module.
>>> For example, tests/misc/expand is nice and small.
>>
Simon Josefsson <[EMAIL PROTECTED]> wrote:
> Jim Meyering <[EMAIL PROTECTED]> writes:
>
>> Simon Josefsson <[EMAIL PROTECTED]> wrote:
>>> Here are updated tests. They test several corner cases, but still not
>>> comprehensive.
>>
>> Thank you!
>> Applied.
>
> With the patch below, it builds and p
Simon Josefsson <[EMAIL PROTECTED]> wrote:
> Jim Meyering <[EMAIL PROTECTED]> writes:
>> Plus, I indented a few cpp directives in lib/base64.h,
>> to make them consistent with the first #define.
>
> I feeded gnulib with these.
Thanks!
>> Would you please write a test script to go along with that?
Simon Josefsson <[EMAIL PROTECTED]> wrote:
> Here is an updated patch for Coreutils to provide the base64 command.
>
> I believe I have addressed all major comments given earlier, I'm
> Cc:ing all people who helped me, maybe they can help review it again.
>
> The lib/base64.? files are from gnulib.
Jim Meyering <[EMAIL PROTECTED]> writes:
> Simon Josefsson <[EMAIL PROTECTED]> wrote:
>> Here is an updated patch for Coreutils to provide the base64 command.
>>
>> I believe I have addressed all major comments given earlier, I'm
>> Cc:ing all people who helped me, maybe they can help review it ag
Here is an updated patch for Coreutils to provide the base64 command.
I believe I have addressed all major comments given earlier, I'm
Cc:ing all people who helped me, maybe they can help review it again.
The lib/base64.? files are from gnulib.
Warning: it has not been tested much at all!
Thank
Simon Josefsson wrote:
> > As for whether choosing on "base64 abc" whether abc is the filename
> > containing text to be encoded, or the actual text to be encoded, I would
> > lean towards filenames.
>
> Me too. The tool started out as a debugging tool for me, but it is
> not the typical use. A
[EMAIL PROTECTED] (Eric Blake) writes:
>> The RFC is fuzzy on the issue, but I want to discourage too lax
>> treatment of encoded data. Lax treatment create opportunities for
>> side channel attacks, and make implementations complex since they have
>> to deal with various ill-formed input. So wi
> The RFC is fuzzy on the issue, but I want to discourage too lax
> treatment of encoded data. Lax treatment create opportunities for
> side channel attacks, and make implementations complex since they have
> to deal with various ill-formed input. So without --wrap, I
> definitely think the file
Eric Blake <[EMAIL PROTECTED]> writes:
> According to Simon Josefsson on 6/27/2005 3:55 PM:
>>
>> -w is for encoding, -i for decoding. So they are orthogonal. I
>> thought about making -w affect decoding to, so decoding would ignore
>> (only) newlines after COLS. Could be fixed later on.
>
> I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Simon Josefsson on 6/27/2005 3:55 PM:
>
> -w is for encoding, -i for decoding. So they are orthogonal. I
> thought about making -w affect decoding to, so decoding would ignore
> (only) newlines after COLS. Could be fixed later on.
I w
Paul Eggert <[EMAIL PROTECTED]> writes:
>> [EMAIL PROTECTED] [EMAIL PROTECTED]
>> [EMAIL PROTECTED] [EMAIL PROTECTED]
>> [EMAIL PROTECTED] -w
>> [EMAIL PROTECTED] --wrap
>> [EMAIL PROTECTED] wrap data
>> [EMAIL PROTECTED] column to wrap data after
>> +During encoding, wrap lines after @var{COLS} c
Thanks for writing that. Here's a quick review.
Simon Josefsson <[EMAIL PROTECTED]> writes:
> +The base64 encoding expand data to roughly 133% of the original.
expand -> expands
> [EMAIL PROTECTED] [EMAIL PROTECTED]
> [EMAIL PROTECTED] [EMAIL PROTECTED]
> [EMAIL PROTECTED] -w
> [EMAIL PROTECTE
Eric Blake <[EMAIL PROTECTED]> writes:
> s/provide/provides/
> s/transform/transforms/
> s/expand/expands/
Fixed, thanks! I really need a flygrammar.el. Or some english
classes.
>> [EMAIL PROTECTED] [EMAIL PROTECTED]
>> [EMAIL PROTECTED] [EMAIL PROTECTED]
>> [EMAIL PROTECTED] -w
>> [EMAIL PROT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Simon Josefsson on 6/25/2005 7:32 AM:
> +++ NEWS 25 Jun 2005 13:28:40 -
> @@ -167,6 +167,11 @@ GNU coreutils NEWS
>stat -f's default output format has been changed to output this size as
> well.
>sta
Simon Josefsson <[EMAIL PROTECTED]> writes:
> Jim Meyering <[EMAIL PROTECTED]> writes:
>
>> Simon Josefsson <[EMAIL PROTECTED]> wrote:
>> ...
>>> I'll volunteer to submit a patch and documentation for the tool if you
>>> think it could be added.
>>
>> Ok. That sounds fair.
>> If you can add some
Jim Meyering <[EMAIL PROTECTED]> writes:
> Simon Josefsson <[EMAIL PROTECTED]> wrote:
> ...
>> I'll volunteer to submit a patch and documentation for the tool if you
>> think it could be added.
>
> Ok. That sounds fair.
> If you can add some tests too, that'd be great.
> If so, please use somethi
Jim Meyering <[EMAIL PROTECTED]> writes:
>> Is a base64 encode/decode tool suitable for coreutils?
>
> As Padraig noted, GNU recode does this:
>
> $ echo foo|recode ../64
> Zm9vCg==
> $ echo foo|recode ../64|recode /64
> foo
>
> but I find the syntax to be obscure.
> And it's not always av
Simon Josefsson <[EMAIL PROTECTED]> wrote:
...
> I'll volunteer to submit a patch and documentation for the tool if you
> think it could be added.
Ok. That sounds fair.
If you can add some tests too, that'd be great.
If so, please use something like coreutils/tests/md5sum/basic-1 as a model.
__
recode does this:
>
> $ echo foo|recode ../64
> Zm9vCg==
> $ echo foo|recode ../64|recode /64
> foo
>
> but I find the syntax to be obscure.
> And it's not always available.
Agreed.
FWIW, I have written a base64 tool to satisfy my needs. It is based
on the coreu
On Tue, 21 Dec 2004, Simon Josefsson wrote:
>I was looking for something simpler, preferably the tool should even be
>called 'base64' so TAB completion works. Perhaps base64 is not yet as
>widely used to motivate it being part of coreutils, though. Just
>because I often need such a tool doesn't
[EMAIL PROTECTED] writes:
> Simon Josefsson wrote:
>> Is a base64 encode/decode tool suitable for coreutils?
>> I typically use `M-: (base64-encode-string "foo")' in Emacs, but I
>> have found I often want a command line tool as well. And `echo
>> foo|base64' is easier to type.
>> There is a base
> Is a base64 encode/decode tool suitable for coreutils?
As Padraig noted, GNU recode does this:
$ echo foo|recode ../64
Zm9vCg==
$ echo foo|recode ../64|recode /64
foo
but I find the syntax to be obscure.
And it's not always available.
___
B
On Tue, Dec 21, 2004 at 12:25:56PM +0100, Simon Josefsson wrote:
> I'm thinking:
>
> Usage: base64 [OPTION] [FILE]...
> Encode binary data using printable characters.
> With no FILE, or when FILE is -, read standard input.
Alternatively, we could use a two-line Perl script with MIME::Decoder.
J
Simon Josefsson wrote:
Is a base64 encode/decode tool suitable for coreutils?
I typically use `M-: (base64-encode-string "foo")' in Emacs, but I
have found I often want a command line tool as well. And `echo
foo|base64' is easier to type.
There is a base64 module in gnulib that I think would be su
Is a base64 encode/decode tool suitable for coreutils?
I typically use `M-: (base64-encode-string "foo")' in Emacs, but I
have found I often want a command line tool as well. And `echo
foo|base64' is easier to type.
There is a base64 module in gnulib that I think would be suitable for
this. It
29 matches
Mail list logo
