On 23/10/2015 16:16, Matt Seitz (matseitz) wrote:
> When I right click a folder in Windows Explorer and select
> "Bash Prompt Here", a window opens briefly and then closes
> immediately. If I select "Applications -> Xterm" from the
> Cygwin/X Server tray icon, XTerm opens fine.
>
> Cygcheck and X
On 10/10/2014 14:46, Andrew Schulman wrote:
OK, I rolled a new release of fish 2.1.1:
x86:
http://home.comcast.net/~andrex2/cygwin/x86/fish-2.1.1-1.tar.xz
http://home.comcast.net/~andrex2/cygwin/x86/fish-2.1.1-1-src.tar.xz
x86_64:
http://home.comcast.net/~andrex2/cygwin/x86_64/fish-2.1.1-1.tar
On 09/10/2014 18:26, Andrey Repin wrote:
Greetings, Andrew Schulman!
Bad news: the PATH problem is back. When I run
C:\cygwin64\bin\fish.exe -l
I get the same error messages as before on startup, and PATH doesn't
include /bin /usr/bin /sbin /usr/sbin.
How are /bin /usr/bin etc. normally added
On 08/10/2014 18:36, Alive4Ever wrote:
On Wednesday, October 08, 2014 11:08:43 AM you wrote:
Does that work. It seemed to have the same issue as noted in the
following thread https://cygwin.com/ml/cygwin/2014-04/msg00111.html
Dave.
It should work, although I don't recommend running cygwin apps
On 08/10/2014 10:57, Andrew Schulman wrote:
On Wednesday, October 08, 2014 05:13:54 AM Andrew Schulman wrote:
When I try to start fish directly from the Windows shell instead of from
bash, I get a boatload of errors, like this:
I suggest you to read fish manual page, and find how to invoke fish
On 24/08/2014 11:02, Michelle Pace wrote:
HOORAY! Thanks Andrey, this command worked for me:
$ chere -i -t mintty -s bash
I'm glad you got it to work. chere is attempting to use the shell
defined in your passwd (as retrieved by getent). The shell being
returned is '/bin/sh'.
It looks like
On 10/04/2014 11:06, Ronald Fischer wrote:
I've had more time to look around. If you add the following to the file
~/.config/fish/config.fish (create it if you haven't already got one),
then things should work as intended:
if status --is-login
set PATH /usr/local/bin /usr/bin $PATH
end
On 07/04/2014 23:35, Dave Kilroy wrote:
On 07/04/2014 13:02, Ronald Fischer wrote:
I have installed fish 2.1.0. Works fine, when invoking a new fish shell
manually.
However, when doing a
chere -ifcm -t mintty -s fish
and invoke the new fish shell from the Windows Explorer context menu, I
On 07/04/2014 13:02, Ronald Fischer wrote:
I have installed fish 2.1.0. Works fine, when invoking a new fish shell
manually.
However, when doing a
chere -ifcm -t mintty -s fish
and invoke the new fish shell from the Windows Explorer context menu, I
get plenty of error messages, like this:
Version 1.4-1 of "chere" has been uploaded and should be available from
mirrors shortly.
chere is a script allowing you to add Explorer context menus to start
cygwin in the selected directory.
This script supports x86 and x86_64 simultaneously. If you have 32 and
64 bit cygwin installed on t
On 13/02/2014 21:48, David Stacey wrote:
On 13/02/2014 19:36, m0viefreak wrote:
Grepping through /bin I found at least one other package
that makes use of /etc/passwd as a file directly (cvsbug), but
since I don't have everything installed I can only assume there
are more cygwin-packages and oth
On 12/12/2013 17:01, klonos wrote:
Is there a feature request filed and any link to it so I can follow?
Thanx in advance.
In case you missed it, I've just released an initial version of chere
for x86_64
Dave.
--
Problem reports: http://cygwin.com/problems.html
FAQ:
Version 1.3-1 of "chere" has been uploaded and should be available from
mirrors shortly.
chere is a script allowing you to add Explorer context menus to start
cygwin in the selected directory.
This version of the script supports x86 and x86_64. If you have 32 and
64 bit cygwin installed on t
On 12/12/2013 17:01, klonos wrote:
Is there a feature request filed and any link to it so I can follow?
Thanx in advance.
There's no feature request or link. I suspect the 32 bit package will
work with x64 but haven't had time to check.
Dave.
--
Problem reports: http://cygwin.com/pro
On 03/12/2013 10:21, Corinna Vinschen wrote:
On Dec 2 23:58, Charles Butterfield wrote:
Any suggestions on how to have a shortcut (or something similar) that
runs mintty as admin, but has no global effect on other mintty launches?
You seem to have gotten something else wrong here. If the shor
On 01/12/2013 21:09, Corinna Vinschen wrote:
On Dec 1 15:48, Charles Butterfield wrote:
-Original Message-
From: David Kilroy [mailto:kilr...@googlemail.com]
Can you run the following commands from mintty running bash vs cmd
running bash:
cygpath -u "y:\apps"
test -d /cygdrive/y/apps
e
On 29/11/2013 22:11, Charles Butterfield wrote:
Dave wrote:
Can you clarify which isn't working:
a) a network share mapped to a drive letter, e.g N:\my\network\location
This is my situation. I have my Y: drive mapped to a Linux Samba server. See
more details below
b) network share accessed
On 29/11/2013 17:29, Charles Butterfield wrote:
I've noticed that if I install a right-click shell entry via "chere" and use
"minty" as the terminal that I cannot start a shell on a network share. This is true
regardless of which of the following two installation commands I execute:
chere -I
Originally seen with 1.7.11. I've run rebaseall, and the 20120227
snapshot, and still get this error.
Originally the error was during a git pull. I separated things out and
managed to do the git fetch first, but repeating the pull still
results in a fork failure.
$ uname -a
CYGWIN_NT-6.1-WOW64 ma
Version 1.2-1 of "chere" has been uploaded.
chere is a script allowing you to add context menus to Explorer to start
cygwin in the selected directory.
Changes:
- Support 64 bit Windows registry
- Add support for dash
- Add support for mksh
- Add support for urxvt
*** CYGWIN-
On 23/11/2011 08:12, Ronald Fischer wrote:
It's been a while since I last refreshed the package, so I'll have a
look and see if I can get something done ASAP.
Is there a technical reason, why chere needs to know a predefined set of
"keys" for the shell to install?
If I recall, this was to mak
On 21/11/2011 09:24, Ronald Fischer wrote:
I would like to use "chere" to create a context menu for a terminal
running ksh.
I have installed mksh, since pdksh is marked as obsolete. However, the
chere man-page says that it expects pdksh, if I want a Korn Shell. What
is the best way to proceed?
On 08/09/2011 15:51, Jim Garrison wrote:
I ran chere as follows:
chere -i -t mintty -s bash -a -n -e"bash Shell Here" -o "-s140,50"
However, the Windows Explorer context menu reads:
cygwin_bash
not "bash Shell Here", and when clicking on it I get an error dialog:
[directory in
On Thu, Aug 26, 2010 at 11:45 PM, Reckoner wrote:
> I use chere to right-click and open a shell at a given directory, and
> I was wondering if it is possible to setup a windows batch script that
> would accomplish the same thing from the Windows command line. In
> other words something like,
>
> c
The chere package has been updated to 0.8-1
chere is a tool to manage context menu items for starting shells from
Windows Explorer. See the man page for detailed instructions.
Bug fixes
---
* xterm invoked with /usr/X11R6/bin in the path. This allows it to
find various DLLs it requires.
* DI
On 6/27/06, David Mastronarde wrote:
On Sun, 25 Jun 2006, Dave wrote:
> David Mastronarde wrote:
>> After upgrading sed from 4.1.4 to 4.1.5, I found that line endings were
>> being converted from CRLF to CRCRLF when the input file was specified
>> with a windows file path:
>>
>> % sed -e 's/g5a/s
26 matches
Mail list logo
