"... the need to use local::lib.

I don't have local::lib installed under Cygwin -- I don't have any need for it. I checked this with a utility, perlmodver, that I wrote to provide info on installed modules -- here's an example: 

ken@titan ~/tmp
$ perlmodver local::lib Data::Dumper Data::Dump
NOT FOUND: local::lib
----------------------------------------------------------------------
+--
Data::Dumper 2.189
  in /home/ken/perl5/perlbrew/perls/perl-5.40.0/lib/5.40.0/cygwin-thre
+ad-multi/Data/Dumper.pm
----------------------------------------------------------------------
+--
Data::Dump 1.25
  in /home/ken/perl5/perlbrew/perls/perl-5.40.0/lib/site_perl/5.40.0/D
+ata/Dump.pm
----------------------------------------------------------------------
+--

[download]

The code, if you're interested, is in the spoiler. I have copies of this on many platforms and use it frequently.

<Reveal this spoiler or all in this thread>

I do require local::lib for other platforms that I use for $work; for example, see perl-local-lib, in the list of packages I need to get cpan to work properly, in the fairly recently posted Re: cpan: Terminal does not support AddHistory. [openSUSE].

"... I don't like having two home directories ..."

Same here; except I have more than two:

I don't use Win10 directly that much; however, when I'm downloading something it typically starts by suggesting a location like ken/some/path/ (i.e. chopping off the important part at the start of the pathname). This use to annoy me intensely -- after many years of usage I've become use to this and have stopped letting it bug me.

My more normal usage is to start a shell. There's no real problem here as it puts me in my Cygwin home directory: 

ken@titan ~
$ pwd
/home/ken

[download]

— Ken

In reply to Re^3: diagnostics pragma throwing a compile-time error in Cygwin-Perl by kcott
in thread diagnostics pragma throwing a compile-time error in Cygwin-Perl by Intrepid

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.