discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Jan Stary <hans@stare.cz>
To: discuss@mandoc.bsd.lv
Subject: Re: Possible to add optional bzip2 support?
Date: Sun, 29 Nov 2020 22:07:32 +0100	[thread overview]
Message-ID: <X8QNk7dTJCxQ92XH@www.stare.cz> (raw)
In-Reply-To: <20201129201424.GI58187@athene.usta.de>

Hi Ingo,

On Nov 29 21:14:24, schwarze@usta.de wrote:
> It would be easier to convince me to delete *.gz support than to
> add *.bz2 support.  Either is unrelated to the purpose of mandoc
> and linking to zlib is ugly and messy, i'd love to get rid of the
> dependency and of the rather ugly and error-prone code needed to
> support *.gz files.

would you please kindly consider removing the gz support from mandoc?
The linking is messy, the code needed to support *.gz files is rather
ugly and error-prone, and the (un)compression is unrelated to the
purpose of mandoc in the first place.

	Jan

--
 To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv


  reply	other threads:[~2020-11-29 21:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d5e55c57-002a-e654-b7c2-dca9fb84863d@aisha.cc>
2020-11-29 20:14 ` Ingo Schwarze
2020-11-29 21:07   ` Jan Stary [this message]
2020-11-29 21:41   ` Aisha Tammy
2020-11-29 22:24   ` Kazuo Kuroi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=X8QNk7dTJCxQ92XH@www.stare.cz \
    --to=hans@stare.cz \
    --cc=discuss@mandoc.bsd.lv \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).