Re: using chere

On 2007-06-21, Dave wrote: > Paul Mallas wrote: > > Since we are on the topic - is there a way to do something similar > > inside an open windows folder rather than from the folder icon? I would > > find that much more convenient. > > This came up two years ago. Follow the thread from about here:

Re: using chere

Paul Mallas wrote: > Since we are on the topic - is there a way to do something similar > inside an open windows folder rather than from the folder icon? I would > find that much more convenient. This came up two years ago. Follow the thread from about here:

Re: using chere

I had a similar problem with chere and xterm. Chere edits your Windows registry file. It added this to my registry: C:\cygwin\bin\run.exe C:\cygwin\bin\xterm.exe -e /bin/xhere /bin/bash.exe "%L" This sits in the registry at HKEY_CLASSES_ROOT/Directory/shell/cygwin_bash/command I added -dis

Re: using chere

--- Lewis Hyatt <[EMAIL PROTECTED]> ha scritto: > Lewis Hyatt wrote: > > > OK, one last thing, sorry. I did something wrong > with the last test. If > > I add c:\cygwin\bin and c:\cygwin\usr\X11R6\bin to > the Windows PATH > > variable, then chere does work to open up an > xterm! > > > > So I

Re: using chere

Lewis Hyatt wrote: > Lewis Hyatt wrote: > >> OK, one last thing, sorry. I did something wrong with the last test. >> If I add c:\cygwin\bin and c:\cygwin\usr\X11R6\bin to the Windows PATH >> variable, then chere does work to open up an xterm! >> >> So I guess the only question is: is there any way

Re: using chere

Lewis Hyatt wrote: OK, one last thing, sorry. I did something wrong with the last test. If I add c:\cygwin\bin and c:\cygwin\usr\X11R6\bin to the Windows PATH variable, then chere does work to open up an xterm! So I guess the only question is: is there any way to avoid this requirement? It w

Re: using chere

The difference is that --login -i directs bash eventually to read /etc/profile, which adds cygwin dirs to the path. So as Morgan thought, this is somehow a PATH issue. However, I added c:\cygwin\bin, c:\cygwin\user\X11R6\bin to my Windows path, and the chere still does not pop up an xterm. (N

Re: using chere

Dave wrote: At a guess, do you need to make sure the DISPLAY environment variable is set for the xterm to find the server? You have it set in your cygcheck output, but you clearly produced that within an xterm which will have the variable set. If that's the case DISPLAY will need to be set in t

Re: using chere

Lewis Hyatt wrote: >> What happens if you run the following command from a cmd prompt: >> >> xterm -e /bin/bash -l > > The latter command works fine if I type it from an xterm, but it doesn't > work if I type it from a bash CMD window. (Nothing happens). I am always > running the X server. Thanks

Re: using chere

It is supposed to work. That said I don't use X myself, so haven't explicitly tested this. Using xterm does require that the x server is already running before xterm is invoked. What happens if you run the following command from a cmd prompt: xterm -e /bin/bash -l The latter command works f

Re: using chere

Lewis Hyatt wrote: > Is this supposed to work? I tried this: > > chere -iam1 -s bash -t xterm > > and this: > > chere -iam2 -s bash -t xterm > > In both cases, the shell extension is installed as expected, but when I > click on "Bash prompt here", nothing happens. It is supposed to work. That

Re: using chere

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lewis Hyatt wrote: > Hi Everyone- > > If I run chere like this: > > chere -iam1 -s bash -t cmd > > or like this: > > chere -iam2 -s bash -t cmd > > Then it behaves as expected. What I was hoping was to get the same > functionality, but have it pop