Sh/Bash

Newsgroups: comp.unix.shell

^l = clear screen
^c = clear line
^m = enter
^o = enter
^j = enter
^a = go to beginning of line
^e = go to end of line
^d = delete char under cursor ( delete forwards )
^h = delete char defore cursor ( delete backwards )
^8 = delete char defore cursor ( delete backwards )
^w = delete from char before cursor till beginnng of this word
^u = delete from char before cursor till beginnng of line
^k = delete from char under cursor till end of line
^7 = undo
^p = arrow up ( previous )
^n = arrow down ( next )
^b = arrow left  ( back )
^f = arrow right ( forward )
^t = exchange two chars before cursor
^r = search in bash history
^q = clear input buffer in case someting is broken !

bash$ echo aaa bbb ccc ddd | xargs1 | sort -r
ddd
ccc
bbb
aaa

bash$ ^aaa^111^
echo 111 bbb ccc ddd | xargs1 | sort -r
ddd
ccc
bbb
111
  -- how to replace

bash$ ^xargs1^xargs -n 1^
echo 111 bbb ccc ddd | xargs -n 1 | sort -r
ddd
ccc
bbb
111

bash$ echo 111 bbb ccc ddd | xargs -n 1 | sort -r | less

bash$  ^less^cat^
bash: ^less^cat^: command not found

$ alias alias_tst
alias alias_tst=echo

ChkCmd=alias_tst
ls *.rpm | $ChkCmd
-bash: alias_tst: command not found

ls *.rpm | eval $ChkCmd

$ alias ls='ls --color=auto '

$ alias dir='ls -lF '

$ alias
alias dir='ls -lF '
alias ls='ls --color=auto '

$ lf(){ dir "$@" | grep -v '^[dl]' ;}

$ type lf
lf is a function
lf ()
{
    ls --color=auto -lF "$@" | grep -v '^[dl]'
}

$ echo aa{a,b}
aaa aab

echo mkdir -p /mnt/iso{1,2,3,4,5}
echo mkdir -p /mnt/tmp{,1,2}
echo mkdir -p /dos/drv_{a,b,c}{1,2,3,4}

bash$ echo m{1,2,3} n{1,2,3}
m1 m2 m3 n1 n2 n3

bash$ echo m{1,2,3 a b} n{1,2,3}
m{1,2,3 a b} n1 n2 n3

bash$ echo m{1,2,3,a,b} n{1,2,3}
m1 m2 m3 ma mb n1 n2 n3

bash$ echo m{1,2,3,a, b}
m{1,2,3,a, b}

$ echo fjdslkfjdslk

$ printf fj M-TAB

M-TAB: dynamic-complete-history

$ /bin/echo a1 b2 c3 d4
a1 b2 c3 d4

$  echo !:0
 echo /bin/echo
/bin/echo

$  echo !:1
 echo a1
a1

$  echo !:2
 echo b2
b2

$  echo !*
echo a1 b2 c3 d4
a1 b2 c3 d4

ls -f a1 b2 c3 d4 &

$ ls !:1-
ls -f a1 b2 c3 d4

$ echo A /a/b/c.d.e
A /a/b/c.d.e
$ echo B !:2*
echo B /a/b/c.d.e
/a/b/c.d.e

Event Designators
    An  event  designator  is  a reference to a command line entry in the
    history list.

!      Start a history substitution, except when followed by a blank,
       newline, = or (.
!!     Refer to the previous command.  This is a synonym for `!-1'.
!n     Refer to command line n.
!-n    Refer to the current command line minus n.
!string
       Refer to the most recent command starting with string.
!?string[?]
       Refer to the most recent command containing string.
^string1^string2^
       Quick   substitution.   Repeat  the  last  command,  replacing
       string1 with string2.  Equivalent to ``!!:s/string1/string2/''
       (see Modifiers below).
!#     The entire command line typed so far.

Word Designators
    A  :  separates the event specification from the word designator.  It
    can be omitted if the word designator begins with a ^, $,  *,  or  %.
    Words  are  numbered  from  the beginning of the line, with the first
    word being denoted by a 0 (zero).

0 (zero)
       The zeroth word.  For the shell, this is the command word.
n      The nth word.
^      The first argument.  That is, word 1.
$      The last argument.
%      The word matched by the most recent `?string?' search.
x-y    A range of words; `-y' abbreviates `0-y'.
*      All of the words but the zeroth.  This is a synonym for `1-$'.
       It  is  not an error to use * if there is just one word in the
       event; the empty string is returned in that case.
x*     Abbreviates x-$.
x-     Abbreviates x-$ like x*, but omits the last word.

Modifiers
    After the optional word designator, you can add a sequence of one  or
    more of the following modifiers, each preceded by a `:'.

h      Remove a trailing pathname component, leaving only the head.
r      Remove  a  trailing suffix of the form .xxx, leaving the basename.
e      Remove all but the trailing suffix.
t      Remove all leading pathname components, leaving the tail.
p      Print the new command but do not execute it.
q      Quote the substituted words, escaping further substitutions.
x      Quote the substituted words as with q, but break into words at
       blanks and newlines.
s/old/new/
       Substitute new for the first occurrence of old in the event
       line.  Any delimiter can be used in place of /.  The final
       delimiter is optional if it is the last character of the event
       line.  The delimiter may be quoted in old and new with a
       single backslash.  If & appears in new, it is replaced by old.
       A single backslash will quote the &.

&      Repeat the previous substitution.
g      Cause changes to be applied over the entire event line.   This
       is  used  in  conjunction  with `:s' (e.g., `:gs/old/new/') or
       `:&'.  If used with `:s', any delimiter can be used  in  place
       of  /,  and  the final delimiter is optional if it is the last
       character of the event line.

command_oriented_history
     If  set, bash attempts to save all lines of a multiple-line command in
     the same history entry.  This allows  easy  re-editing  of  multi-line
     commands.

previous-history (C-p)
       Fetch the previous command from the history list, moving back
       in the list.
next-history (C-n)
       Fetch the next command from the history list, moving  forward
       in the list.
beginning-of-history (M-<)
       Move to the first line in the history.
end-of-history (M->)
       Move  to  the  end  of the input history, i.e., the line cur-
       rently being entered.
reverse-search-history (C-r)
       Search backward starting at the current line and moving  `up'
       through  the  history  as  necessary.  This is an incremental
       search.
forward-search-history (C-s)
       Search forward starting at the current line and moving `down'
       through  the  history  as  necessary.  This is an incremental
       search.
non-incremental-reverse-search-history (M-p)
       Search backward through the history starting at  the  current
       line  using a non-incremental search for a string supplied by
       the user.
non-incremental-forward-search-history (M-n)
       Search forward through the history  using  a  non-incremental
       search for a string supplied by the user.
history-search-forward
       Search  forward through the history for the string of charac-
       ters between the start of the current line  and  the  current
       point.   This  is a non-incremental search.  By default, this
       command is unbound.

-a   Append the ``new'' history  lines  (history  lines
     entered  since  the  beginning of the current bash
     session) to the history file.
-n   Read the history lines not already read  from  the
     history file into the current history list.  These
     are lines appended to the history file  since  the
     beginning of the current bash session.
-r   Read the contents of the history file and use them
     as the current history.
-w   Write the current history  to  the  history  file,
     overwriting the history file's contents.
-c   Clear  the  history  list  by  deleting  all   the
     entries.

Editor commands (+)
    `bindkey'  lists  key  bindings and `bindkey -l' lists and
    briefly describes editor commands.  Only new or especially
    interesting  editor  commands  are  described  here.   See
    emacs(1) and vi(1) for descriptions of each  editor's  key
    bindings.

complete-word-fwd (not bound)
        Replaces  the  current word with the first word in
        the list of possible completions. May be  repeated
        to  step down through the list.  At the end of the
        list, beeps and reverts to the incomplete word.

expand-history (M-space)
        Expands history substitutions in the current word.
        See History substitution.  See  also  magic-space,
        toggle-literal-history  and  the  autoexpand shell
        variable.

expand-variables (^X-$)
        Expands the variable to the left  of  the  cursor.
        See Variable substitution.

history-search-backward (M-p, M-P)
        Searches  backwards through the history list for a
        command beginning with the current contents of the
        input  buffer  up to the cursor and copies it into
        the input buffer.  The  search  string  may  be  a
        glob-pattern  (see Filename substitution) contain-
        ing `*', `?', `[]' or `{}'.  up-history and  down-
        history will proceed from the appropriate point in
        the history list.  Emacs mode only.  See also his-
        tory-search-forward and i-search-back.

insert-last-word (M-_)
        Inserts the last word of the previous  input  line
        (`!$') into the input buffer.  See also copy-prev-
        word.

spell-line (M-$)
        Attempts to correct the spelling of each  word  in
        the  input  buffer,  like  spell-word, but ignores
        words whose first character is one  of  `-',  `!',
        `^'  or  `%', or which contain `\', `*' or `?', to
        avoid problems with  switches,  substitutions  and
        the like.  See Spelling correction.

spell-word (M-s, M-S)
        Attempts  to  correct  the spelling of the current
        word  as  described  under  Spelling   correction.
        Checks  each  component of a word which appears to
        be a pathname.

toggle-literal-history (M-r, M-R)
        Expands or `unexpands'  history  substitutions  in
        the input buffer.  See also expand-history and the
        autoexpand shell variable.

which-command (M-?)
        Does  a  which (see the description of the builtin
        command) on the first word of the input buffer.

DIRSTACK
     An array variable (see  Arrays  below)  containing  the
     current  contents  of the directory stack.  Directories
     appear in the stack in the order they are displayed  by
     the  dirs  builtin.  Assigning to members of this array
     variable may be used to modify directories  already  in
     the stack, but the pushd and popd builtins must be used
     to add and  remove  directories.   Assignment  to  this
     variable  will  not  change  the current directory.  If
     DIRSTACK is unset, it  loses  its  special  properties,
     even if it is subsequently reset.

Arrays
   Bash provides one-dimensional array variables.  Any variable
   may be used as an array; the declare builtin will explicitly
   declare an array.  There is no maximum limit on the size  of
   an  array,  nor  any  requirement that members be indexed or
   assigned contiguously.  Arrays are  indexed  using  integers
   and are zero-based.

An  array  is  created  automatically  if  any  variable  is
assigned  to  using  the  syntax name[subscript]=value.  The
subscript is treated as an arithmetic expression  that  must
evaluate  to  a  number  greater  than or equal to zero.  To
explicitly declare an array, use declare -a name (see  SHELL
BUILTIN COMMANDS below).  declare -a name[subscript] is also
accepted; the  subscript  is  ignored.   Attributes  may  be
specified  for  an  array  variable  using  the  declare and
readonly builtins.  Each attribute applies to all members of
an array.

Arrays are assigned to using  compound  assignments  of  the
form  name=(value1  ...  valuen), where each value is of the
form [subscript]=string.  Only string is required.   If  the
optional  brackets and subscript are supplied, that index is
assigned to; otherwise the index of the element assigned  is
the  last  index  assigned  to  by  the  statement plus one.
Indexing starts at zero.  This syntax is  also  accepted  by
the  declare  builtin.   Individual  array  elements  may be
assigned to using the  name[subscript]=value  syntax  intro-
duced above.

Any  element  of  an   array   may   be   referenced   using
${name[subscript]}.   The  braces are required to avoid con-
flicts with pathname expansion.  If subscript is @ or *, the
word  expands  to  all  members  of  name.  These subscripts
differ only when the word appears within double quotes.   If
the  word  is  double-quoted, ${name[*]} expands to a single
word with the value of each array member  separated  by  the
first  character of the IFS special variable, and ${name[@]}
expands each element of name to a separate word.  When there
are  no  array members, ${name[@]} expands to nothing.  This
is analogous to the expansion of the  special  parameters  *
and  @  (see Special Parameters above).  ${#name[subscript]}
expands to the length of ${name[subscript]}.   If  subscript
is  *  or  @, the expansion is the number of elements in the
array.  Referencing an array variable without a subscript is
equivalent to referencing element zero.

HISTCONTROL
     If set to a value of  ignorespace,  lines  which  begin
     with  a  space character are not entered on the history
     list.  If set to a value of ignoredups, lines  matching
     the  last  history  line  are  not entered.  A value of
     ignoreboth combines the two options.

Brace Expansion
   For example, a{d,c,b}e expands into `ade ace  abe'.
     and,
        mkdir /usr/local/src/bash/{old,new,dist,bugs}
   or
        chown root /usr/{ucb/{ex,edit},lib/{ex?.?*,how_ex}}

Tilde Expansion
   If the tilde-prefix is a `~+', the value of the shell  vari-
   able  PWD replaces the tilde-prefix.  If the tilde-prefix is
   a `~-', the value of the shell variable  OLDPWD,  if  it  is
   set,  is substituted.  If the characters following the tilde
   in the tilde-prefix consist of a number N,  optionally  pre-
   fixed  by  a `+' or a `-', the tilde-prefix is replaced with
   the corresponding element from the directory  stack,  as  it
   would  be  displayed  by  the  dirs builtin invoked with the
   tilde-prefix as an argument.  If  the  characters  following
   the  tilde in the tilde-prefix consist of a number without a
   leading `+' or `-', `+' is assumed.

Arithmetic Expansion
   Arithmetic  expansion allows the evaluation of an arithmetic
   expression and the substitution of the result.   The  format
   for arithmetic expansion is:
        $((expression))

Readline Initialization
   Readline is customized by putting commands in an initializa-
   tion  file  (the  inputrc  file).   The name of this file is
   taken from the value of the INPUTRC variable.  If that vari-
   able  is  unset,  the default is ~/.inputrc.  When a program
   which uses the readline library starts up,  the  initializa-
   tion  file  is  read, and the key bindings and variables are
   set.  There are only a few basic constructs allowed  in  the
   readline  initialization  file.   Blank  lines  are ignored.
   Lines beginning with a # are comments.  Lines beginning with
   a $ indicate conditional constructs.  Other lines denote key
   bindings and variable settings.

The default key-bindings may  be  changed  with  an  inputrc
file.   Other  programs  that use this library may add their
own commands and bindings.

Readline Variables
   Readline has variables that can be used to further customize
   its  behavior.   A  variable  may be set in the inputrc file
   with a statement of the form

set variable-name value

Except where noted, readline variables can take  the  values
On or Off.  The variables and their default values are:

completion-ignore-case (Off)
     If set to On, readline performs filename  matching  and
     completion in a case-insensitive fashion.
completion-query-items (100)
     This determines when the user is queried about  viewing
     the  number  of  possible  completions generated by the
     possible-completions command.  It may  be  set  to  any
     integer  value  greater  than or equal to zero.  If the
     number of possible completions is greater than or equal
     to  the  value  of  this  variable,  the  user is asked
     whether or not he wishes to view them;  otherwise  they
     are simply listed on the terminal.
possible-command-completions (C-x !)
     List the possible completions of the text before point,
     treating it as a command name.
dynamic-complete-history (M-TAB)
     Attempt completion on the text before point,  comparing
     the text against lines from the history list for possi-
     ble completion matches.
show-all-if-ambiguous (Off)
     This alters the  default  behavior  of  the  completion
     functions.   If  set  to on, words which have more than
     one possible completion cause the matches to be  listed
     immediately instead of ringing the bell.
visible-stats (Off)
     If  set  to  On,  a character denoting a file's type as
     reported by stat(2) is appended to  the  filename  when
     listing possible completions.

if [ -n "$BASH_ENV" ]; then . "$BASH_ENV"; fi

Newsgroups: gmane.linux.debian.user
Date: Sat, 26 Jan 2008

$ bash

$ alias rd
alias rd='rmdir'

$ type dt
dt is a function
dt ()
{
    pushd +$1
}

$ exit
exit

Aliases  are not expanded when the shell is not interactive, unless the
expand_aliases shell option is set using shopt.

expand_aliases
        If set, aliases are expanded as  described  above  under
        ALIASES.  This option is enabled by default for interac-
        tive shells.

$ bash -c 'shopt -s expand_aliases; alias rd'
bash: line 0: alias: rd: not found

$ bash -O expand_aliases -c 'rd /tmp/ttt; alias rd; dt bin; type dt'
bash: rd: command not found
bash: line 0: alias: rd: not found
bash: dt: command not found
bash: line 0: type: dt: not found

$ bash -O expand_aliases -c '. ~/.bashrc; (rd /tmp/ttt; alias rd; dt bin; type dt)'

> Use functions. Don't use aliases.

Note: no answer.

> An advanced bash alias expansion question --
> How can I use my aliases or functions in my bash script?

> PS. I even tried the following but it didn't work either:
>
>   $ bash -O expand_aliases -c '. ~/.bashrc; (rd /tmp/ttt; alias rd; dt bin; type dt)'

$ cat .bashrc

alias rd="echo foo"

$ bash -c 'alias rd'
bash: line 0: alias: rd: not found

$ bash -c '. ~/.bashrc; alias rd'
alias rd='echo foo'

$ bash -c '. ~/.bashrc; (alias rd)'
alias rd='echo foo'

[ -z "$PS1" ] && return

$ cat .bashrc
alias rd="echo foo"

$ bash -c '. ~/.bashrc; alias rd;'
alias rd='echo foo'
$ cat > .bashrc << 'EOF'
 > [ -z "$PS1" ] && return
 > alias rd="echo foo"
 > EOF
$ bash -c '. ~/.bashrc; alias rd;'
bash: line 0: alias: rd: not found

$ bash -c 'PS1="."; . ~/.bashrc; alias rd;'
alias rd='echo foo'

>> An advanced bash alias expansion question --
>> How can I use my aliases or functions in my bash script?
>
>> PS. I even tried the following but it didn't work either:
>>
>>   $ bash -O expand_aliases -c '. ~/.bashrc; (rd /tmp/ttt; alias rd; dt bin; type dt)'
>
> . . . your .bashrc probably includes a line of the form:
> [ -z "$PS1" ] && return
>
> So that the bashrc returns prior to defining any aliases. . .

$ cat test.sh
. ~/bin/.aliases_bs; alias rd; shopt -s expand_aliases; rd -v /tmp/ttt

$ bash test.sh
alias rd='rmdir'
test.sh: line 1: rd: command not found

$ cat test.sh
. ~/bin/.aliases_bs; alias rd
rd -v /tmp/ttt

$ bash test.sh
alias rd='rmdir'
rmdir: removing directory, /tmp/ttt

mkdir /tmp/ttt
$ BASH_ENV=~/bin/.aliases_bs bash -c "rd -v /tmp/ttt"
rmdir: removing directory, /tmp/ttt

> > It seems I can't use alias in .bashrc. To illustrate it, I put the
> > following 2 lines at the bottom of my .bashrc file:
> [...]
> Works fine on linux/hpux for both bash and bash2.
> [...]

alias bash_alias_test='echo just testing'; set -x; alias bash_alias_test
bash_alias_test; set +x; unalias bash_alias_test

if [ ${PS1:+T} ]; then
alias bash_alias_test='echo just testing'; set -x; alias bash_alias_test
bash_alias_test; set +x; unalias bash_alias_test
fi

alias bash_alias_test='echo just testing'; set -x; alias bash_alias_test
bash_alias_test; set +x; unalias bash_alias_test

+ alias bash_alias_test
alias bash_alias_test='echo just testing'
+ echo just testing
just testing
+ set +x
+ alias bash_alias_test
alias bash_alias_test='echo just testing'
+ bash_alias_test
bash: bash_alias_test: command not found
+ set +x
+ alias bash_alias_test
alias bash_alias_test='echo just testing'
+ echo just testing
just testing
+ set +x

Newsgroups: comp.os.linux.misc,comp.unix.questions

>In Linux slackware, when I try to use ^d to logout from bash, I got
>a warning saying something like "type logout instead". How can I
>disable this feature?

IGNOREEOF
     Controls the action of the shell on receipt of  an  EOF
     character  as the sole input.  If set, the value is the
     number of consecutive EOF characters typed as the first
     characters  on an input line before bash exits.  If the
     variable exists but does not have a numeric  value,  or
     has  no value, the default value is 10.  If it does not
     exist, EOF signifies the end of  input  to  the  shell.
     This is only in effect for interactive shells.

Newsgroups:  gmane.linux.debian.user
Date:        Thu, 16 Nov 2006 11:59:59 -0500

> For characters whose byte values are greater than 0x7f, how bash
> encode/decode them?
>
> I.e.,
>
>  echo $'\312\325\274\376\317\344' | bash_encode
>
> Anybody know how to make the output similar to '\312\325\274\376\317\344'?

echo -ne "\033]0;aaaa\007"

echo -ne "\033]0;aaaa\007"; cat

PS1="\n\\$ "

> > Further test reveals that, I can't even use the
> >
> > echo -ne "\033]0;aaaa\007"
> >
> > to set my xterm title
> >
> Look for PROMPT_COMMAND in /etc/bash.bashrc

$ grep PROMPT_COMMAND /etc/bash.bashrc
   PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME}: ${PWD}\007"'

Newsgroups: comp.unix.shell

>extraneous characters are generated -- and they end up in the keyboard's
>input buffer, so that the next prompt the user sees has these characters
>present (though ...

#include <unistd.h>
#include <termios.h>
int main(void) { tcflush(STDIN_FILENO, TCIFLUSH); return 0; }

Newsgroups: comp.unix.shell

> I'm trying to find a way to do interactive debugging of bash shell
> scripts; has anybody any suggestion?

>Could someone guide me around bash's lack of support for
>multi-dimensional arrays?  I've tried creating one array with the name
>of the other arrys.  Here is  a sample of what I'm trying to do:
>#!/bin/sh
>
>SERVER="MACSERVER ADVMKT CIRFIN OPSHR MIS1"
>
>MACSERVER="1 2 3 4 5"
>ADVMKT="6 7 8 9 10"
>CIRFIN="11 12 13 14 15"
>OPSHR="16 17 18 19 20"
>MIS1="21 22 23 24 25"
>
>for SYSTEM in ${SERVER}
>do
>    echo "System: "${SYSTEM}
>    for ITEM in ${SYSTEM}
>    do
>        echo "Item: "${ITEM}
>    done
>done

for ITEM in ${!SYSTEM}

>I know I don't need to do a rehash for bash, if new comands appear, it
>get picked up automatically.
>
>But strange thing is that if I launch an application then create an
>instance in my local bin, which comes first in my $PATH, and issue the
>command again, bash still pick the application from the old place, not
>the new place:

$ alias test_p='echo 1:$1 2:$2 3:$3'

$ test_p sss ww bbb
1: 2: 3: sss ww bbb

>say I name an alias sh and in it I want to use the original sh command.
>How can I do it in bash?

sh()
{
        command sh "$@"
}

cd()
{
        builtin cd "$@" && echo $PWD
}

alias sh="command sh"
alias cd="builtin cd"

>I don't know why I can't paste tab into bash.
>
>The following line:
>
>texts1         # 2 tabs before it
>
>when pasted into bash, lookes like:
>
>texts1# 2 tabs before it.
>
>The 2 (whatever) tabs disapeared.

> I don't know offhand of a way to make pasting automatically insert C-v's
> before each TAB.

Date: 9 Sep 2002 04:17:09 GMT
Newsgroups: comp.os.linux.misc

 > Bash manual says ">" and "<" can compare strings based on lexicography
order.

When used within [[ ]], not [ ].

> But:
>
> bash2.05>if [ "1.4" > "1.3" ]; then echo "okay"; fi
> okay

$ if [[ "1.4" > "1.3" ]]; then echo "okay"; fi
okay

> bash2.05>if [ "1.4" < "1.3" ]; then echo "okay"; fi
> okay

$ if [[ "1.4" < "1.3" ]]; then echo "okay"; else echo NOT; fi
NOT

Newsgroups: comp.unix.shell
Date: 27 Sep 2001 11:37:16 -0300

xargs some_alias_command rest of parameters

xargs `get_alias_def some_alias_command` rest of parameters

$ alias atest="echo 'aa bb'"

$ alias atest
alias atest='echo '\''aa bb'\'''

$ alias atest | cut -d= -f 2
'echo '\''aa bb'\'''

$ echo `!!`
echo `alias atest | cut -d= -f 2`
'echo '\''aa bb'\'''

$ echo 'echo '\''aa bb'\'''
echo 'aa bb'

>  xargs `get_alias_def some_alias_command` rest of parameters

$ mkdir test
$ cd test
$ >a;>b;>c
$ alias xx='ls -ld'
$ alias xargs='\xargs '
$ echo * | xargs xx
-rw-rw-rw-   1 dam        users            0 Sep 28 09:35 a
-rw-rw-rw-   1 dam        users            0 Sep 28 09:35 b
-rw-rw-rw-   1 dam        users            0 Sep 28 09:35 c

$ cd /opt
$ ls -l
drwxr-xr-x           ...     applix
...
$ cd applix
pd[4]: /opt/applix/applix: not a directory

$ alias xargs1="xargs -l1"
$ echo * | xargs1 xx
xargs: xx: No such file or directory

$ alias xargs1="xargs -l1 "
$ echo * | xargs1 xx
-rw-rw----    1 tong     tong          118 Sep 18 22:56 Changes
-rw-rw----    1 tong     tong           46 Sep 18 22:56 MANIFEST
...

xargs_with_alias() {
  alias_name=$1
  shift
  eval expanded_alias="`alias $alias_name | cut -d = -f2-`"
  eval xargs "$expanded_alias" '"$@"'
}

> >   eval xargs "$expanded_alias" '"$@"'
>
> Anybody else can come up with more generic solutions that don't
> tie up with xargs? I just use xargs as an example to explain the
> situation... thanks

Newsgroups: comp.unix.shell

{ echo "GET /" >&0; cat; } <>/dev/tcp/www.server.com/80