Re: [bug-gtypist] Are double spaces after periods still relevant?

[Ben Armstrong]

On 06/22/2012 11:37 AM, Tim Marston wrote:
> Hi Martin,
> Regardless of whether they're a relic or not, though, I would bet that a
> lot of people would complain either way if we added or removed them.  It
> sounds like the kind of thing that you might want to configure.  So I'll
> add it to our to-do list to add a command-line option that removes or
> adds them.

Agreed; cf. -w option, which is similar in its intent (deals with the fact that 
in a word processor,
pressing enter is not needed). I'm not suggesting that the two options be 
combined, but merely cite
it as a precedent for making options for this sort of thing.

The other thing to discuss is "what should the default behaviour be?" I would 
argue that no matter
the aggravation it causes old users, one space should be the default. That is, 
make people wishing
to cling to legacy style rules do the extra work to configure gtypist to suit 
them, not the other
way around.

Can the same case be made for making -w the default? Surely we should 
discourage, not encourage,
pressing enter at the end of every line? (But this would require the option to 
be negatable. I'm not
sure if it is ...)

Ben