> > > a request that would print its argument with all
> > > hyphenation points visible
>
> I think this is not necessary.
>
> > [...] single word. That is trivially handled by
> > groff -a
> > .ll 1u
> > recapitulation
>
> Exactly. Based on that a simple macro can be constructed:
>> a request that would print its argument with all hyphenation points
>> visible
I think this is not necessary.
> What I see as the typical use is a nonce question about a
> single word. That is trivially handled by
> groff -a
> .ll 1u
> recapitulation
> The result is marrred
[adding groff@gnu back into CC]
I think the TUHS guys might be wondering where this topic came from. :)
At 2018-11-08T11:30:46-0500, Doug McIlroy wrote:
> > I have a vague intuition right now that the hyphenation decisions
> > ...
> > should be accessible without having to invoke the output drive
At 2018-11-08T09:50:31-0500, Doug McIlroy wrote:
> > a request that would print its argument with all hyphenation points visible
> > ...
> > it requires a contrivance to discover them
>
> The second bit of the quote seems to answer the first: there's
> no need for such a request because the functi
Hi Doug,
> That is trivially handled by
> groff -a
> .ll 1u
> recapitulation
> The result is marrred with "can't break line" diagnostics,
> but it's quick and intelligible.
The warnings can be turned off.
$ printf '%s\n' '.ll 1u' recapitulation |
> nroff -Wbreak |
>
On Thu, Nov 08, 2018 at 09:50:31AM -0500, Doug McIlroy wrote:
> What I see as the typical use is a nonce question about a
> single word. That is trivially handled by
> groff -a
> .ll 1u
> recapitulation
> The result is marrred with "can't break line" diagnostics,
> but it's quick
> a request that would print its argument with all hyphenation points visible
> ...
> it requires a contrivance to discover them
The second bit of the quote seems to answer the first: there's
no need for such a request because the function can be
accomplished fairly easily.
But I have no perspec
Hi Branden,
> Wouldn't we need a third argument to specify the string register to be
> populated?
Yes, maybe. I was assuming a known destination for the result.
Others, like Tadziu, will have a wider knowledge of what's normal for
new requests of this kind, and what's easier to use when programm
At 2018-11-08T13:50:28+, Ralph Corderoy wrote:
> Hi Branden,
>
> > doc/webpage.ms is a nice example of how to do some fairly
> > sophisticated stuff with groff
> ...
> > 1. Retire it (delete it from the build and repo).
>
> -1. This seems wrong given your praise of it.
Not everybody likes t
At 2018-11-08T13:43:43+, Ralph Corderoy wrote:
> We already have too many printing requests, there's no need for
> another.
Fair enough.
> > re·ca·pit·u·la·tion
>
> How about a request that sets a string register to its second argument
> with all hyphenation points decorated with the first?
Hi Branden,
> doc/webpage.ms is a nice example of how to do some fairly
> sophisticated stuff with groff
...
> 1. Retire it (delete it from the build and repo).
-1. This seems wrong given your praise of it.
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
Hi Branden,
> In my opinion it would be nice if groff had a request that would print
> its argument with all hyphenation points visible
We already have too many printing requests, there's no need for another.
> re·ca·pit·u·la·tion
How about a request that sets a string register to its second ar
At 2018-11-07T01:47:29+0100, Bertrand Garrigues wrote:
> I've also added a rudimentary sanity check on these 2 hdtbl examples
> connected to 'make check'. It justs use 'gs -o /dev/null/
> -sDEVICE=bbox' and 'grep' to count the number of pages. I'll also add
> something for the pdf examples (probab
> Is it possible to configure bug-groff to autorespond to any email
> that doesn't come from the Savannah bug tracker, telling the sender
> that the tracker is the preferred place to report groff bugs?
Probably yes. Dave, do you want to become admistrator of the `groff'
and `bug-groff' mailing
In my opinion it would be nice if groff had a request that would print
its argument with all hyphenation points visible, reminiscent of the way
some dictionaries render their head words.
E.g., a dictionary may say:
re·ca·pit·u·la·tion
I ask for a groff request because otherwise the hyphenation p
doc/webpage.ms is a nice example of how to do some fairly sophisticated
stuff with groff, putting groff color extensions and the www macro
package on top of the classical ms macro package to make an attractive
hypertext document.
...but it is a maintenance burden to keep up. It appears to be the
At 2018-11-07T01:47:29+0100, Bertrand Garrigues wrote:
> Hi Ingo,
>
> On Mon, Nov 05 2018 at 11:36:42 AM, "G. Branden Robinson"
> wrote:
> >> So here is a complete patch to fix all issues mentioned by Branden
> >> and Bjarni in this thread, unless i missed any.
> >>
> >> I don't think a ChangeL
17 matches
Mail list logo
