Re: [cmd]:"env edit" vs "env set", do we need both options for "env" command ??

[Wolfgang Denk]

Dear Adarsh Babu Kalepalli,

In message  
you wrote:
>
> Are'nt "env edit" vs "env set" redundant ??.

No, they are not.

> "env edit" allows modification of the environment variable value in the
> next line,whereas "env set" requires the mention of the environment
> variable value in the same line.

"env edit" is an _interactive_ command. You cannot use it in
scripts, for example.

> Can we have only one of these commands ??.

No, they serve very different purposes.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de
A good aphorism is too hard for the tooth of time, and  is  not  worn
away  by  all  the  centuries,  although  it serves as food for every
epoch.  - Friedrich Wilhelm Nietzsche
  _Miscellaneous Maxims and Opinions_ no. 168

[cmd]:"env edit" vs "env set",do we need both options for "env" command ??

[Adarsh Babu Kalepalli]

Hi,

Are'nt "env edit" vs "env set" redundant ??.
"env edit" allows modification of the environment variable value in the
next line,whereas "env set" requires the mention of the environment
variable value in the same line.

If the values for environment variables are not provided ,in either case
they would be deleted.

Can we have only one of these commands ??.

A single line description for "set" sub-command of "env" with mention to
that additional feature will provide better clarity.

Regards,
Adarsh