Werner LEMBERG wrote:
> No time to dig into this issue. If you provide a patch, I'm gladly
> applying it.
The macro misc@tag is solely used for HTML output (currently). It causes the
problem in this case (the line \h'\\n[misc*.k]u'\c). I suggest to enable this
macro only in HTML mode to avoi
> Werner, is misc@tag really written by you?
I no longer can remember.
> Isn't it dangerous to use \c there? Wouldn't it be better to but a
> "if HTML" around everything inside this macro? And also the \{
> (instead \{\) without a comment that this is intented doesn't look
> trustworthy.
No t
> Without trying to complicate the discussion, I used
>
> .\"
>
> Not
> \#
>
> The former is a pure comment. It does not enter into any processing.
This is not correct. The escape `\"' strips everything to the end of
the line but *not* the final newline. Consequently,
.\"
is
On Wed, 23 Dec 2015, Mike Bianchi wrote:
On Wed, Dec 23, 2015 at 04:44:40PM +0100, Carsten Kunze wrote:
Hello Mike,
what do you mean here--Damian didn't use \#?
Carsten
His example was
.H 2 "A Heading"
.TS
.\" some table of something
.
.TE
or
.H 2 "
Damian McGuckin wrote:
> [...] I was after some words of wisdom or
> more precisely, insight, from somebody who had used such a tool for longer
> than I have.
This is totally groff specific, AT&T roff didn't have this issue (and groff
doesn't have it either if this HTML specific line is remove
On Wed, 23 Dec 2015, Carsten Kunze wrote:
Damian McGuckin wrote:
Or are my ideas too rooted in the past? Comments (Doug)?
I think Doug is not to blame here :)
I was not blaming Doug. Sorry Doug. I was after some words of wisdom or
more precisely, insight, from somebody who had used such
Damian McGuckin wrote:
> The use of \# looks like a fudge to fix a problem. Which sounds like a
> recipe for disaster.
Indeed :)
> Or are my ideas too rooted in the past? Comments (Doug)?
I think Doug is not to blame here :)
Werner, is misc@tag really written by you? Isn't it dangerous to u
On Wed, Dec 23, 2015 at 04:44:40PM +0100, Carsten Kunze wrote:
> Hello Mike,
>
> what do you mean here--Damian didn't use \#?
>
> Carsten
His example was
> .H 2 "A Heading"
> .TS
> .\" some table of something
> .
> .TE
> or
> .H 2 "Another Heading"
>
On Wed, 23 Dec 2015, Carsten Kunze wrote:
what do you mean here--Damian didn't use \#?
The use of \# looks like a fudge to fix a problem. Which sounds like a
recipe for disaster.
Or are my ideas too rooted in the past? Comments (Doug)?
Regards - Damian
Pacific Engineering Systems Internat
Hello Mike,
what do you mean here--Damian didn't use \#?
Carsten
Damian,
I find that
\# works well outside of tables.
.\# works well inside tables _AFTER_ the initial specification.
>From man 7 groff ...
\# Everything up to and including the next newline is ignored.
This is interpreted in copy mode. T
Damian McGuckin wrote:
> What is the real fix please?
... the .sp -1 and \c in misc@tag don't look reliable and depending on what
follows may cause issues. This seems to be the case here. H adds space after
the heading, with the .br at begin of DS that space gets fixed. Now DS of
cause adds
Around August 2014, there was a discussion started by Blake McBride
Problem with MM spacing
I looks like Werner fixed something but I cannot exactly figure out what
it was from that discussion.
The problem I have could be related but it is subtly different.
Let me know if I should r
Looks good. Thanks!
On Thu, Aug 28, 2014 at 12:28 AM, Werner LEMBERG wrote:
>
> > Given MM input text:
> >
> > .nr Hb 0
> > .nr Hs 0
> > .nr Hi 0
> > .H 1 A
> > .P
> > Now is the time for all good men to come to the aid of their party.
> > .H 2 B
> > .P
> > Now is the t
Hi Werner,
> > Groff produces output in which the section headers are overwritten
> > by the paragraph text.
>
> This should be fixed now in git, please test.
LGTM.
BTW, this is a regression that could be caught by simple -Tascii-level
tests of a `make check'. I know we think PDF comparisons a
> Given MM input text:
>
> .nr Hb 0
> .nr Hs 0
> .nr Hi 0
> .H 1 A
> .P
> Now is the time for all good men to come to the aid of their party.
> .H 2 B
> .P
> Now is the time for all good men to come to the aid of their party.
>
>
> Groff produces output in which the section
I tried reversing out the changes in that git revision and it fixed the
problem. I do not know how to change it so that the fix that patch was
intended for and the correct functionality still works correctly. Can
someone help with this?
Thanks!
Blake
On Wed, Aug 27, 2014 at 9:57 AM, Ralph Cor
> I can confirm the bug. But it's not mm.tmac that has changed,
Well, this is embarrassing. Of course mm.tmac has not changed,
it simply refers to m.tmac, which has indeed changed.
It's the (new) block starting "wrapper to cancel the side effect"
which causes the problem.
So troff is actually
> I suggest that non-release versions of groff should display the GIT
> revision number in addition to the version number in order to remove
> all ambiguities. I've suggested this to several other packages who
> have agreed making debugging a lot easier.
We essentially get this for free as soon
Hi Tadziu,
> I can confirm the bug. But it's not mm.tmac that has changed,
> so it must be something in troff itself (somewhere between
> versions 1.21 and 1.22.2).
Well, if I've done it right, `git bisect' is saying it went wrong with
http://git.savannah.gnu.org/cgit/groff.git/commit?id=d32e328
groff --version returns 1.22.2
Having said that, however, it is probably a git version I built at some
point. I suggest that non-release versions of groff should display the GIT
revision number in addition to the version number in order to remove all
ambiguities. I've suggested this to several o
> I'd say older is better. :-) Can you be any more specific about the
> versions? That would help narrow down changes that might have caused
> the problem.
I can confirm the bug. But it's not mm.tmac that has changed,
so it must be something in troff itself (somewhere between
versions 1.21 an
Hi Blake,
> .nr Hb 0
> .nr Hs 0
> .nr Hi 0
> .H 1 A
> .P
> Now is the time for all good men to come to the aid of their party.
> .H 2 B
> .P
> Now is the time for all good men to come to the aid of their party.
>
> Groff produces output in which the section headers are ove
Greetings,
Given MM input text:
.nr Hb 0
.nr Hs 0
.nr Hi 0
.H 1 A
.P
Now is the time for all good men to come to the aid of their party.
.H 2 B
.P
Now is the time for all good men to come to the aid of their party.
Groff produces output in which the section headers are o
24 matches
Mail list logo
