On Jan 23, 2008 7:04 AM, Nick Pilon [EMAIL PROTECTED] wrote:
On Jan 22, 2008 8:41 PM, Philip Ganchev [EMAIL PROTECTED] wrote:
Would it help to read command names from the path for binaries first?
There may still be man pages for commands that are not installed in
the system when the
On Jan 23, 2008 5:35 AM, Nick Pilon [EMAIL PROTECTED] wrote:
On Jan 22, 2008 7:53 PM, Axel Liljencrantz [EMAIL PROTECTED] wrote:
On Jan 21, 2008 7:34 PM, Axel Liljencrantz [EMAIL PROTECTED] wrote:
One simple solution is to disable with the X clipboard by sending
--without-xsel to
On Jan 23, 2008 9:40 AM, Axel Liljencrantz [EMAIL PROTECTED] wrote:
Unfortunatly, that depends heavily on the apropos implementation. Some
apropos implementations are simply a wrapper shellscript around grep
while others are perform a search on multiple binary database files. I
added that
On Jan 23, 2008 12:53 AM, Axel Liljencrantz [EMAIL PROTECTED] wrote:
On Jan 22, 2008 7:16 PM, Nick Pilon [EMAIL PROTECTED] wrote:
[...]
Except prompt_pwd was broken in darcs and was printing every path
element twice. IE, /usr/usr. So I've fixed that instead and sent the
patch to the list.
On Jan 22, 2008 1:16 PM, Nick Pilon [EMAIL PROTECTED] wrote:
[...]
1) Man pages for commands that are in subsections. This is easy enough
to fix. For example:
lastwords(1m)- print syscalls before exit. Uses DTrace
[...]
2) Man pages with alternative names with just plain weird
On Jan 22, 2008 7:53 PM, Axel Liljencrantz [EMAIL PROTECTED] wrote:
On Jan 21, 2008 7:34 PM, Axel Liljencrantz [EMAIL PROTECTED] wrote:
One simple solution is to disable with the X clipboard by sending
--without-xsel to configure. This means fish won't share the clipboard
with X,
On Jan 22, 2008 8:41 PM, Philip Ganchev [EMAIL PROTECTED] wrote:
Would it help to read command names from the path for binaries first?
There may still be man pages for commands that are not installed in
the system when the completion files are generated. Maybe then when
the user tries to
So, it looks like Fish 1.23.0 has some weird problems on Mac OS X
10.5. This is expected, I'm going to see what I can do to smooth them
out.
1) Since OS X sets $DISPLAY by default, even if X11 isn't open,
anything that puts anything on the killring causes X11 to be launched.
It's not a problem,
1) Since OS X sets $DISPLAY by default, even if X11 isn't open,
anything that puts anything on the killring causes X11 to be launched.
It's not a problem, it's more annoying than anything else. I've solved
this by clearing $DISPLAY on login, and I'm pretty sure that this is
all that can be
On Mon, Jan 21, 2008 at 05:54:05PM -0400, Nick Pilon wrote:
I've solved
this by clearing $DISPLAY on login, and I'm pretty sure that this is
all that can be done, since it's indistinguishable from a terminal
with an actual X server running.
well, you could run a program that detect whether
On Jan 21, 2008 10:54 PM, Nick Pilon [EMAIL PROTECTED] wrote:
So, it looks like Fish 1.23.0 has some weird problems on Mac OS X
10.5. This is expected, I'm going to see what I can do to smooth them
out.
1) Since OS X sets $DISPLAY by default, even if X11 isn't open,
anything that puts
11 matches
Mail list logo
