Hi Chet,
> > On 7/18/2011 10:14 AM, Ralph Corderoy wrote:
> > > Is this happening because the built-in printf is using putchar(3)
> > > in the PC() macro and stdio thinks file descriptor 1 is still to a
> > > tty so it's persisting in line buffering? It would seem nicer if
> > > fewer write(2)s w
On 7/18/11 10:46 AM, Steven W. Orr wrote:
> On 7/18/2011 10:14 AM, Ralph Corderoy wrote:
>> Hi,
>>
>> (I'm not subscribed to the list so please keep me CC'd.)
>>
>> Consider
>>
>> printf 'foo bar\n'>/dev/udp/localhost/4242
>>
>> with bash's printf built-in, it works fine. One packet is sent.
On Mon, Jul 18, 2011 at 10:46:19AM -0400, Steven W. Orr wrote:
> On 7/18/2011 10:14 AM, Ralph Corderoy wrote:
>> printf 'foo\nbar\n'>/dev/udp/localhost/4242
>>
>> and two packets are sent, one per line. If the aim is to send a string
>> of data in one packet this causes problems.
>>
>> Using
On 7/18/2011 10:14 AM, Ralph Corderoy wrote:
Hi,
(I'm not subscribed to the list so please keep me CC'd.)
Consider
printf 'foo bar\n'>/dev/udp/localhost/4242
with bash's printf built-in, it works fine. One packet is sent.
However, make that two lines
printf 'foo\nbar\n'>/dev/udp/l
Hi,
(I'm not subscribed to the list so please keep me CC'd.)
Consider
printf 'foo bar\n' >/dev/udp/localhost/4242
with bash's printf built-in, it works fine. One packet is sent.
However, make that two lines
printf 'foo\nbar\n' >/dev/udp/localhost/4242
and two packets are sent, one pe
> Try like this:
>
> [bash-4.2.8] # set -o vi
> [bash-4.2.8] # bind -m vi-insert '"jj": "\e"'
> [bash-4.2.8] # echo jk
> [bash-4.2.8] # echo k
> [bash-4.2.8] #
>
> Then press ctrl-r and enter jk to search. It'll find ``echo k'' instead of
> ``echo jk''. Bug?
Thanks for the report. Yes, it's a b
On 7/16/11 4:21 PM, Jonathan Nieder wrote:
> Chet Ramey wrote:
>
>> The man page copyright belongs to me -- I don't know that I ever
>> assigned it to the FSF. I don't have a problem with others modifying the
>> man page, and expect it under certain circumstances. For instance, if a
>> distribut
