At 2020-11-12T09:00:11+1100, Damian McGuckin wrote:
> On Wed, 11 Nov 2020, Dorai Sitaram via wrote:
>
> > Is there a way to change the text used for the section header inserted
> > by 'refer' before the accumulated references? By default, it is
> > "References". Hopefully it isn't hardcoded.
>
At 2020-11-11T23:16:28+0100, Bertrand Garrigues wrote:
> Hi Branden,
>
> I've replied to this bombardment by firing a commit that changes 509
> files; well it's just to update the copyright date... This time I've
> been more cautious and I think everything is in order.
Excellent!
> I found no i
On Wed, Nov 11, 2020 at 09:42:25PM +, Dorai Sitaram via wrote:
> Is there a way to change the text used for the section header inserted by
> 'refer' before the accumulated references? By default, it is "References".
> Hopefully it isn't hardcoded.
>
> --d
Use the file "tmac/sv.tmac" as
Hi Branden,
> In view of the date, I therefore offer my regrets for subjecting
> subscribers to groff-commit or pullers from our Git repo to a barrage
> of artillery shells.
Whether it's Armistice Day, Remembrance Day, as it is in Great Britain,
or Veterans Day, I don't think Happy is appropriate
Hi Branden,
On Wed, Nov 11 2020 at 08:20:26 PM, "G. Branden Robinson"
wrote:
> In view of the date, I therefore offer my regrets for subjecting
> subscribers to groff-commit or pullers from our Git repo to a barrage
> of artillery shells.
I've replied to this bombardment by firing a commit that
On Wed, 11 Nov 2020, Dorai Sitaram via wrote:
Is there a way to change the text used for the section header inserted
by 'refer' before the accumulated references? By default, it is
"References". Hopefully it isn't hardcoded.
With '-mm', it is defined by the string
\*(Rp
I hacked t
Is there a way to change the text used for the section header inserted by
'refer' before the accumulated references? By default, it is "References".
Hopefully it isn't hardcoded.
--d
> Overall, let’s (both of us) focus on trimming anything that doesn’t
> help a reader get a -ms document together.
YES!
But don't throw away the trimmings. They often contain info that the
more involved readers might value. So maybe there can be an Appendix called
"Color Commentary"? ;)
If that does not work try (assuming bash):
export GROFF_ENCODING=utf8
groff_pipeline
rationale:
doing
GROFF_ENCODING=utf8 groff_pipeline
is setting GROFF_ENCODING for the first element only, if anything later in the
pipe needs that also it is lost. Using export means that subshell also have
this
In view of the date, I therefore offer my regrets for subjecting
subscribers to groff-commit or pullers from our Git repo to a barrage
of artillery shells.
Regards,
Branden
signature.asc
Description: PGP signature
[redirecting discussion to groff at gnu org, since I don't think of
bug-groff as really a discussion list]
At 2020-11-08T02:06:20+, Bjarni Ingi Gislason wrote:
> On Fri, Nov 06, 2020 at 05:59:16PM -0500, G. Branden Robinson wrote:
> > Update of bug #59424 (project groff):
> > [comment #0 origi
11 matches
Mail list logo
