[bug #60802] Make .substring handle an empty result

Additional Item Attachment, bug #60802 (project groff): File name: substring_test_rev3b.bash Size:4 KB ___ Reply to this item at:

[bug #60802] Make .substring handle an empty result

Follow-up Comment #5, bug #60802 (project groff): Hi Branden, I agree that changing existing expected behavior should be avoided. With 20-20 hindsight, it might have been better to make .substring take OFFSET LENGTH parameters instead of N1 N2 (similar to Perl's "substr"). But that water

[bug #60802] Make .substring handle an empty result

Additional Item Attachment, bug #60802 (project groff): File name: substring_test.bashSize:2 KB ___ Reply to this item at:

[bug #60802] Make .substring handle an empty result

Follow-up Comment #2, bug #60802 (project groff): In the email list where this was reported, Brandon Robinson asked for (1) a unit test for the boundary conditions of the .substring request and (2) a precise description of its slicing semantics in our documentation. Here is a first crack at

[bug #60260] Incorrect warnings of dangling .el with bracket-less nesting

Follow-up Comment #1, bug #60260 (project groff): Forgot to mention that the conditionals work correctly in spite of the warnings. The code also works correctly on Heirloom Doctools nroff, according to Branden's test (with an example tweaked to not use gnu extended syntax). So the groff warning

[bug #57218] [PATCH] Reproducible builds support is broken and embeds timezone

Follow-up Comment #8, bug #57218 (project groff): Commenting as an ordinary user: Please do not make groff ignore TZ. That breaks user functionality (for example \*(DT will be wrong around midnight when using -mm). The build systems should simply run everything with TZ=UTC to make displays be

Minor typos in groff_font(5) man page

Some gobble got into the groff_font(5) man page.  Unsensible bits are hightlighted: "The  depth subfield gives the depth of the glyph, that is, the distance *below the **lowest point below* the baseline to which the glyph extends (downwards is positive); if a glyph *does not extend below above*

[bug #50921] Minor documentation bug (\D' DX DY' args documented reversed)

URL: Summary: Minor documentation bug (\D' DX DY' args documented reversed) Project: GNU troff Submitted by: jimav Submitted on: Wed 03 May 2017 01:06:09 AM UTC Severity: 3 - Normal

Re: \s[] gives syntax error (should restore previous size)

Thanks for fixing the docs. I'm curious, though, why \s can not support the no-argument form in the same way that \f and \F do. -Jim On 03/05/2013 12:07 AM, Werner LEMBERG wrote: # \s[] causes a syntax error. According to 'info groff' # \s with no argument should restore the previous point

\s[] gives syntax error (should restore previous size)

#!/bin/sh # \s[] causes a syntax error. According to 'info groff' # \s with no argument should restore the previous point size # Such behavior would be consistent with \m \f and \F, so this seems likely to be a bug # (using groff 1.22.2 build from cvs) groff -Tps 'EOF' /dev/null .warn .ps 10

un-matched .ie in mm macros (patch)

The mm macros contain a couple of cases of .ie without a matching .el This somehow triggers irrational groff behavior later, for example, occasionally executing both branches of .ie/.el (the exact circumstances are unstable, but may depend on macro nesting depth). Anyway, I had some impossible

Another groff doc typo

The info documentation for .substring says: -- Request: .substring str n1 [n2] Replace the string named STR with the substring defined by the indices N1 and N2. The first character in the string has index 0. If N2 is omitted, it is taken to be equal to the string's length. ...

mm macros put footers off end of page if using larger type

I don't know if anybody is supporting the mm macros, but there is a bug which lands page footers too far down the page (or entirely off the bottom) if you try to make a large type edition of a document. #!/bin/sh groff -mm -Tps 'EOF' | gv - # bottom footer is mostly invisible .\ N.B. Pgps=1 .S

if-else \{\ ... \} docs contain broken example (groff 1.21)

# The groff 1.21 'info' documentation for if-else \{\ ... \} contains an # example which is incorrect. To see the example, run info make # and type /Escape: \\\{ # # Here it is: # # [begin quote] # -- Escape: \{ # -- Escape: \} # In many cases, an if (or if-else) construct needs to execute

.el .ie does not work in groff 1.21

groff 'EOF' .warn .ie 1 .tm action1 .el .ie 0 .tm action2 .el .ie 0 .tm action3 .el .tm defaultaction EOF action1 standard input:4: warning: unbalanced .el request standard input:5: warning: unbalanced .el request ---discussion--- These warnings seem wrong. In .ie cond anything

mm macro .S interferes with .ne command, causing stack-overflow

Hello, There seems to be a bug in either the mm macros or gtroff itself, where if the .S directive is used to change the vertical spacing after a .ne command, then if the text adds up to more than one page-length an abort occurs with fatal error: input stack limit exceeded (probable infinite