Miserable installation worse installation documentation

[Andrew & Patty Winter]

Gentlemen

It seems that in the modern age of programming giving out complete
information is considered /passe/. It is very frustrating to download
a "complete" install package only to find that the "install" did not
bother to tell the OS where the program was.

I downloaded the "setup" package for SED
Ran the setup and installed it.
tried to invoke sed from the command prompt only to receive the error
that sed was not a recognized command.

This is a very nasty very aggravating thing to run into after several
days of researching a problem and running into brick walls.

It took me an additional hour of research on the web to find out that
your installer simply does not inform windows where the thing was
installed and that in addition to installing sed I have then /manually/
go into my path statement and add the path to sed there.

This is a monumental pain in the ass. Especially since NOTHING in your
documentation even hints at such a problem which required me to go
search the web for a solution to the fact that you just did not think it
important to give your potential users complete information.

Good Gawd people.

[Paul Eggert]

On 11/15/12 07:59, Andrew & Patty Winter wrote:

> This is a monumental pain in the ass.

Welcome to Microsoft Windows :-).

I'm not sure what the "setup" package is, as it isn't part of
GNU sed itself. I expect that the "setup" package was
developed by a third party, and that you should inform the third
party of your problems, as the bug...@gnu.org mailing list is
for bugs in GNU sed. Good luck!