> I'm running fish[1] as my shell under iTerm[2]. fish will start
> up and run for a while and then it will crash and kill iTerm. I
> will be running any number of programs: vim, sqlplus, gqlplus,
> less, etc. I don't believe the problem is iTerm. Using zsh as my
> shell does not cause
On Mar 5, 2007, at 11:09 AM, Martin Baehr wrote:
> On Mon, Mar 05, 2007 at 11:59:08AM -0600, Myrddin Emrys wrote:
>> linux> rm ab*
>> Ab* Absolute.txt, Abstract.txt, Abrasive.txt...
>> linux> rm Ab*
>
> this is exactly what i am afraid of, because if i do not notice
> that the
> case chsnged
I'm sure I'm missing something here, but I have no clue what it is. It may be your LOCALE or LANG; if you’re lucky, the word-breaking is locale-dependent.-Ben-
Using Tomcat but need to do more? Need to support web services, sec
?: Matches any character except '/' *: Matches any substring not including the character '/' **: Matches any substring To me, this seems much more intuitive. Unless someone has a very strong reason for sticking with the current behaviour, it will change. This sounds great. Anything done to reduce
Ah, I understand. Unfortunatly, it seems that allowing the terminal to wrap itself makes cursor movement unpredictable. Sometimes moving up/down the wrapped line is seen as one line, sometimes as two. That would definitely be a bug in your terminal emulator or your cursor handling code. While many
> If the fish configuration files are moved to ~/.config/fish, it seems
> a bit silly for the configuration file to be named
>
> ~/.config/fish/fish
How about ~/.config/fish/food or ~/.config/fish/tank?
I’m sure a more clever individual could find an acronym expansion for
food or tank.
-Ben
>> An alternative approach that actually almost always works is to parse
>> the manpage, at least as a fallback. I was looking at command
>> completion a while back and this approach worked with nearly every
>> manpage I threw at it.
>
> If you still have the code and have the option of releasing i
>> Problems with this approach:
>> Get this accepted in all getopt implementations.
>
> seems a lot easier than getting all apps patched.
An alternative approach that actually almost always works is to parse
the manpage, at least as a fallback. I was looking at command
completion a while back
