****** I ask you once again, use the Reply all feature of your mail client. I'd like the discussion to stay public. ******
On 24. 4. 2015 15:06, Rainer Schuetz wrote:> >> On 24 Apr 2015, at 13:39, David Macek <[email protected]> wrote: >> >> As long as you set MSYSTEM and call `bash --login -i`, you should be fine >> without having to fiddle with paths manually. > > Ah, great! Didn’t know/understand that, must have missed that bit in the > documentation. Thank’s a loTT (could have saved some fiddleing had I > understood that before ;)) > >>> but I am not sure how activate the “msys-specific” functionality like path >>> mapping (c:\msys->/ etc). I don’t quite get at which stage that happens >>> when I read the open shell script batch file... >> >> I'm not sure what's the problem here. The virtualized filesytem is compiled >> into the runtime and there's no switch for enabling or disabling it AFAIK. >> Every(*) program in /usr/bin should understand what `/` means. >> >> *) Not actually every one; there's a few exceptions. > > The problem is the basic understanding of how the system works. So thanks a > lot again, you’ve opened my eyes ;) > > Best > .r. On 24. 4. 2015 15:44, Rainer Schuetz wrote: > >> On 24 Apr 2015, at 13:39, David Macek <[email protected]> wrote: >> >> As long as you set MSYSTEM and call `bash --login -i`, you should be fine >> without having to fiddle with paths manually. > > This is really sexy. From ssh I can call bash and I stay in my home-folder. > `env` reports my Windows-home folder as home. So I guess I could use my > normal Windows home folder with msys2 too? Sure, I do that. > Is that supported/taken into account, Just keep in mind that if your HOME is the same as your user profile directory, and you use some non-MSYS2 open-source software builds, they may share configuration files. That could cause some conflicts. > or do I get problems if I make this my standard working-dir with msys2 Now I'm not sure if you're not mixing "home directory" with "working directory". Anyway, I don't work in my profile directory, I use it strictly for storing configuration and application data (and whatever Windows puts there). I have a separate directory as my workplace. But that's a matter of personal preference; there should be no problem with using your Windows home directory as your workplace. > and just setting a value to MSYSTEM and calling bash my defalut way of > entering msys2 (I could use the same ssh keys, git-configuration etc without > much attention)? If you look at the .bat files, there's not much else than that, so yeah. > I miss out on mintty when coming from ssh, but I think the advantages of this > alternative outweigh the loss by far, I would also use it locally, I think. You can use PuTTY to connect to your remote MSYS2. It's very similar to mintty. I'm not sure if I get your point, so just to be clear: You don't need SSH to have your HOME pointing at your Windows profile directory. > One more question, if you allow: I see some lines enabling Windows links for > msys2 - can I enable that without risk - I wonder why it’s commented out? NTFS symlinks don't behave exactly like POSIX symlinks, that's why they're not enabled by default. Reading: https://cygwin.com/cygwin-ug-net/using.html#pathnames-symlinks https://en.wikipedia.org/wiki/Symbolic_link#Windows_symbolic_link https://en.wikipedia.org/wiki/NTFS_symbolic_link > Thanks so much again! > .r. -- David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
