From: Oleksandr Gavenko <gavenkoa@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Noticed that mintty starts non-login bash with "Win+R mintty Enter".
Date: Sun, 17 Jan 2021 01:09:14 +0200 [thread overview]
Message-ID: <vriuwnwclbs5.fsf@gavenkoa.example.com> (raw)
In-Reply-To: <09bf01d6e36e$f2694020$d73bc060$@pdinc.us>
On 2021-01-05, Jason Pyeron wrote:
> I do not put Cygwin in my windows PATH, (anymore since about 10 years ago).
Sometimes it is useful to have GNU utils at hands. I use Far Commander and in
order to find directory size I type:
du -s -m NAME
Also having Cygwin staff in PATH allows to start program elevated easily
(<Win> NAME <Ctrl><Shift><Enter>).
> I use an environment where settings are lost at logoff, so I have become
> accustomed to launching it from the command prompt.
>
> I have not found it too difficult to type
>
> c:\cygwin64\bin\mintty /bin/bash -l
It won't be productive for my workflow. I own dev PC, not restricted to
corporate policies and launch mintty hundred times a day (have CDPATH and
other convenience set as the environment is permanent).
Though I might get rid of Cygwin from PATH too.
For starting Emacs I wrote wrapper that run it elevated (and hides that
irritating console as I use emacs-w32) - it is a pleasure to be able to edit
Windows /etc/hosts from within Emacs ))
Same wrapper can be written for Mintty and placed to PATH.
Though I wouldn't do that because all IDEs are rely on git.exe from Cygwin...
It is pity that Mercurial comes with "shell" launcher, so cannot be used by
non-Cygwin programs.
--
http://defun.work/
next prev parent reply other threads:[~2021-01-16 23:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 22:33 Oleksandr Gavenko
2021-01-05 10:31 ` Thomas Wolff
2021-01-05 14:27 ` [cygwin] " Jason Pyeron
2021-01-16 23:09 ` Oleksandr Gavenko [this message]
2021-01-07 7:34 ` Andrey Repin
2021-01-07 12:42 ` Kamran
2021-01-16 22:57 ` Oleksandr Gavenko
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=vriuwnwclbs5.fsf@gavenkoa.example.com \
--to=gavenkoa@gmail.com \
--cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).