From: "Kevin Carhart" <kevin_carhart@fastmail.fm>
To: "Karl Dahlke" <eklhad@comcast.net>, edbrowse-dev@edbrowse.org
Subject: Re: [edbrowse-dev] quick js
Date: Tue, 09 Mar 2021 02:23:53 -0800 [thread overview]
Message-ID: <247e8e81-8a65-4172-82a1-fc298d39a467@www.fastmail.com> (raw)
In-Reply-To: <20210208034648.eklhad@comcast.net>
In 2019 through last year, I was stuck at a work PC and wanted to do little or no ssh'ing from the office. Yet I had itchy fingers for an edbrowse. I think I even got the mingw compiler together but then discovered WSL. So, I'm not advocating for WSL particularly, but I found it intriguing that there was another option. The workload to get it wasn't terrible. It's true that WSL sets up its own filesystem and this could put people off the idea. I believe the top level in linux world would be under several folders in windows like files\blah\blah\linuxroot\home\kevin. You technically could get things back and forth if you were willing to read the boards to figure it out. Non admins, people with no root or sudo, stuck at work, are a niche who might be interested in edbrowse for Windows.
next prev parent reply other threads:[~2021-03-09 10:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 13:26 Karl Dahlke
2021-03-07 16:15 ` Chris Brannon
2021-03-07 16:44 ` Karl Dahlke
2021-03-07 17:15 ` Chris Brannon
2021-03-07 18:40 ` Geoff McLane
2021-03-07 19:27 ` Karl Dahlke
2021-03-07 19:37 ` Chris Brannon
2021-03-08 8:46 ` Karl Dahlke
2021-03-08 19:31 ` Geoff McLane
2021-03-08 21:18 ` Karl Dahlke
2021-03-09 10:23 ` Kevin Carhart [this message]
2021-03-09 14:37 ` Geoff McLane
2021-03-09 22:52 ` Kevin Carhart
[not found] ` <20210210053836.eklhad@comcast.net>
2021-03-14 20:36 ` Geoff McLane
2021-03-15 9:44 ` Kevin Carhart
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=247e8e81-8a65-4172-82a1-fc298d39a467@www.fastmail.com \
--to=kevin_carhart@fastmail.fm \
--cc=edbrowse-dev@edbrowse.org \
--cc=eklhad@comcast.net \
/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).