public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: w3m displays blank help page
Date: Thu, 30 Dec 2021 08:13:15 +0100	[thread overview]
Message-ID: <459e912d-e77b-4b66-22e5-308e1ade4a28@gmail.com> (raw)
In-Reply-To: <20211230011326.GB28615@phoenix>

On 30.12.2021 02:13, Gary Johnson wrote:
> On 2021-12-29, Ken Brown wrote:
>> On 12/29/2021 4:44 PM, Gary Johnson wrote:
>>> So, I have
>>> a workaround for the problem, but I'd really like a proper fix, and
>>> there may be other users with this problem.
>>
>> w3m currently has no maintainer.  Would you like to take over?
> 
> Possibly.  Let me take a look at fixing it properly and if I can
> figure that out, I can probably manage maintaining it.
> 
> I didn't see any Cygwin-specific docs or maintenance notes among the
> package or source files.  That must mean that there's nothing to it.
> 
> Regards,
> Gary
> 
> 

See
https://cygwin.com/packages/x86_64/w3m-src/w3m-0.5.3-3-src

the cygwin source package has several patches.

I suggest you to try rebuilding it to familiarize with the
cygport tool.
It is possible that the changes in the build tools need
some adjustment after all these years..


After the

    cygport w3m.cygport prep

step, you can add your patch to the "src" subtree and cygport
will produce during packaging phase a new patch that you can rename
and add to the existing one in the w3m.cygport.

You can ask more info in the "cygwin-apps at cygwin dot com"
mailing list.
https://cygwin.com/mailman/listinfo/cygwin-apps




      reply	other threads:[~2021-12-30  7:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29 21:44 Gary Johnson
2021-12-29 22:17 ` Ken Brown
2021-12-30  1:13   ` Gary Johnson
2021-12-30  7:13     ` Marco Atzeri [this message]

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=459e912d-e77b-4b66-22e5-308e1ade4a28@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).