On 29 November 2010 19:11, Roe, Kevin L. wrote:
> I have set up a registry entry:
>
> [HKEY_CLASSES_ROOT\Directory\shell\bashrxvt]
> @="&Open BASH Shell Here"
> [HKEY_CLASSES_ROOT\Directory\shell\bashrxvt\command]
> @="C:\\cygwin\\bin\\mintty.exe -"
> [HKEY_CLASSES_ROOT\Drive\shell\bashrxvt]
> @="&
> What Csaba said. Also, MSYS's bin directory does appear in there
> (/cygdrive/c/msys/1.0/bin), but Cygwin's is before it, so that's fine.
> Hence, as mentioned before, you need to check whether you do actually
> have Cygwin's vi and make installed, e.g. using the 'which' command.
>
> For further
Well, you may have noticed that my registry entries look remarkably like what
chere produces. I used "chere -i -p -c -t minty" to find my working solution
(with the hoops). I built my "BASH shell here" context menu before "chere"
existed. I based it on the "cmd shell here" powertoy. It start
"Roe, Kevin L." wrote:
>I know Windows explorer is supposed to pass the location to minty, so
why do I need to jump through these hoops?
I'm curious. Why are you editing the registry by hand instead of using
"chere"?
http://code.google.com/p/mintty/wiki/Tips#Creating_a_folder_context_menu
_entry
I have determined that modifying the registry entry to:
[HKEY_CLASSES_ROOT\Directory\shell\bashrxvt]
@="&Open BASH Shell Here"
[HKEY_CLASSES_ROOT\Directory\shell\bashrxvt\command]
@="C:\\cygwin\\bin\\mintty.exe -e /bin/xhere /bin/bash.exe \"%L\""
[HKEY_CLASSES_ROOT\Drive\shell\bashrxvt]
@="&Open B
On Mon, Nov 29, 2010 at 01:23:01PM -0800, Daniel Colascione wrote:
>On 11/29/2010 10:39 AM, Ken Brown wrote:
>>On 11/29/2010 8:22 AM, Daniel Colascione wrote:
>>>Starting a login shell on my system takes a painfully long time, mostly
>>>because fork() is pretty slow on WOW6432 systems. I've taken
On 11/29/2010 10:39 AM, Ken Brown wrote:
> On 11/29/2010 8:22 AM, Daniel Colascione wrote:
>> Starting a login shell on my system takes a painfully long time, mostly
>> because fork() is pretty slow on WOW6432 systems. I've taken a look at
>> the shell initialization routines and identified some po
On 11/29/2010 9:29 AM, David Sastre wrote:
> I'm already working in some changes in base-files to include some
> bugfixes, and hopefully improve start-up performance by reorganizing how
> things are done now. I'll check your proposals.
Good.
> One thing: we need to set at least a minimum PS1 in
On Nov 29 05:58, tsteven4 wrote:
> I can readily reproduce a tcsh error "Out of memory", however the
> timing is variable. In my actual application the time to failure
> varies from seconds to hours. I have a test case that seems to be
> able to reproduce the error.
>
> The symptom of the error
Am 26.11.2010 09:32, schrieb Corinna Vinschen:
There's an older Cygwin DLL in the path somewhere. You should try to
find and remove it.
True. I've found it in c:\cygwin\bin\cygwin1.dll and in parallel
c:\cygwin\bin\cygwin1.dll.new - I renamed the current one to *.old and
the .new to cygwin1.dl
On 11/29/2010 8:22 AM, Daniel Colascione wrote:
Starting a login shell on my system takes a painfully long time, mostly
because fork() is pretty slow on WOW6432 systems. I've taken a look at
the shell initialization routines and identified some potential savings:
- Can't we use USERNAME to set U
On Mon, Nov 29, 2010 at 05:22:56AM -0800, Daniel Colascione wrote:
> Starting a login shell on my system takes a painfully long time, mostly
> because fork() is pretty slow on WOW6432 systems. I've taken a look at
> the shell initialization routines and identified some potential savings:
>
> - Can
On Mon, Nov 29, 2010 at 09:51:19AM +, Andy Koppe wrote:
>What Csaba said. Also, MSYS's bin directory does appear in there
>(/cygdrive/c/msys/1.0/bin), but Cygwin's is before it, so that's fine.
>Hence, as mentioned before, you need to check whether you do actually
>have Cygwin's vi and make ins
When I use scp -r for recursive copy from Win7 to a remote XP machine,
the properties for the new directory show the message "The permissions
on ... are incorrectly ordered ..." This is for a simple test case.
For an attempted network backup, the process hung up, and I could get
access to the
Starting a login shell on my system takes a painfully long time, mostly
because fork() is pretty slow on WOW6432 systems. I've taken a look at
the shell initialization routines and identified some potential savings:
- Can't we use USERNAME to set USER instead of running `id -un`?
- Move the /tmp
I can readily reproduce a tcsh error "Out of memory", however the timing
is variable. In my actual application the time to failure varies from
seconds to hours. I have a test case that seems to be able to reproduce
the error.
The symptom of the error is a message like:
188
./test2
189
./test
Hi,
Could someone explain why the time differs when i log in using ssh versus
typing date in a mintty window.
Output from a mintty window:
$ date; ssh localhost date; date
Mon Nov 29 11:02:30 CUT 2010
gi...@localhost's password:
Mon Nov 29 11:02:56 CUT 2010
Mon Nov 29 11:02:34 CUT 2010
I
I was wondering how a fix for the below can be obtained as soon as
it's available? The current implementation of find's -execdir has all
our scripts that use cygwin halted.
Thanks,
Peter
-
www.pdanford.com
On Nov 22 13:13, Dirk Fassbender wrote:
> The behaviour of find -execdir is documented in t
On 29 November 2010 08:20, Nathan Rose wrote:
>> You're probably invoking MSYS's versions of vi and make. You can check
>> that with the which command. Ensure that you do have the Cygwin
>> versions of those installed, and that the Cygwin bin directory comes
>> before MSYS's in the Cygwin PATH. To
Hi Nathan,
On Mon, Nov 29, 2010 at 9:20 AM, Nathan Rose wrote:
>
> Thanks for your help. I have fixed the Windows path but Cygwin seems to
> be altering it when loading it in to its own $PATH environment variable.
> Compare below, my path as obtained from Windows cmd console and from
> Cygwin. Not
> Greetings, Vincent Richomme!
>
run setup and choose the directory you want
>>>
the default proposal is c:\cygwin
>>>
>>> To add:
>>> Strongly advised against paths with spaces or national letters.
>>>
>
>> Again I was not very clear I don't want to know how to install cygwin
>> becaus
> You're probably invoking MSYS's versions of vi and make. You can check
> that with the which command. Ensure that you do have the Cygwin
> versions of those installed, and that the Cygwin bin directory comes
> before MSYS's in the Cygwin PATH. To avoid such confusion, you might
> want to remove M
22 matches
Mail list logo
