x27;m afraid that the other man package simply doesn't
have enough encoding support to do this right in general, and most major
GNU/Linux distributions have switched away from it at this point because
of this.
Cheers,
--
Colin Watson [cjwat...@debian.org]
On Thu, Sep 26, 2013 at 05:55:52PM -0400, Federico Lucifredi wrote:
> On Sep 26, 2013, at 4:32 AM, Colin Watson wrote:
> > Or use man-db instead, which is much smarter about character encodings
> > and handles your situation out of the box with no configuration
> > required
t incremental changes that make
the job easier for the next person, or even "this general pattern of
things you're doing is Unix-specific; you need to use this pattern
instead to be portable to Cygwin".
Cheers,
--
Colin Watson [cjwat...@debian.org]
eral projects to automake and gnulib, and that's how I tend
to build new projects these days. groff is older and more complex than
most, but probably not intractably so.
I'd like to join the chorus of thanks to Werner for his impeccable work
and leadership over the years.
--
Colin Watson [cjwat...@debian.org]
On Wed, Dec 11, 2013 at 11:21:06AM -0500, Eric S. Raymond wrote:
> Colin Watson :
> > I'm happy with the quality of the bzr import we did, and long preferred
> > its UI, but even I have begun moving my projects to git in the
> > acknowledgement that it's won the
On Wed, Dec 11, 2013 at 01:51:49PM +, Colin Watson wrote:
> I expect I'd switch the Debian packaging over to git once there's an
> upstream tree to base it on.
Money, putting where mouth is, etc.:
http://anonscm.debian.org/gitweb/?p=users/cjwatson/groff.git
The recent his
This is based on an old patch from Fumitoshi UKAI in
the Debian groff packaging, cleaned up and extended to cover all fonts
by me.
---
font/devascii/Makefile.sub | 4 ++--
font/devcp1047/Makefile.sub | 4 ++--
font/devhtml/Makefile.sub | 4 ++--
font/devlatin1/Makefile.sub | 4 ++--
font/devut
/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,10 @@
+2014-01-02 Colin Watson
+
+ * contrib/eqn2graph/eqn2graph.sh: Use bash rather than sh; $RANDOM
+ is a bashism.
+ * contrib/grap2graph/grap2graph.sh: Likewise.
+ * contrib/pic2graph/pic2graph.sh: Likewise.
+
2013-12-23 Bernd
c/main.cpp | 4
3 files changed, 14 insertions(+)
diff --git a/ChangeLog b/ChangeLog
index abf7534..2953608 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,11 @@
+2014-01-02 Colin Watson
+
+ * src/preproc/eqn/main.cpp: Define EQ and EN if they are not already
+ defined, to appe
On Thu, Jan 02, 2014 at 02:52:42PM +0100, Werner LEMBERG wrote:
> You have now write access :-)
Thanks!
> Please submit, together with a proper ChangeLog entry.
Yes, I realised I'd forgotten ChangeLog shortly after sending. Done.
--
Colin Watson
On Thu, Jan 02, 2014 at 03:03:48PM +0100, Steffen Nurpmeso wrote:
> Colin Watson wrote:
> |+2014-01-02 Colin Watson
> |+
> |+ * contrib/eqn2graph/eqn2graph.sh: Use bash rather than sh; $RANDOM
> |+ is a bashism.
> |+ * contrib/grap2graph/grap2
ndment A).
Debian has never had any widespread objections to GPLv3, and has
certainly never considered it non-free. Packages using GPLv3 have been
in Debian main for years.
Of course you are entitled to have whatever opinions you like about the
GPLv3 - but please refrai
On Sun, Jan 05, 2014 at 06:06:25PM +0100, Bernd Warken wrote:
> > Von: "Colin Watson"
> > No, this statement about Debian's behaviour is simply untrue and always
> > has been.
>
> That's a lie: http://archive09.linux.com/feature/51576?theme=print
ll the browser on that, using the usual
> man.conf(5) or manpath(1) or whatever mechanisms.
That's indeed basically what "man -H" does in man-db. There are
annoyances with the lifetime of rendered image files, though, and it's
not clear how to solve that (https://b
les relatively easily out of the box today (you just
have to do a separate native build pass so that it can build its own
documentation). I'd hate to see groff switching to something
significantly less battle-hardened.
--
Colin Watson [cjwat...@debian.org]
IBUTIONS
> > OpenBSD - Ingo Schwarze
> > LinuxMint Debian - Keith Marshall
>
> I am NOT the maintainer of the LinuxMint distribution; other than being
> a USER of their Debian Edition, I am, in no way, even associated with
> LinuxMint! For their Debian Edition, I guess ...
>
imestamp of any included file?)
2) Add an option or environment variable or something to suppress the
inclusion of timestamps. For bonus points, set this when building
groff's own documentation.
Thanks,
--
Colin Watson [cjwat...@debian.org]
On Wed, Aug 27, 2014 at 08:28:53AM +0200, Werner LEMBERG wrote:
> Colin Watson wrote:
> > 2) Add an option or environment variable or something to suppress
> > the inclusion of timestamps.
>
> This is the way to go, I guess.
>
> > For bonus points, set
timestamp there is very
useful. The presenter on the topic of reproducible builds at DebConf
today offered to start a support group for people addicted to
unnecessary timestamps. :-)
--
Colin Watson [cjwat...@debian.org]
configure. Running "autoreconf -fi -I m4" fixes it
(Bernd, the need for "-I m4" is documented in INSTALL.REPO; -fi is just
my usual reflex for making sure that autoreconf does everything it needs
to do).
--
Colin Watson [cjwat...@debian.org]
Hi,
The attached patch is the leftover bits of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717608 that have not
yet been applied upstream (as per a git rebase). Original submitter
CCed.
Thanks,
--
Colin Watson [cjwat...@debian.org]
>F
re: gxditview and xtotroff won't be built
I think it would be a good idea to make sure that these directories are
present regardless of configuration.
Thanks,
--
Colin Watson [cjwat...@debian.org]
On Sat, Oct 11, 2014 at 12:03:14PM +0200, Werner LEMBERG wrote:
> Colin Watson wrote:
> > I tried running a test "make dist", importing that into my Debian
> > packaging branch, and building. This failed because
> > src/utils/xtotroff was missing. On looking back
On Sat, Nov 08, 2014 at 01:27:37PM +, Ralph Corderoy wrote:
> Ubuntu's package manager? http://packages.ubuntu.com/utopic/groff says
> 14.10's is currently 1.22.2-8 and that they take Debian's package,
> maintained by Colin Watson (who's on this list). That ve
end of the world not to have it, but that doesn't mean it isn't
useful to work on it now.
More details on SOURCE_DATE_EPOCH (and there are many other useful
things on the same site):
https://reproducible-builds.org/specs/source-date-epoch/
--
Colin Watson
at the next
> step actually is.
As far as I know I don't have direct commit access. I believe my patch
still applies as-is with the exception of ChangeLog, though. Werner,
might you be able to commit it?
Thanks,
--
Colin Watson [cjwat...@debian.org]
On Tue, Jun 14, 2016 at 05:59:26AM +0200, Werner LEMBERG wrote:
> Colin Watson wrote:
> > As far as I know I don't have direct commit access.
>
> You have :-) So please proceed!
Right, so I do, and apologies for the delay. Pushed now.
Cheer
done; \
- if test -d $(DESTDIR)$(devpdffontutildir); then \
- rmdir $(DESTDIR)$(devpdffontutildir); \
- fi; \
if test -d $(DESTDIR)$(devpdffontencdir); then \
rmdir $(DESTDIR)$(devpdffontencdir); \
fi; \
What do yo
ged, 53 insertions(+), 61 deletions(-)
create mode 100755 mdate.pl
delete mode 100755 mdate.sh
diff --git a/ChangeLog b/ChangeLog
index e0263e6c..c73e23c6 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,22 @@
+2017-02-18 Colin Watson
+
+ mdate.sh: rewrite in Perl
+
+ groff already requ
c/doc.am | 4 ++--
2 files changed, 19 insertions(+), 2 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index e0263e6c..76491b1e 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,20 @@
+2017-02-18 Colin Watson
+
+ doc: stop generating W3C validation icons
+
+ Debian's `lintian
On Thu, Jan 02, 2014 at 01:55:05PM +, Colin Watson wrote:
> * src/preproc/eqn/main.cpp: Define EQ and EN if they are not already
> defined, to appease "groff -wmac".
> * src/preproc/pic/main.cpp: Likewise for PS and PE.
>
> Fixes: http://bugs.debian.org/495713
I'
Log b/ChangeLog
index 861f8d80..a571a0be 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,18 @@
2017-02-18 Colin Watson
+ Remove #! lines from non-executable files
+
+ These are always invoked by the build system (either in-tree or via
+ the installed Makefiles) using the nece
On Sat, Feb 18, 2017 at 01:07:38PM -0500, James K. Lowden wrote:
> On Sat, 18 Feb 2017 03:28:03 +
> Colin Watson wrote:
> > This version is much shorter and easier to understand than the
> > shell/awk version: we don't have to worry about convincing ls to
> > pro
the way that mdoc(7) parses its argument list for
callable macro names. An understandable omission given the complexity,
but it does end up being a blocker for me.
This is of course not a deficiency in *roff, but it's a problem in the
wider ecosystem that IMO a serious push towards mdoc(7) ought to
address.
--
Colin Watson [cjwat...@debian.org]
u 17.10. It seems
> ./configure has unexpanded m4 macros.
This should just be a matter of amending INSTALL.REPO (and maybe
doc/automake.mom?) to note that you need pkg-config installed in order
to run ./bootstrap (because the .m4 file it ships must be av
This is more actively maintained, straightforward to integrate now that
we have Gnulib integration, and simplifies groff's overall licensing.
* bootstrap.conf (gnulib_modules): Add `snprintf' and `vsnprintf'.
* configure.ac: Remove local checks for `snprintf' and `vsnprintf'.
* Makefile.am: Remove
, but ./bootstrap will only produce the
mysterious failure that Ralph noted.
(I wouldn't object to it being documented in INSTALL.extra too.)
--
Colin Watson [cjwat...@debian.org]
nts-other a dependency for the groff-base and
> groff packages?
Can't do that, because gsfonts-other is in non-free. (It looks like
perhaps it's a conglomeration of free elements and random stuff like
shareware.) Is there no free alternative that works?
--
Colin Watson
| 10 ++
contrib/hdtbl/examples/common.roff | 6 +-
2 files changed, 15 insertions(+), 1 deletion(-)
diff --git a/ChangeLog b/ChangeLog
index 25b6629..af6de40 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,13 @@
+2018-03-05 Colin Watson
+
+ Remove unnecessary randomness fr
+1,15 @@
+2018-03-05 Colin Watson
+
+ Sort Perl hash keys.
+
+ Hash iteration order may differ between runs, which makes builds
+ harder to reproduce. Sort hash keys in gropdf and afmtodit output
+ to avoid this.
+
+ * src/devices/gropdf/gropdf.pl: Sort hash
due to spacing changes in a comment but
otherwise still applies:
https://lists.gnu.org/archive/html/groff/2017-02/msg00014.html
Thanks,
--
Colin Watson [cjwat...@debian.org]
On Mon, Mar 05, 2018 at 07:55:34PM +0100, Werner LEMBERG wrote:
> Colin Watson wrote:
> > Would it be possible to include these simple fixes in 1.22.4?
> >
> > https://lists.gnu.org/archive/html/groff/2017-02/msg00015.html
> > https://lists.gnu.org/archive/html/
+++ b/ChangeLog
@@ -1,5 +1,18 @@
2018-03-09 Colin Watson
+ build: fix out-of-tree builds without dependency tracking
+
+ The non-recursive-gnulib-prefix-hack module interacts poorly with
+ out-of-tree builds: if configure is run with
+ --disable-dependency-tracking,
be
removed? It can always be retrieved from the git history if anyone
needs it for archaeological purposes.
--
Colin Watson [cjwat...@debian.org]
with that.
In the meantime, "git checkout -- doc/automake_migration_tests.txt"
after "make distclean" should work around it.
--
Colin Watson [cjwat...@debian.org]
/roff/grog/subs.pl| 1 -
8 files changed, 23 insertions(+), 17 deletions(-)
mode change 100755 => 100644 contrib/gpinyin/subs.pl
diff --git a/ChangeLog b/ChangeLog
index 4699a22..d5bb0db 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,22 @@
+2018-03-09 Colin Watson
+
+ Remove
es\~\[mu]\~unitwidth = 7\|620\|000.
-.EN
-.
+\fIres\fR\~\[mu]\~\fIunitwidth\fR\~=\~7\|620\|000.
Although HP PCL\~5 LaserJet printers support an internal resolution of
7200 units per inch,
they use a 16-bit signed integer for cursor positioning;
Thanks,
--
Colin Watson [cjwat...@debian.org]
e'. Setting the executable
bit on them would be quite misleading.
There is one possible exception in the above list: split_env.sh is at
least theoretically useful when executed directly, even though groffer
specifically invokes it using 'sh'. But it's in fact an internal helper
for groffer, so I don't think it really makes sense to suggest that its
executability is part of its interface.
Thanks,
--
Colin Watson [cjwat...@debian.org]
switching instead of embedded font escapes.
Cool, thanks. Your patch seems reasonable to me.
--
Colin Watson [cjwat...@debian.org]
On Sun, Mar 11, 2018 at 11:11:20PM +0100, Bertrand Garrigues wrote:
> You can also commit these two:
>
> https://lists.gnu.org/archive/html/groff/2018-03/msg8.html
> https://lists.gnu.org/archive/html/groff/2018-02/msg00026.html
Thanks. I've done so now.
this autumn.
Similarly, I have this RC in Debian experimental and will upload it to
unstable once officially released, so it should be in Debian 10
"buster". Downstream of that, it's missed the deadline for Ubuntu
18.04, but I expect it to be in Ubun
the resulting warning. The appropriate
language code is of course substituted for %s.
.if (\n[.g] & ((\n[.x] > 1) : ((\n[.x] == 1) & (\n[.y] > 20)) : ((\n[.x] ==
1) & (\n[.y] == 20) & (\n[.Y] >= 2 \{\
. warn (\n[.warn] - (\n[.warn] / 1048576 % 2 * 1048576))
.
On Sun, Apr 01, 2018 at 07:34:44AM +0200, Werner LEMBERG wrote:
> And here (hopefully!) a final version that properly takes the `.g'
> flag into account.
Thanks! I've applied this (with one refinement: I added ".rm Ystring"
to the end, for h
Hi,
The attached input file, when processed as follows:
LC_ALL=ja_JP.UTF-8 groff -mtty-char -mandoc -Tutf8 --- Begin Message ---
Package: man-db
Version: 2.8.2-1
Severity: normal
Running:
man -Tutf8 /usr/share/man/ja/man5/apt_preferences.5.gz
starts outputting the manpage, but then at some p
suggestion, and I'm aware that this is a
bikeshed, but can I suggest a more explicit variable name? Otherwise
the next time some old behaviour needs to be switchably deprecated we're
in for some confusion.
(In my third year in college, I lived in "New Court", built in 1825.)
--
Colin Watson [cjwat...@debian.org]
27;s an absolute path or a relative path containing a slash,
the situation seems quite clear.
> Besides, with the mandoc implementation of man(1), it is not
> absolutely required to update the database even after installing a
> new page into /usr/share/man/.
You can also leave out
On Thu, Apr 19, 2018 at 06:48:19PM +0200, Ingo Schwarze wrote:
> Colin Watson wrote on Thu, Apr 19, 2018 at 10:06:28AM +0100:
> > "man ./apropos.1", as Nate pointed out. man-db's heuristic is that if
> > the page name contains a slash then it's surely a path nam
ines of ChangeLog for the same period?
I'm not really qualified to prepare updates there, but the ratio seems
unusually low to me.
--
Colin Watson [cjwat...@debian.org]
and Scottish Gaelic both have a similar
scheme for pronouncing "ch" as standard German does: if it's surrounded
by front vowels, traditionally called "slender", then it's [ç], while if
it's surrounded by back or "broad" vowels then it's [x]. I don't know
whether the similarity to German is one of common evolution, borrowing,
or just coincidence.)
--
Colin Watson [cjwat...@debian.org]
ugs.debian.org/440047).
There's no good (i.e. configuration-file-based) way for a distribution
to change the default. Could you file a bug report for me as a
reminder?
--
Colin Watson [cjwat...@debian.org]
;ve had here to rebootstrap the build system properly.
--
Colin Watson [cjwat...@debian.org]
ur,
and you aren't going to get one unless the POSIX committee chooses to
clarify it. But POSIX also says that the other return values you're
concerned about simply don't happen, so I'd suggest just picking
whatever syntax you prefer for testing for the cases that do happen and
moving on.
--
Colin Watson [cjwat...@debian.org]
atic analysers: any static analyser capable of handling typical C code
must be able to handle both. (I would be inclined to say the same for
human readers, TBH, although as usual picking one style within a project
and sticking to it is helpful.)
--
Colin Watson [cjwat...@debian.org]
box, in which I suspect I've shamefully neglected to consider the
gxditview case.
--
Colin Watson [cjwat...@debian.org]
ons to man-db (although I don't exactly expect
this to be frequent).
--
Colin Watson [cjwat...@debian.org]
astic
about pushing in a release candidate.
Thanks,
--
Colin Watson [cjwat...@debian.org]
ine" diagnostics,
> but it's quick and intelligible.
This is perhaps me being Captain Obvious, but FWIW adding the -Wbreak
option suppresses those diagnostics.
--
Colin Watson [cjwat...@debian.org]
ey're absent, presumably because
you can use most of groff without them) which then causes the test suite
to fail, which doesn't seem ideal.
Thanks,
--
Colin Watson [cjwat...@debian.org]
me,
so I don't feel bad about sharing emails like this in some form.)
I don't wish to set up any kind of competitiveness with mom here; if you
get unsolicited thank-you mails about it, it sounds like it's doing OK!
But my inbox suggests that man pages do in fact inspire
c prefix, the split between groff-base
and groff is a Debianism), so they can't be committed upstream like
that. Either the local references will need to be omitted, or we'll
need some kind of arrangement along the lines of the existing
@HTMLDOCDIR@ and @PDFDOCDIR@ in groff's man pages (I
On Mon, Dec 24, 2018 at 11:44:54PM +1100, John Gardner wrote:
> Kudos to everyone's hard work! I did my part
> <https://github.com/Homebrew/homebrew-core/pull/35385>. :-)
And me:
https://tracker.debian.org/pkg/groff
All the best,
--
Colin Watson
xpect the opposite.
Thanks,
--
Colin Watson [cjwat...@debian.org]
--- Begin Message ---
Package: groff-base
Version: 1.22.3-9
Severity: minor
Tags: patch
Dear Maintainer,
I used the following to export man pages (ie ssh_config, written in
mdoc-style) to
On Mon, Jan 21, 2019 at 03:04:33PM +0100, Ingo Schwarze wrote:
> Colin Watson wrote on Sun, Jan 20, 2019 at 04:18:29PM +:
> > but much the same problem exists; page numbers are printed on the left
> > of odd-numbered pages and on the right of even-numbered pages,
>
> Isn&
it
might not be worth getting too worked up about the code duplication:
https://metacpan.org/source/DAVIDNICO/ARGV-readonly-0.01/lib/ARGV/readonly.pm
Any other ideas welcome.
Thanks,
--
Colin Watson [cjwat...@debian.org]
--- Begin Message ---
Package: gr
On Wed, Jan 23, 2019 at 03:21:53PM +0100, Jakub Wilk wrote:
> * Colin Watson , 2019-01-23, 13:56:
> > Perl >= 5.20 has the safer <<>> operator,
>
> It was actually added only in Perl 5.22.
Sorry, indeed so - I grepped the perl*delta man pages for it but misread
&qu
of the groff Perl scripts that use `<>'.
Ah, yes - in that case I agree that that isn't a good option.
--
Colin Watson [cjwat...@debian.org]
ace all my accents seems burdensome.
You wouldn't actually modify your files, but just have the build script
you use to render them add the -k option.
--
Colin Watson [cjwat...@debian.org]
The "<>" operator is implemented using the two-argument form of "open",
which interprets magic such as pipe characters, allowing execution of
arbitrary commands which is unlikely to be expected. Perl >= 5.22 has a
"<<>>" operator which avoids this, but also forbids the use of "-" to
mean the stand
On Thu, Jan 24, 2019 at 03:38:38PM +, Deri wrote:
> Have you seen:-
>
> https://savannah.gnu.org/bugs/?7
>
> Perhaps the patch could be uploaded there?
Thanks, I hadn't seen that. Done.
--
Colin Watson [cjwat...@debian.org]
x27;d support it.
FWIW, this was gnulib upstream, not man-db / libpipeline upstream (i.e.
me).
If somebody could point me to where I could get SSH access to a macOS
box with the right set of build tools installed, I'd be happy to try to
get it working
On Thu, Jan 24, 2019 at 04:21:51PM +, Colin Watson wrote:
> On Fri, Jan 25, 2019 at 02:10:32AM +1100, John Gardner wrote:
> > There was an attempt to get man-db
> > <https://github.com/Homebrew/homebrew-core/pull/25376> accepted in
> > Homebrew, but a patch was need
On Mon, Jan 28, 2019 at 07:59:00PM +1100, John Gardner wrote:
> *> Would anyone who uses a Mac and is reasonably Homebrew-literate like to
> pick this up?*
>
> Done! See https://github.com/Homebrew/homebrew-core/pull/36469 (I CC'd you
> on GitHub anyway)
Th
don't have a robust mechanism for
sshd to pick some other suitable locale that at least has a matching
encoding, and the details of this would no doubt be difficult to define
anyway; so the upshot is that somebody in this situation ends up with
the equivalent of LC_ALL=C on
be a matter of somebody who can do test-builds on Windows
making sure that we're importing the right set of Gnulib modules.
(It's possible that some of the _WIN32 conditionals can be supplied by
Gnulib these days, but there's also no great urge
On Thu, Feb 14, 2019 at 07:30:13PM +0200, Eli Zaretskii wrote:
> > Date: Thu, 14 Feb 2019 12:50:09 +
> > From: Colin Watson
> >
> > If it's just the runtime, then Gnulib should be able to paper over a
> > pretty fair number of the differences, and groff alr
fonts were definitely there in 1.22.3.
It's likely that this is a bug in the Homebrew formula: you can confirm
this by looking for "URW fonts for pdf" in the configure output (it
should say "yes", but I bet it says "no"). The fo
On Thu, Jan 24, 2019 at 02:34:35PM +, Colin Watson wrote:
> The "<>" operator is implemented using the two-argument form of "open",
> which interprets magic such as pipe characters, allowing execution of
> arbitrary commands which is unlikely
Thanks for the review.
On Fri, Mar 01, 2019 at 04:41:36PM +, Deri wrote:
> On Thursday, 28 February 2019 19:42:45 GMT Colin Watson wrote:
> > On Thu, Jan 24, 2019 at 02:34:35PM +0000, Colin Watson wrote:
> > > The "<>" operator is implemented using the two-ar
agic" two-argument open is too magical for you,
then the obvious next thing to use is the non-magical three-argument
open, not sysopen.
So, even if that document from 1999 remains authoritative on how to
perform safe escaping, I don't think it's any longer authoritative on
style.
free software circles, much less something that one can claim with a
straight fact to be "objectively correct".
--
Colin Watson [cjwat...@debian.org]
le to
likewise hear the primes being counted off. We eventually got somebody
who'd worked on the original machine to come and listen to it: he told
us that it really sounded nothing like the original but it clearly
fulfilled the same purpose. Good enough for us co
oes this too, doesn't it? I think the way you're supposed
to handle this at the moment is to run preconv before other
preprocessors, including refer.
--
Colin Watson [cjwat...@debian.org]
On Mon, Nov 04, 2019 at 01:31:06AM -0800, Dale Snell wrote:
> For the Norwegian characters, you'll need to use constructions like "\[o/]"
> and "\[ae]".
Alternatively, run your input file through "preconv" as the first
preprocessor.
--
Colin Watson
f5109dbdcb72b074b99517
CCing Peter, FYI.
--
Colin Watson [cjwat...@debian.org]
'
I expect that this failed simply because the previous bootstrap command
had failed, as described in the other thread you posted today. If you
git pull, it should work now.
--
Colin Watson [cjwat...@debian.org]
Based on a patch from Guillem Jover .
* tmac/doc-common-u: Update NetBSD, OpenBSD, FreeBSD, Darwin, and
DragonFly version strings.
* tmac/groff_mdoc.7.man: Synchronize.
Fixes: https://bugs.debian.org/867123
---
tmac/doc-common-u | 120 ++
tmac/groff_m
On Tue, Dec 17, 2019 at 01:14:06PM +, Colin Watson wrote:
> Based on a patch from Guillem Jover .
>
> * tmac/doc-common-u: Update NetBSD, OpenBSD, FreeBSD, Darwin, and
> DragonFly version strings.
>
> * tmac/groff_mdoc.7.man: Synchronize.
Side note: I am not the biggest fa
em, so i just stuck to existing practice as
>best i could.
Thanks. I have no complaints with these - I wasn't completely sure what
I was doing and am happy for the corrections.
(There was a small typo, which I've fixed on master. It's very easy for
one'
;;
}
else {
...
snprintf(sprintf_buf, sizeof(sprintf_buf),
one_format.contents(), v[i++]);
result += sprintf_buf;
}
one_format.clear();
But I understand if you'd prefer not to do that here.
--
Colin Watson [cjwat...@debian.org]
ated PDFs. That
said, with current git master on Debian unstable, all the tests pass for
me right now.
--
Colin Watson [cjwat...@debian.org]
1 - 100 of 183 matches
Mail list logo
