Hello, all
`groff -man -Tutf8' does not seem to handle font
styles on my terminal. I have made sure that plain
`groff' works as expected:
This is
.ft B
strange
.ft R
indeed.
. Branden Robinson to Anton Shepelev:
> > instead of using ANSI control codes, and this has no
> > intended effect. How can I cause `-man -Tutf8' to use
> > ANSI codes?
>
> Check your environment for variables named "GROFF_SGR" (a
> Debianism) and "GROFF_
G. Branden Robinson to Anton Shepelev:
> > `export | grep -i sgr' finds nothing, unfortu-
> > nately. Where else can I look for the reason of
> > -man treating my virtual terminal as a printer?
> > Once I find it, I will bring it up with the ad-
> > minis
G. Branden Robinson to Anton Shepelev:
> > I wonder what Debian user or developer dis-
> > liked those SGR sequences emitted by groff...
>
> Well, here's one of them.
>
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=312935
>
> ...with my leng
Jim Hall:
> Several weeks ago, I interviewed Dr. Marshall Kirk
> McKusick about how he writes his books using groff:
> https://technicallywewrite.com/2023/10/13/groffbooks
McKusick writes about orphan elimination, end-of-
line tweaking, and balancing of text on facing
pages. Does that
Anton Shepelev wrote to G. Branden Robinson:
> > Check your environment for variables named "GROFF_SGR"
> > (a Debianism) and "GROFF_NO_SGR". Unset them both and
> > try "groff -man -Tutf8" again.
>
> `export | grep -i sgr' finds nothin
Hello, all
What is the covenstional way of documenting a set of C
functions with -man? Have you any recommendations or
examples about typesetting function declaraions, their
return types and aruguments in a classic man-page? The .SY
macro does not seem to work well for C, because its function
de
G. Branden Robinson to Anton Shepelev:
> > This means that one must /set/ rather than unset
> > GROFF_SGR to restore the normal nroff behavior.
>
> This advice, while still applicable to groff 1.22.4, is
> becoming stale. Distributors that introduced the
> GROFF_SGR Debia
G. Branden Robinson:
> People frequently run into trouble because they usually
> don't want the text of function prototypes filled, but the
> prototypes can also get lengthy, and they don't know how
> to make the text adapt to the available terminal width in
> the absence of filling. (Short answe
G. Branden Robinson, just quick commentincle on this:
> So if "adjustment" is, as I claim, "the widening of
> the spaces between words until glyphs abut both the
> left and right margins", well, that's clearly not hap-
> pening here.
No, it is not. What you describe is "both" adjustment,
hj.oertel:
> by default groff generates PS, using the flag
> -Tps. In Linux you can convert it to PDF using
> the ps2pdf tool.
Ditto on Windows, just install Ghostscript for this
OS: http://ghostscript.com/download/gsdnld.html .
--
() ascii ribbon campaign - against html e-mail
/\ h
I wrote seven years ago:
> OK, I have modified the patch (attached).
>
> But I am not sure how mm is supposed to handle
> long signatures if they spread across the page
> boundary: should it treat the .FC + .SG combina-
> tion as an indivisible keep or not, e.t.c.; so I
> did it the si
Damian McGuckin:
> I went back to a very old document using troff and
> MM. It is a tutorial on using troff at the macro
> package level without needing to know much about
> the low level troff. I was contemplating updating
> it and putting it out there.
>
> I am trying to use a display wi
Damian McGuckin:
> I went back to a very old document using troff and
> MM. It is a tutorial on using troff at the macro
> package level without needing to know much about
> the low level troff. I was contemplating updating
> it and putting it out there.
>
> I am trying to use a display wi
Damian McGuckin:
> The bug is that while
>
> .DS 1
>
> uses the standard indent,
>
> .DS 1 1
>
> does NOT use the standard indent.
Let us maybe share some examples of a) the current
and b) the expected behavior. This e-mail is for-
matted using mm, w
Damian McGuckin to Anton Shepelev:
> As you noticed, that 1.22.4 version of '-mm' solved the
> fill-mode problem with '.DS'.
>
> However, when you use
>
>.DS 1
>.EQ (X)
>... equation
>.EN
>.DE
>
> it places put the
Hello all!
I can't figure out how to make nroff with the -me package output
text without inter-page space. Whatever I do, it keeps putting
one empty line between pages.
I have set the tm value to zero, and when I try to zero the bm
(bottom margin) value, nroff exits with a crash saying: input
st
Hello, Ralph
I don't know -me so can't answer on your specific problem. But have
you
tried making the page length very long instead of trying to remove the
inter-page
Yes, that was the first thing I did. Although I works, the
"functinality"
of this method is a bit scantier bacause there'
Ralph Corderoy:
I don't know -me so can't answer on your specific problem. But have
you
tried making the page length very long instead of trying to remove the
inter-page gap?
And there's another annoyance to this method: the output file will
containt at
leat one whole page, Imagine writti
Mike Bianchi
To format a document of arbitrary length as _one_ nroff page
I use this trick.
First, set the page length _very_ long.
.pl 9
And then make the last two lines of input a line break and
setting the page length to the _current_ page length.
.br
Hello all,
Is there a way to make nroff process Russian documents cor-
rectly and with hyphenation?
Anton
Thank you for the reply, Werner!
I have found all the files: koi8-r.tmac, ru.tmac and
hyphen.ru (in the koi8-r encoding). The koi8-r.tmac file
consists of lines like:
.trin \[char186]\[u2568]
and I believe it maps UTF-8 to KOI8-R, hence I cocluded the
input file should be in the U
I have made a break-through! I have made hyphenationn work
by just referring to latin1.tmac instead of koi8-r.tmac from
ru.tmac. Can anyone explain me how and why it works?
With koi8-r.tmac I keep getting that "Special symbol" er-
ror...
> > I have found all the files: koi8-r.tmac, r
Hello all,
I have read that the easiest way to convert
groff output to text is to filter it using
the col command.
I tried this:
groff -man -Tlatin1 test.man | col -bx,
but in the result section names still con-
tained color-setting characters:
1mSection one0m
Is one of the tools (groff or
Thank you, Werner and Ralph.
And I was using sed :P
Hello all,
I was experimenting with displays in groff (nroff
mode) and found found a problem. Whenever I begin
a new paragraph after a display, the vertical in-
dent after the display is twice the normal size.
Below is an example for the MS macro's .LD dis-
play:
.LP
Test paragraph. T
Ted Harding:
> If you are using ms macros, then there are two number registers
> to watch out for: \n[PD] "paragraph drop" and \n[DD] "display
> drop". \n[PD] defines how much vertical space will be inserted
> before starting a new paragraph. \n[DD] defines how much vertical
> space will be insert
>> Ted Harding:
>>
>>> If you are using ms macros, then there are two number registers
>>> to watch out for: \n[PD] "paragraph drop" and \n[DD] "display
>>> drop". \n[PD] defines how much vertical space will be inserted
>>> before starting a new paragraph. \n[DD] defines how much vertical
>>> space
Hello all,
I want the headers (.NH) automatically create TOC entries,
for which reason, right in my document's file, I defined
the following macro:
.de HD
.NH \\$1
\\$2
.XS
\\$2
.XE
..
which creates both a header and a TOC entry for it, so I
would no longer bother about the actuality of my TOC.
> In the GNU ms macros, the name "HD" seems to be reserved
> for a user-supplied page header and/or footer macro, which
> (if it exists) gets called at some place during the page
> initialization. Since you have defined HD, this gets called,
> and in turn calls XS and XE but with no useful text (s
Hello all,
Is it possible to modify the MS macro package
(by adding some macro (re)defintions) so it
would make all headings stick out to the left
by the same abount of space?
1. Heading One
text text
text text
1.1 Heading One.one
text text
text text
text text
2. Heading Two
text
Hello all,
I am learning the MM macro package and have met a couple of
problems I couldn't solve after reading the man page:
(1) Is it possible to omit the standard page headers
without using .LT?
(2) My test document begins with a call to the .PGFORM
macro, setting
Mike Bishop:
> Anton,
>
> Everything I learned about MM I learnt from the SystemV/AT
> documentation from Microport. I have never found a copy of
> that documentation as source on the net. I *did* find a
> scanned image of the docs however, at
> http://www.tenox.tc/docs/
> under the
> Micropor
Tadziu Hoffmann:
>
>> I have followed you instructions and still couldn't eliminate
>> the vertical margins. [...]
>
>> .VM 0u 0u
>
> Use ".VM -T 0u 0u". Without the "-T", the arguments specify
> *extra* space to add.
Thank you, and sorry for the bothering. I did read
it in the man-page but m
Mike Bianchi:
> Let's try again:
>
> I've commented out .PGFORM, .PH and .VM.
>
> I've replaced them with the nroff/troff/groff basic commands
> .pl page length
> .ll line length
> .po page offset
>
Thank you, Mike.
Tadziu HOffman has poin
> > If it wasn't due to my bad English, may I suggest
> > a different wording: [...]
>
> I've committed something along your suggestion, thanks.
>
>
> Werner
Thanks to you, Werner :)
Hello all,
When I saw how MM formats headers the first thing
that stroke me was the lask of hanging indent for
multiline headers, so I did these little modifica-
tion:
.de HY
.length a \*(}0
.in +\nan
.ti -\nan
.nr ;0 2
..
.de HZ
.in 0n
..
Me:
> Hello all,
>
> When I saw how MM formats headers the first thing
> that stroke me was the lask of hanging indent for
> multiline headers, so I did these little modifica-
> tion:
Sorry, I forgot to escape slashes in the source
code, so all double slashes turned to single ones.
Here's the
Mike Bianchi:
> Anton,
>
> Since HX, HY and HZ are initialized as empty, and hence no-ops, using them to
> do anything that works for you is just fine.
>
> The one thing to be careful of is using knowledge of the implementation
> obtained by reading the code. Any of that can be changed.
>
> In
Hello all,
I have found a difference in groff's behaviour on
my home computer (groff 1.19.2) and at work (groff
1.20.1). Note the vertical spacing and the merging
of paragraphs:
Here's the first test file:
.de TP
..
.de EOP
..
.PGFORM 60n v 0n 1
.de HY
.length antI \\*(}0
.in +\\n[antI]n
.t
Thanks to everybody )) and especially to Mike Bianchi for
volunteering to fix the bug.
By the way, what about Jurgen Hogg, the author of m.tmac
whose e-mail is still in the file as the address to sent bug
reports to?
Anton
Hello, all
I often need to typeset single hanging paragraphs
like:
PS: Example of a post-scriptum, it has a hanging
indent.
I have created a macro for this, which
1. Calculates the length of the label and
increments it by one,
2. Begins a variable-item list (MM's .VL)
Ted Harding:
> One "hack" which might lead to what you want is to calculate an
> indent based on the width of the tag "PS: ", and then increment
> the line-indentation once the paragraph has been started (but
> you would need to reset it at the end of the paragraph):
> (Note the use of the unstret
Mike Bianchi:
> Anton,
> Could you just use \ to continue the macro onto your next line?
>
> .MyMacro FirstArg \
> All the text that is processed by MyMacro FirstArg follows.
Thanks for the hint. I thought about it and con-
sidered it a sort of 'quick and dirty' (not
en
Me:
>
> I have made your code a bit simpler:
>
>.nr indnt 120
>.in +\n[indnt]u
>.ti -(\n[indnt]u)
>PS:\ Example of a post-scriptum, it has a hanging indent.
>.in -\n[indnt]u
I forgot to escape the \w request (first line).
Here's the corrected verstion:
.nr indnt \w'PS:
Mike Bianchi:
> When I do need something special or "improved" then I make my own macro
> and carry it around with me. I have my own MM macros that I
> have carried around for decades, going back to my days at Bell Labs.
I wonder, how do you 'deploy' your own MM macros?
Just pick the ones y
Ralph Corderoy:
> Hi Anton,
>
> > I can manage a two-part macro like .(MyPS and .)MyPS, so I could
> > reset the indent upon exit. But I don't know how to do it using only
> > one macro. I probably have to 'subscribe' to some 'call-back' macro
> > that gets called every time a paragraph (
Tadziu Hoffmann:
>
>> I can manage a two-part macro like .(MyPS and .)MyPS,
>> so I could reset the indent upon exit. But I don't know how
>> to do it using only one macro. I probably have to 'subscribe'
>> to some 'call-back' macro that gets called every time a
>> paragraph (in groff's
> Ah, yes. In the manpage macros, this works similarly: all
> paragraph macros reset the indent to what it "should" be
> (so that any ".in" invocations within a paragraph will be
> undone at the beginning of the next paragraph). That is,
> ".TP" absolutely sets the indent to "something" + "extra"
> Ah, yes. In the manpage macros, this works similarly: all
> paragraph macros reset the indent to what it "should" be
> (so that any ".in" invocations within a paragraph will be
> undone at the beginning of the next paragraph). That is,
> ".TP" absolutely sets the indent to "something" + "extra"
On 3 Jun 2010 at 10:01, Ralph Corderoy wrote:
>
> Hi Anton,
>
> > The trap is set by .it 1 an-trap, so I why is it
> > fired after the section text even is it was passed
> > to .SH as parameter? Are macro parameters handled
> > as input lines?
>
> No, I think you'll find it's this line,
>
>
Maybe this document will be of interest for the
readers of this thread:
http://2009.asiabsdcon.org/papers/abc2009-P6B-paper.pdf
Anton
Hello all,
I have found a problem with pagination in MM. In
the following example, the bottom margin is dif-
ferent for the first page (which ends with a
filled line of text) and the second page (which
ends with a non-filled line of a footnote). To the
left is the source and to the ri
Hello all,
Looks like my previous message's text was over-
wrapped by the mailing list engine. It looks that
way in the mailing list archieve. If was not a
display problem and you recived the garbled ver-
sion, I'll re-post my message.
Sorry for the inconvenience,
Anton
Tadziu Hoffmann:
> Anyhow, the upshot of all this is that if you're only working
> with character-cell devices with fixed baseline spacing, just
> remove the "+1v" and all should be fine. If you're also using
> high-res devices, you'll probably need to rethink mm's setting
> of trap positions. (
Tasziu Hoffmann:
> Yes, of course. But that "+1v" is also "wrong" in troff mode.
> Better to always use
>
> 'sp |\\n[pg*foot-trap]u
>
> (without the "+1v") in addr...@hidden, and
>
> .if n .wh \\n[pg*foot-trap]u addr...@hidden
> .if t .wh \\n[pg*foot-trap]u-1v+1u addr...@hidden
>
Tadziu Hoffmann:
> [...]
>
> > .am p...@set-new-trap
> > . if n \{\
> > . if \\n[ft*note-size]>0 .nr pg*foot-trap -1v
> > . \}
> > ..
>
> I think that leaves you with more space before the footnotes
> than necessary in nroff (but the bottom margin is okay),
> but in troff you still ha
Macro names containing the e-mail 'dog' symbol got
replaced with addr...@hidden. Here's an updated
version, where [dog] is used istead of the actual
symbol:
.am pg[dog]set-new-trap
. if \\n[ft*note-size]>0 \{\
. nr pg*foot-trap -1v
. \}
..
.am pg[dog]enable-trap
.
Tadziu Hoffmann:
The error must have been introduced between
1.19.2 and 1.19.3, and it's a bug in the mm
macros, not in troff, as you can see by sourc-
ing the 1.19.2 mm macros with troff 1.20.1
(and vice versa).
If you edit the current mm macros and move the
addr
Hello all,
Nested lists work well in MM most of the time, but I
have just found a situation wherein MM seems to have
a problem:
.de TP
..
.de EOP
..
.PGFORM 40n 20v 0u
.BVL 2
.LI "Correct:"
This item looks ok.
.AL
.LI
One
.LE
.LI "Incorrect:"
After .AL, o
Tadziu Hoffmann:
> BVL's list type is "-1". When LE restores the
> outer list's settings via l...@pop and m...@pop-nr,
> the list type is reset as
>
>.nr \$2 \*[misc*pop]
>
> where \$2 ist the register name (in this case,
> "li*type") and \*[misc*pop] is the saved type (in
> this ca
Hello all,
I think, although it is not explicitly documented,
it is inferrable from the desctiprion of the \n
escape:
Interpolate number register with name IDENT
(one-character name I, two-character name ID).
This means that the value of the register is
expanded in-place
Ted Harding:
> That -- the asymmetry -- is also my feeling
> exactly! However, I think the increment/decrement
> operation is best left alone! Consider:
So you show a way to make Groff do what you want it
to do, but my mind either inattentive or lazy and
therefore prone to human m
Hello all,
I am trying to adopt tbl for typesetting tables and
have found one problem that I don't know from which
side to approach. It is connected with table width.
How to make my tables' width dependent on the line
length setting? For example, should I want to type-
set my document with
Mike Bianchi:
> Are you using the expand global option? See
> tbl(1). That makes the table as wide as the line.
No. It doesn't allow me to decide which column to
stretch.
Anton
Werner Lemberg:
> Then what about the `x' column specifier?
Thanks. I was 'fixed' on the 'w' specifier.
Ted Harding:
> Meanwhile, looking for something "clever"...
May I ask you if you have found it?
Anton
Hello, Ted
> Well, this is an approximation to "something
> clever", but it is definitely "work in progress"!
See how your example can be rewritten using tbl's
registers:
The line below is the current line-length:
.br
\D'l \n[.l]u 0'
.TS
tab(#);
|l2 | l2 | l2 | l |.
Hello all,
I have found what may be a bug either in tbl or in
groff's \D request. Or I don't understand how either
works. The same piece of code typesets differently
in troff and nroff modes:
.ll 36n
.br
The line below should be the current line-length:
.br
\D'l \n[.l]u 0'
.
Here's a simpler example in which the length of the
line produced by the \D'l' request differs twice in
nroff and troff:
.ll 36n
.br
The line below should by one symbol long (one "en"):
.br
.sp 1v
N - this is for reference.
.br
.if t .sp -0.8v
\D'l 1n 0'
Here's the nr
Hello, Werner.
Many thanks for the info. I see that the problem
lies deeper than I had thought.
> It's obvious that the values 0..23 are somehow
> 'assigned' to character cell 0, and for orthogo-
> nality we have to assign position 24 already to
> character cell 1.
This is indeed on
Werner Lemberg:
> I've just tested heirloom troff, and it doesn't
> support \D'l ...' with nroff. Consequently, I
> think AT&T nroff doesnt' do it either.
Does this mean that tbl can't make horizontal rulers
in its tables in nroff mode, or is the drawing of
them implemented bypassing \
Ted Harding:
> When you use the 'ms' macros, there is no macro
> ".PO", so your ".PO 0" would have no effect.
The lack of warning/error messages can be mislead-
ing. At least, it had been so with me until I dis-
covered that they must be turned on with the .warn
request.
Werner, would
Werner LEMBERG:
> Mhmm. I don't think so. Compare this to gcc's -W
> switches which are off by default too. I don't
> see an immediate need to change a behaviour which
> has been unmodified for more than 20 years.
But there is a difference compared to gcc. Missing
(undefined) macros ar
May the earth be soft to him.
Hello all,
I thought I had solved all encoding problems until I
tried to export my documetns into the HTML format.
It seems that my understanding of how groff maps
input charactes into its internal charactes and then
into output glyphs is incomplete. Below I have
described what I was d
Michael Witten:
> 7i/2u=> ((7i)/2)u => 3.5iu <--- WTF?
Numeric registers are dimentionless, and the speci-
fied unit of measurement only affects how the dimen-
tionless value it follows is to be scaled. In this
example:
1. 7i = 7 * 240 = 1680 (because 1i = 240u),
2. Then this valu
Myself:
> 1. I tried to define glyphs for the characters
> reported in the abovementioned warnings, in
> the ...\fontevhtml\r file like this:
> [...]
Now I am trying to understand a very simple case:
for the latin1 device, no font definition contains a
glyph named [`A]
Another pecuilarity: When I use:
troff -mkoi8-r -Thtml test.roff > test.out
it works correctly and does not issue any warning
messages, but the command
pre-grohtml troff -mkoi8-r -Thtml test.roff > \
test.out
does issue the "can't find special character" warn-
ings. What is it that
Myself:
> Now I am trying to understand a very simple case:
> for the latin1 device, no font definition contains
> a glyph named [`A], while it is this glyph that
> [char192] maps to (by latin1.tmac). And this works
> correctly without any warning messages. Where does
> groff take the definiti
Werner,
> For me it works [...]
Sorry, I checked it again and it had the expected
effect. Must have been doing something wrong.
> ??? I have this line in font/devlatin1/R:
>
> `A 24 0 0300
I already got it and wrote about it, but the post
probably made it to the list too late.
> These
Werber Lemberg:
> BTW, does my suggestion w.r.t. Cyrillic PS fonts
> work?
Yes.
Anton
Werner Lemberg:
> Note that you are the first who reports this prob-
> lem.
Actually I did report it under the subject of ".SY
macro of the Man package" on the bug-groff mailing
list on the 12th of October, 2009.
The solution was to delete an obsolette version of
an-old.tmac from the "sha
Werner Lemberg:
> Have you reported it to the GNU Win32 people?
> Apparently, this hasn't been fixed yet.
I done done it:
In the groff 1.20.1 distribution the package
an_old.tmac located at
GnuWin32\share\groff\site-tmac\an_old.tmac
is outdated, while the correct up-to-da
Werner Lemberg:
> > I['ve just] done it:
>
> Thanks!
This is the slang of the black proletarian people of
America and can be heard on early blues and r&b re-
cords:
Oh see, see rider,
Just see what you done done,
You done made me love you,
And now your man done come.
Anton
Werner Lemberg:
> These warning messages are harmless. Reason is
> that grohtml processes the input twice: One time
> with -Thtml for text and a second time with -Tps
> for everything which grohtml can't handle. This
> second run causes the warning messages.
> [...]
> Admittedly, this i
Hello all,
I have returned to the problem with vertical indents
around headings in MM and found the cause of it. The
problem disappeared when removed the call to
.DEVTAG-EO-H macro from the definition of the .H
macro. The devtag macros seem to conflict with MM's
.SP macro.
Then I a
Werner Lemberg,
> This looks fine. Are you going to send a real
> patch?
Yes. I posted this for review, because otherwise
reviewing would require applying the patch...
Sorry for the long delay, but even when making small
patches a newbie finds it necessary to learn a lot
about the th
> This looks fine. Are you going to send a real patch?
Attached is the patch for grohtml.man.
Anton
--- grohtml_cur.man 2010-10-30 23:15:36.0 +0400
+++ grohtml_a.man 2010-10-30 23:29:22.0 +0400
@@ -99,6 +99,23 @@
.B \-P
option.
.
+.PP
+.B grohtml
+invokes
+.B groff
+
Myself:
> The devtag macros seem to conflict with MM's .SP
> macro.
The problem is that the .tag request confuses the
.br request
Here's an example:
.warn
.mso devtag.tmac
break before .tag:
.br
.br
.DEVTAG-EO-H
after
.sp 1v
break after tag:
.br
.DEVTAG-EO-
Werner Lemberg:
Thanks! I've applied it, with slight modifications.
Attached is the patch for groff.texinfo. Compared to
the corresonding man patch with Werner's correc-
tions, I've only added one clause to the end.
Anton
groff.texinfo.diff
Description: Binary data
Myself:
> The problem is that the .tag request confuses the
> .br request.
I do not understand why the output of a tag-unaware
device can depend on tags. I still think it is a bug
or a design problem.
I have successfully used input line traps to fix
this for my particular task (no drawi
I wrote:
> I do not understand why the output of a tag-
> unaware device can depend on tags. I still think
> it is a bug or a design problem.
Is it so stupid a question? Is this side effect of
the .tag request documented anywhere?
Anton
Werner Lemberg:
> However, I haven't had time yet to even think
> about your particular problem, sorry. All your
> emails are sitting in my input queue...
Then I wish you to have more time for groff and
other joyful things that you like.
Anton
Sergio Villone:
> I wonder: is the groff manual written with
> groff? if the answwer is "yes" is the source to
> this manual available anywhere? just to have a
> working example specially for the front cover and
> the toc... thank you in advance and sorry for
> bothering :-)
Werner Lemberg:
> the vertical effect of .DEVTAG-EO-H is cancelled;
> this works just fine with your example. Can you
> try whether this works with your documents as a
> patch to to mm also?
OK, I'll try it. I got a bit sick now and it's hard
for me to work at the PC, but I'll do it s
Werner Lemberg:
> I don't think so. .DEVTAG-EO-H is very low-level
> (and since of its beta nature, neither .tag nor
> .taga are documented at all); it's a bad idea IMHO
> to hardcode any typographical behaviour with it.
I still cannot agree with it, because the modifica-
tion in question
Werner Lemberg:
> I don't think so. .DEVTAG-EO-H is very low-level
> (and since of its beta nature, neither .tag nor
> .taga are documented at all); it's a bad idea IMHO
> to hardcode any typographical behaviour with it.
I still cannot agree with it, because the modifica-
tion in question
Werner Lemberg:
> > > I don't think so. .DEVTAG-EO-H is very low-
> > > level (and since of its beta nature, neither
> > > .tag nor .taga are documented at all); it's a
> > > bad idea IMHO to hardcode any typographical
> > > behaviour with it.
> >
> > I still cannot agree with it, becaus
Werner Lemberg:
> This patch I actually dislike since it essentially
> means that after DEVTAG there is always a line
> break, which is too strong an assumption
There's no such assumption.
-- If a call to DEVTAG is followed by a break then
its side effect is eliminated.
-- If a cal
Werner Lemberg:
> This patch I actually dislike since it essentially
> means that after DEVTAG there is always a line
> break, which is too strong an assumption
Sorry, you probably mean the resetting of the
horisontal position. I now get it.
Sorry for bothering,
Anton
1 - 100 of 220 matches
Mail list logo
