Tadziu's opinion matters to me; I read every bit of troff
he posts here because I normally learn something. :-)
Wow. I feel flattered.
But lest I come across as a dinosaur born yesterday and stubbornly
resisting progress, let me explain my position a bit better.
[Warning: aimless
|i wrote:
||2014-09-11 [1]. So here i present a first working prototype for
||mdocmx(7), as above.
ok, hm, well, in mdocmx.sh there is a return at the wrong
position, so i have to take back that mature. Now it is.
And -toc i have extended to take output device arguments.
I'll repost the
Tadziu Hoffmann hoffm...@usm.uni-muenchen.de wrote:
|
lots of interesting stuff skipped
|As an aside at the end, I'm surprised that no-one has yet
|pointed out the obvious: we're working with a macro
|processor, where the natural block structuring element
|is not a tacked-on brace
But it won't match .ds myfruit \lemon, to give one example.
Of course not -- they're different strings. Should they
be considered the same? What about \h'0'lemon?
Or \h'\w'l'u'e\h'-\w'le'u'l\h'\w'e'u'mon?
(They all look the same in print.)
Where do you draw the line?
I believe macros should
Hi Peter,
On Thu, Nov 20 2014 at 02:48:55 AM, Peter Schaffter pe...@schaffter.ca wrote:
Bertrand --
On Wed, Nov 19, 2014, Bertrand Garrigues wrote:
So I've written a very simple example with Mom in French with a
step-by-step explanation on Ubuntu's French documentation page.
Could I commit
On Wed, 26 Nov 2014 17:31:44 +0100
Tadziu Hoffmann hoffm...@usm.uni-muenchen.de wrote:
The syntax of expressions and conditionals isn't what's keeping new
users from using groff. As Peter has already pointed out, the entire
working model of roff presents a much greater mental hurdle than the
Bertrand --
On Thu, Nov 27, 2014, Bertrand Garrigues wrote:
Thanks for your remarks, I will correct my example and commit it. I
have a tendency to add a blank line before or after a HEADING for
clarity pupose in the source file, but this add an extra blank line. I
guess the recommandation
