How do you format a command line that needs < > and they are not meant to redirect anything they are part of an email address.
command -f "Some Email someemail@somedomain.com" -x -y -z
I tried putting a backslach in front of the < and > but that didnt do it either.
Thanks,
Jerry
Jerry Geis wrote:
How do you format a command line that needs < > and they are not meant to redirect anything they are part of an email address.
command -f "Some Email someemail@somedomain.com" -x -y -z
use single quote
command -f 'Some Email someemail@somedomain.com' -x -y -z
I tried putting a backslach in front of the < and > but that didnt do it either.
Thanks,
Jerry _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Mon, Dec 18, 2006 at 07:27:12PM +0200, Diaa Radwan wrote:
Jerry Geis wrote:
How do you format a command line that needs < > and they are not meant to redirect anything they are part of an email address.
command -f "Some Email someemail@somedomain.com" -x -y -z
use single quote
command -f 'Some Email someemail@somedomain.com' -x -y -z
Or take out the "<" and ">" entirely,... they're not needed anyway.
I tried putting a backslach in front of the < and > but that didnt do it either.
On Mon, Dec 18, 2006 at 06:44:57PM -0500, fredex wrote:
On Mon, Dec 18, 2006 at 07:27:12PM +0200, Diaa Radwan wrote:
Jerry Geis wrote:
How do you format a command line that needs < > and they are not meant to redirect anything they are part of an email address.
command -f "Some Email someemail@somedomain.com" -x -y -z
use single quote
command -f 'Some Email someemail@somedomain.com' -x -y -z
Or take out the "<" and ">" entirely,... they're not needed anyway.
by which I MEANT to say, reformat it to look like this:
command -f someemail@somedomain.com -x -y -z
because the verbose form is for human readability anyway.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
fredex wrote:
Or take out the "<" and ">" entirely,... they're not needed anyway.
by which I MEANT to say, reformat it to look like this:
command -f someemail@somedomain.com -x -y -z
because the verbose form is for human readability anyway.
My mails aren't read by machines, so I'd always factor in human readability.
Ralph
Quoting Jerry Geis geisj@pagestation.com:
How do you format a command line that needs < > and they are not meant to redirect anything they are part of an email address.
command -f "Some Email someemail@somedomain.com" -x -y -z
I tried putting a backslach in front of the < and > but that didnt do it either.
That's strange. Your example (with double or single quotes) should work. It surelly works for me:
$ echo "Some Email someemail@somedomain.com" Some Email someemail@somedomain.com
Have you done something strange in your shell's config file?
I have experimented poltergeists like that when calling scripts with system command from perl for example. In such case I have problems when I did not scape the @ symbol with a backslash. did you tried it?
Maybe it's a nonsense, maybe not...
Aleksandar Milivojevic wrote:
Quoting Jerry Geis geisj@pagestation.com:
How do you format a command line that needs < > and they are not meant to redirect anything they are part of an email address.
command -f "Some Email someemail@somedomain.com" -x -y -z
I tried putting a backslach in front of the < and > but that didnt do it either.
That's strange. Your example (with double or single quotes) should work. It surelly works for me:
$ echo "Some Email someemail@somedomain.com" Some Email someemail@somedomain.com
Have you done something strange in your shell's config file?
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Quoting Lorenzo Martínez Rodríguez Lawwait@yahoo.es:
I have experimented poltergeists like that when calling scripts with system command from perl for example. In such case I have problems when I did not scape the @ symbol with a backslash. did you tried it?
If the "command" from OP's example is badly written Perl or shell script (or whatever other script or program) that invokes some other command blindly passing to it its command line arguments in some broken way, yes there might be problems. However, than it is a bug in the "command" (OP hasn't told us what is the "command" he is invoking), not the problem with the shell that invokes that "command".
On 12/18/06, Aleksandar Milivojevic alex@milivojevic.org wrote:
Quoting Jerry Geis geisj@pagestation.com:
How do you format a command line that needs < > and they are not meant to redirect anything they are part of an email address.
command -f "Some Email someemail@somedomain.com" -x -y -z
I tried putting a backslach in front of the < and > but that didnt do it either.
That's strange. Your example (with double or single quotes) should work. It surelly works for me:
Ditto....james
On 12/18/06, Aleksandar Milivojevic alex@milivojevic.org wrote:
Quoting Jerry Geis geisj@pagestation.com:
How do you format a command line that needs < > and they are not meant to redirect anything they are part of an email address.
command -f "Some Email someemail@somedomain.com" -x -y -z
I tried putting a backslach in front of the < and > but that didnt do it either.
That's strange. Your example (with double or single quotes) should work. It surelly works for me:
Perhaps it is not the command syntax but the syntax of the email address. Normally an email address with From Name and Address should be:
"My Name" myemail@domain.com
and not
My Name myemail@domain.com
Perhaps it is not the command syntax but the syntax of the email address. Normally an email address with From Name and Address should be:
"My Name" myemail@domain.com
and not
My Name myemail@domain.com
Both forms are prefectly legal. Everything outside <> is considered to be a comment. The quotes are usually used for things like "Last, First" (notice the comma) in the comment part.
-
Aleksandar Milivojevic -
Diaa Radwan -
fredex -
James Olin Oden -
Jerry Geis -
Lorenzo Martínez Rodríguez -
Matthew Martz -
Ralph Angenendt