public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: can't open cygwin from shortcut
Date: Sun, 24 Apr 2016 08:30:00 -0000	[thread overview]
Message-ID: <loom.20160424T073320-782@post.gmane.org> (raw)
In-Reply-To: <201604231526.u3NFQkLB011430@coolidge.cs.Dartmouth.EDU>

Doug McIlroy writes:
> On a Microsoft Surface running CYGWIN_NT-10.0 version 2.4.1(0.293/5/3)
> I cannot start Cygwin from the desktop shortcut. It fails to find
> mintty. On failure, it proffers a browsing window focused on /bin.
> Clicking on mintty in that window does not work. I can start
> Cygwin via a Windows "run" request, however.
> 
> On a Dell desktop machine running CYGWIN_NT-6.3 version 1.7.34(0.285/5/3)
> where the shortcut works, I see that the pathname in the shortcut
> ends in mintty.exe. The .exe extension is missing in the 2.4.1
> shortcut. Could this be the cause? If so, is there a convenient
> way to edit a shortcut?

Not familiar with the Win 10 tablet interface, but if you select the icon on
the desktop or Start Menu, mouse right-click (or keyboard right hamburger
key) and the context menu shows a Properties item at the bottom: select that
to edit properties, (if necessary select Shortcut tab) and the Target
textbox should show something like "C:\Cygwin64\bin\mintty.exe -i
/Cygwin-Terminal.ico -", where C:\Cygwin64\ should be wherever you told
setup to make your Cygwin install root. Fix as appropriate. 

You can also Run that command directly. 

If that doesn't work, try a Search for "%APPDATA%\Microsoft\Internet
Explorer\Quick Launch" and select Quick Launch when displayed;
Run: explorer "%APPDATA%\Microsoft\Internet Explorer\Quick Launch";
or if you can open a Command Prompt (cmd.exe) window, type:
start explorer "%APPDATA%\Microsoft\Internet Explorer\Quick Launch"; 
either of which should open a Windows Explorer window, and you can browse
down for Cygwin mintty shortcut, and edit using the context menu Properties
selection described above. 
You can also launch mintty directly by browsing to C:\Cygwin64\bin\mintty,
or C:\Cygwin64\bin\bash, which will then appear in a Command Prompt console
window. You can then type "cygstart mintty" to launch it properly. 

Sorry am unable to be more specific, but few of us shell aficionados are
likely to have (or want!) access to a Windows tablet, and a lot about the
environment comes under the heading "sh*t we shouldn't have to know!" ;^> 

N.B. Cygwin comes with a couple of utilities installed: readshortcut(1) and
mkshortcut(1) which allow you to work with shortcuts from the command line,
using either Cygwin or Windows paths. 
A useful Cygwin package to install is chere, which adds a mintty/bash
context menu item to Windows explorer, allowing you to launch a mintty
console bash shell with the selected folder as your current working directory. 



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2016-04-24  6:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-23 17:17 Doug McIlroy
2016-04-24  5:48 ` John Ruckstuhl
2016-04-24  6:32 ` Achim Gratz
2016-04-24  8:30 ` Brian Inglis [this message]
2016-04-25 17:46 Doug McIlroy

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=loom.20160424T073320-782@post.gmane.org \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).