Greetings, Dave Kilroy!
-1 mode fails because fish would prefer cygpath was run on the argument
first. I'm not sure why this works in bash.
Because bash know what is going on. In fact, many cygwin tools recognize
native paths.
I'll try put together a fix for the latter issue, but it may be a
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
Alternatively drop it in the fish
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
Alternatively drop it in the fish
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 Tue, Apr 8, 2014, at 0: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
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:
On Wed, 15 Jun 2005, Dave wrote:
So it can be done using shell extensions. These require a bit of COM
programming, producing a .dll that needs to be registered.
I didn't experiment with it at all, maybe it's possible to do another way
:)
4. Is the extra context menu item worth the
Jan Schormann wrote:
in my context menu on folders, I have WinZip, WinRar, WinCvs,
TortoiseSVN, WinAmp, Perforce, and WinMerge ...
This is what WinAmp does and it looks rather simple:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Directory\shell\Winamp.Enqueue]
@=Enqueue in
Brian Dessen wrote:
Jan Schormann wrote:
in my context menu on folders, I have WinZip, WinRar, WinCvs,
TortoiseSVN, WinAmp, Perforce, and WinMerge ...
This is what WinAmp does and it looks rather simple:
snip example
I haven't been following this thread very closely (and I don't know what
Hi Dave,
On Tue, 14 Jun 2005, Dave wrote:
If I understand what you mean, then I don't think it's possible. However, if you
can find either:
Well I am not an expert on this, obviously :) But:
a) the appropriate registry key to modify
b) an example of a program that adds something to this
Hi Dave,
a) the appropriate registry key to modify,
b) an example of a program that adds something to this context menu
(the one with 'Customize this folder' on it), and a user to dig
around their registry to find out how it does it,
in my context menu on folders, I have WinZip, WinRar,
--- Nils Jeppe wrote:
On Tue, 14 Jun 2005, Dave wrote:
If I understand what you mean, then I don't think it's possible. However, if
you
can find either:
a) the appropriate registry key to modify
snip
the way to do this is via
At 02:41 PM 6/15/2005, you wrote:
--- Nils Jeppe wrote:
On Tue, 14 Jun 2005, Dave wrote:
If I understand what you mean, then I don't think it's possible. However,
if
you
can find either:
a) the appropriate registry key to modify
snip
the way to do this is via
On Mon, 13 Jun 2005, Dave wrote:
chere adds a bash here context menu just fine. However:
Thanks for the report. Now how did that go unnoticed? More explicit instructions
No problem :) Also, as a feature request, and since you're touching it
anyway: Can you also add it to a folder's
Hi Dave,
From: Dave d_inabox !at! yahoo.com
Date: Mon, 13 Jun 2005 15:09:27 -0700 (PDT)
::chere adds a bash here context menu just fine. However:
::
::1) You have to click on a folder icon, clicking in a folder
:: that's open does not work
::2) It opens the shell not in the folder you clicked
--- Nils Jeppe wrote:
Can you also add it to a folder's context menu? Say, I have a
folder open, and I click on the folder window itself, instead of a folder
icon for a sub-folder. That'd be sweet.
If I understand what you mean, then I don't think it's possible. However, if you
can find
chere adds a bash here context menu just fine. However:
1) You have to click on a folder icon, clicking in a folder
that's open does not work
2) It opens the shell not in the folder you clicked on, but
in the parent folder
Thanks for the report. Now how did that go unnoticed? More explicit
Hi guys,
chere adds a bash here context menu just fine. However:
1) You have to click on a folder icon, clicking in a folder that's open
does not work
2) It opens the shell not in the folder you clicked on, but in the parent
folder
I do not subscribe to the mailing list (too high volume),
At 05:47 AM 6/10/2005, you wrote:
Hi guys,
chere adds a bash here context menu just fine. However:
1) You have to click on a folder icon, clicking in a folder that's open does
not work
I'm not sure what you mean by this. bash here is added to *folder*
context menus. You have to do a
20 matches
Mail list logo
