From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] scandir
Date: Thu, 01 May 2014 20:05:24 -0700 [thread overview]
Message-ID: <87fvksubgr.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20140328123843.eklhad@comcast.net> (Karl Dahlke's message of "Mon, 28 Apr 2014 12:38:43 +0000")
Karl Dahlke <eklhad@comcast.net> writes:
> I was just wondering if we should switch all this over to scandir,
> it would definitely be less code and easier to read and understand etc.
I don't really have any input on this, but maybe one way to get started
would be to see if we can build edbrowse against mingw32 or cygwin?
Both provide POSIX C libraries for Windows, I believe.
-- Chris
next prev parent reply other threads:[~2014-05-02 3:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 12:38 Karl Dahlke
2014-04-30 15:54 ` Adam Thompson
2014-05-02 3:05 ` Chris Brannon [this message]
2014-05-02 11:57 ` Adam Thompson
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=87fvksubgr.fsf@mushroom.PK5001Z \
--to=chris@the-brannons.com \
--cc=Edbrowse-dev@lists.the-brannons.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 NNTP newsgroup(s).