Hi Ted,
> > I could match / *$ but it seems more logical to insist on an least
> > one space being present, as you do.
>
> Matching a single space would be fine if you were confident of at most
> one trailing space. NBut it's more than "logical", it is very
> practical in many cases, to allow fo
Ted, Ralph,
Thanks for your responses. Beyond the `ds' family, are you aware of any
other macros where trailing whitespace is meaningful?
And just for the sake of finality, can you imagine any circumstances
where free-form lines (i.e., w/o a leading macro) would be affected by
trailing whit
Hi Ralph,
I think your points are mostly matters of taste and convenience!
On 09-May-10 00:09:53, Ralph Corderoy wrote:
>
> Hi Ted,
>
>> Using the 'vim' editor, I can easily strip trailing spaces from a file
>> I am editing with the command
>>
>> :1,$s/ [ ]*$//
>
> I'm not sure why the secon
Hi Ted,
> Using the 'vim' editor, I can easily strip trailing spaces from a file
> I am editing with the command
>
> :1,$s/ [ ]*$//
I'm not sure why the second space is a character class, but I do the
same thing with
:%s/ *$
`%' is a shorthand for `1,$'. And since I want to delete the
Ralph has given a nice example. In any case, there is at least one
good concrete reason for avoiding trailing spaces, namely that it
is not obvious what groff will do with them, and they serve no
purpose that you can not achieve by other means.
I hit such a case not long ago, inadvertently, after
Hi Kristaps,
> Are there any concrete reasons for avoiding trailing eoln whitespace
> in roff files (specifically -man and/or -mdoc)? These are stripped
> from input anyway "foo" followed by "bar" outputs "foo bar", so
> I'm hard up for providing a reason beyond "Do It".
It's generally a go
Hello,
Are there any concrete reasons for avoiding trailing eoln whitespace in
roff files (specifically -man and/or -mdoc)? These are stripped from
input anyway "foo" followed by "bar" outputs "foo bar", so I'm hard
up for providing a reason beyond "Do It".
Thank you,
Kristaps
