docs: say that long opts with optional arguments require equals not space

[correabuscar]

maybe the wording here isn't ideal, but this PR is so that "we"(or you) don't forget to address it. Can always change wording later, before merging.

see comment: #104 (comment)

[tgross35]

This is rather wordy. Could you express it in a smaller paragraph(s) followed by examples instead? That also makes sure it is accurate.

(sorry that this crate hasn't really been maintained in a while)

[tgross35]

This is much cleaner, thanks for that. I meant examples that are doctests so we'll get this verified though - would you be able to add them?

[correabuscar]

This is much cleaner, thanks for that. I meant examples that are doctests so we'll get this verified though - would you be able to add them?

Oh, sorry, I misunderstood and this makes your last sentence from before (ie. this That also makes sure it is accurate.) consistent, even though I ignored it at the time automatically without realizing.

I just realized that maybe this PR is not necessarily correct, after seeing this:

getopts/src/lib.rs

Lines 169 to 180 in 4084692

	/// Set or clear "long options only" mode.
	///
	/// In "long options only" mode, short options cannot be clustered
	/// together, and long options can be given with either a single
	/// "-" or the customary "--". This mode also changes the meaning
	/// of "-a=b"; in the ordinary mode this will parse a short option
	/// "-a" with argument "=b"; whereas in long-options-only mode the
	/// argument will be simply "b".
	pub fn long_only(&mut self, long_only: bool) -> &mut Options {
	self.long_only = long_only;
	self
	}

As I don't really have the time needed to ensure consistency here(ie. much consideration required), I vote we scrap this PR. Also I don't know how to do those doctests, not without spending a bunch of hours first.