edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@edbrowse.org
Subject: [edbrowse-dev] quick js
Date: Mon, 08 Mar 2021 03:46:48 -0500	[thread overview]
Message-ID: <20210208034648.eklhad@comcast.net> (raw)
In-Reply-To: <875z22iwlm.fsf@the-brannons.com>

[-- Attachment #1: Type: text/plain, Size: 660 bytes --]

I've never even touched windows, well almost never, so forgive me if I'm being silly.
Let's say there was, someday, a windows edbrowse user.
He surely would want to use edbrowse in his home directory, accessing his own files in documents, downloads, desktop, etc.
There's not much point in him bringing up a virtual os, which he then has to live in entirely, and running edbrowse, just to say he ran it.
Or is WSL some kind of emulator that can wrap around and run a single linux program still in the context of your windows world?

Just curious.

And no - we shouldn't do too much until we see a windows user somewhere on the horizon.

Karl Dahlke

  reply	other threads:[~2021-03-08  8:47 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 [this message]
2021-03-08 19:31               ` Geoff McLane
2021-03-08 21:18                 ` Karl Dahlke
2021-03-09 10:23               ` Kevin Carhart
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:

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

  git send-email \
    --in-reply-to=20210208034648.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=edbrowse-dev@edbrowse.org \
    --subject='Re: [edbrowse-dev] quick js' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).