Re: mention printing of warranty information in GUI programs

[Alfred M. Szmidt]

   >    If the program would open with a window/dialog and maybe even asks me to
   >    click or type "I consent" then this is only fine exactly one time for a
   >    given version.
   >
   > There is no need to "consent" to using a free software program,
   > there is no reason to ask such a question.

   So we completely agree on that.

Nobody was suggesting a "I consent" form so I'm not sure what your
point is.  

   > There is no reason to fantasie about how one can annoy the user in the
   > most annoying manner in GNU programs.

   Agreed. And my point was that for many GUI/TUI programs we just don't
   know how those are used - they may be "long running" (video editing
   comes to mind) or short running "just show me that piece of
   code/text/photo/video/..." - I therefore conclude that whatever is
   possibly done in a TUI/GUI program about "printing warranty information"
   should not disturb in any way.

That is why it is often up to the maintainer to figure out when it is
useful, it shouldn't be necessary to specify exactly in miniscule
detail what to do.

   The suggested change:

...

   > +If your program is interactive, please also print the same information
   > +as for the @code{--version} option (@pxref{--version}) on program
   > +startup, and also provide instructions how to get more information
   > +about the copying conditions and warranty details.
   >
   >  @node Command-Line Interfaces
   >  @section Standards for Command Line Interfaces

   is for me (when just reading that change as-is) a request to annoy the
   user, which is not the intention.

I do not see how it annoys anyone.  If you have a better formulation,
please suggest it.

   > What do people think about this?

   I think that the text either needs more explanation and samples how to
   do that or should not be applied.

It is already explained in the --version section of the GCS.  There is
no need to enumerate every single possible case of fantastic ways to
annoy users, the standard would be longer than its actual useful content.

   If the program has a menu then it should contain an info/version item to
   show this, similar when it has commands (like vim or emacs), then there
   should a command to print this.

This is a different point, and unrelated to showing warranty or
copyright information on startup.

   If it is possible to print it to the user without annoying, (like "show
   in background like a file to view" if no file is open [like VIm does])
   then this would be good, too.

Nothing stops anyone from doing that.  The text only says to show such
information at startup, when it makes sense.  And to provide the same
information to warranty and copyright information, it does not say
where -- this could be a link, a menu or something else.