On Tue, Oct 7, 2014 at 2:25 AM, Dave Rutherford
wrote:
**it.. sorry for the fat finger post. Gmail puts the tiny formatting options
right next to the big SEND button. Ratzen fracken.
On Tue, Oct 7, 2014 at 2:07 AM, Linda Walsh wrote:
>
>
> Pierre Gaston wrote:
>
>>
>> b=<<<$a is not doing anything so I wonder how much value this example has.
>>
> ---
> I wondered about that.. think that was meant to be the
> b=<<<($a) w/o the copy that greg said was pointless.
>
>>
>> A pipe
Pierre Gaston wrote:
b=<<<$a is not doing anything so I wonder how much value this example has.
---
I wondered about that.. think that was meant to be the
b=<<<($a) w/o the copy that greg said was pointless.
A pipe means 2 different processes, a tempfile for a heredoc does not.
First)
On Tue, Oct 7, 2014 at 12:00 AM, Linda Walsh wrote:
According to Chet , only way to do a multi-var assignment in bash is
>
>
>>> read a b c d <<<$(echo ${array[@]})
>>>
>>
>> The redundant $(echo...) there is pretty bizarre. Then again, that
>> whole command is strange. You have a nice friendl
Greg Wooledge wrote:
netdev_pat=... # (and other variable assignments)
(cd "$sysnet" &&
for ifname in ...; do
hwaddr=$(<"$ifname"/address)
act_hw2if[$hwaddr]="$ifname"
act_if2hw[$ifname]="$hwaddr"
done)
Except that either act_hw2if + pair were just assigned to
in the sub process t
On 10/6/2014 6:43 AM, Chet Ramey wrote:
On 10/6/14, 1:35 AM, tsugutomo.en...@jp.sony.com wrote:
Hi,
+ char *
+ parser_remaining_input ()
+ {
+ if (shell_input_line == 0)
+ return 0;
+ if (shell_input_line_index < 0 || shell_input_line_index >=
shell_input_line_len)
+ return '\0';
Not sure how but this went off into space, sorta...
Greg Wooledge wrote:
On Mon, Oct 06, 2014 at 12:14:57PM -0700, Linda Walsh wrote:
done <<<"$(get_net_IFnames_hwaddrs)"
Where am I using a HERE doc?
<<< and << both create temporary files.
Yeah... where?
assign_netif_nam
Greg Wooledge wrote:
On Mon, Oct 06, 2014 at 02:00:47PM -0700, Linda Walsh wrote:
How much of the original do you want?... wait... um...
But the point it it should already work... I think it is trying to read
from the network.
In the code below, you have a function that *generates* a str
On Mon, Oct 06, 2014 at 02:00:47PM -0700, Linda Walsh wrote:
> How much of the original do you want?... wait... um...
> But the point it it should already work... I think it is trying to read
> from the network.
In the code below, you have a function that *generates* a stream of
data out of va
Greg Wooledge wrote:
On Mon, Oct 06, 2014 at 12:38:21PM -0700, Linda Walsh wrote:
According to Chet , only way to do a multi-var assignment in bash is
read a b c d <<<$(echo ${array[@]})
The redundant $(echo...) there is pretty bizarre. Then again, that
whole command is strange. You have
On Mon, Oct 06, 2014 at 12:38:21PM -0700, Linda Walsh wrote:
> According to Chet , only way to do a multi-var assignment in bash is
>
> read a b c d <<<$(echo ${array[@]})
The redundant $(echo...) there is pretty bizarre. Then again, that
whole command is strange. You have a nice friendly arra
On Mon, Oct 6, 2014 at 10:38 PM, Linda Walsh wrote:
> Greg Wooledge wrote:
>
>> On Mon, Oct 06, 2014 at 12:14:57PM -0700, Linda Walsh wrote:
>>
>>>done <<<"$(get_net_IFnames_hwaddrs)"
>>>
>>
>> Where am I using a HERE doc?
>>>
>>
>> <<< and << both create temporary files.
>>
>
>
> According
Greg Wooledge wrote:
On Mon, Oct 06, 2014 at 12:14:57PM -0700, Linda Walsh wrote:
done <<<"$(get_net_IFnames_hwaddrs)"
Where am I using a HERE doc?
<<< and << both create temporary files.
According to Chet , only way to do a multi-var assignment in bash is
read a b c d <<<$(echo ${a
On Mon, Oct 06, 2014 at 12:14:57PM -0700, Linda Walsh wrote:
>done <<<"$(get_net_IFnames_hwaddrs)"
> Where am I using a HERE doc?
<<< and << both create temporary files.
In running a startup script, I am endeavoring not to use tmp files
where possible, As part of this, I sent the output of a command
to stdout where I read it using the "variable read" syntax:
while read ifname hwaddr; do
printf "ifname=%s, hwaddr=%s\n" "$ifname" "$hwaddr"
act_hw2i
Thank you for the clarification.
--
Sent from my iPad
> On Oct 6, 2014, at 4:12 AM, Chet Ramey wrote:
>
>> On 10/5/14, 9:45 PM, Ryan Cunningham wrote:
>> This patch contains statements that add references to the patch directory,
>> "bash-4.3-patched". You should reissue the patch without such
Dear Chet,
Thanks for your kind answer! Then I'm going to try to open these bugs for
RedHat and Debian.
Good byte! Tamás
-Original Message-
From: Chet Ramey [mailto:chet.ra...@case.edu]
Sent: Monday, October 06, 2014 1:52 PM
To: Tajthy, Tamas; bug-bash@gnu.org
Cc: chet.ra...@case.edu
Su
On 10/6/14, 4:04 AM, Tajthy, Tamas wrote:
> Hi,
>
> I have a minor issue with the newest bash-3.2-33.el5_11.4 (RedHat) package.
> Same happens on Debian Wheezy (unfortunately I do not know that version
> number now).
>
> I usually define in my .bash_profile some functions called "..", "...",
>
On 10/6/14, 1:35 AM, tsugutomo.en...@jp.sony.com wrote:
> Hi,
>
>> + char *
>> + parser_remaining_input ()
>> + {
>> + if (shell_input_line == 0)
>> + return 0;
>> + if (shell_input_line_index < 0 || shell_input_line_index >=
>> shell_input_line_len)
>> + return '\0'; /* XXX */
>
>
On 10/5/14, 9:45 PM, Ryan Cunningham wrote:
> This patch contains statements that add references to the patch directory,
> "bash-4.3-patched". You should reissue the patch without such statements if
> you find it feasible to do so.
Why? I want those pathnames in there, rather than the ones that
Hi,
> + char *
> + parser_remaining_input ()
> + {
> + if (shell_input_line == 0)
> + return 0;
> + if (shell_input_line_index < 0 || shell_input_line_index >=
> shell_input_line_len)
> + return '\0';/* XXX */
Do you mean return ""; ?
enami.
Hi,
I have a minor issue with the newest bash-3.2-33.el5_11.4 (RedHat) package.
Same happens on Debian Wheezy (unfortunately I do not know that version number
now).
I usually define in my .bash_profile some functions called "..", "...", ""
and so on. After the latest package was installed
22 matches
Mail list logo
