'type' is a dos command - I think you're looking for 'cat'
On Tue, Mar 30, 2010 at 3:48 PM, David Frascone <[email protected]> wrote:
> Ok -- let's start slow -- my aliases need to be recreated -- which is fine.
>
>
> I set the alias 'vi' to either be vim, or mvim depending on if I'm on my
> mac, or shelled into a linux box. But, the "type" command does not seem to
> do what I think it should:
>
> codemon...@daves-mbp ~/.c/fish> type vi
> -- type -Q -o tpPafh -- vi
> type: Could not find 'vi'
> codemon...@daves-mbp ~/.c/fish> vi
> codemon...@daves-mbp ~/.c/fish> type fg
> -- type -Q -o tpPafh -- fg
> fg is a builtin
> codemon...@daves-mbp ~/.c/fish> alias
> alias: Expected one or two arguments, got 0
> codemon...@daves-mbp ~/.c/fish> alias vi
> fish: Array index out of bounds
> /usr/local/share/fish/functions/alias.fish (line 19): set body
> $tmp[2]
>
> ^
> in function 'alias',
> called on standard input,
> with parameter list 'vi'
>
>
> Ideas? The vi command does work, so I don't know why type does not return
> it. Or what the garbage is in the line before type's output.
>
>
> On Tue, Mar 30, 2010 at 3:35 PM, David Frascone <[email protected]> wrote:
>
>> Ok . . .it's been a few months . . let me switch back, so I can provide
>> details if I run into problems. I did love fish when I used it, but I ran
>> into <something that I don't remember>, so I bailed back to zsh.
>>
>>
>> -Dave
>>
>>
>> On Tue, Mar 30, 2010 at 3:26 PM, Isaac Dupree <
>> [email protected]> wrote:
>>
>>> On 03/30/10 15:14, David Frascone wrote:
>>>
>>>> I had to quit using fish, due to constant script incompatibilities. I
>>>> guess
>>>> some script authors are too lazy to add hash-bang-bash to the top of
>>>> their
>>>> scripts . . .
>>>>
>>>
>>> what? -- script files don't run unless you start the file with
>>> #!/bin/bash (or similar), or unless you invoke them as 'bash
>>> the_script_file'
>>>
>>>
>>> Has anyone had any success making fish their real new home? Oh -- and I
>>>> also had some issues with the select bug that was posted here a while
>>>> ago,
>>>> but is still not patched :(
>>>>
>>>
>>> yes, fish has been my shell for a couple of years. The hilighting and
>>> history features are nice. So is the fact that I've got it storing my
>>> command history forever, rather than just, say, 500 previous commands (can
>>> you configure Bash to store history forever too?). But there are frequent
>>> bugs in various things like redirection, history up-and-down, maybe loops or
>>> syntax, etc... Whenever I want to do something semi-complicated, or if
>>> something didn't work as I expected in Fish, I switch to bash to make it
>>> work--Which I know well, because I write all my own scripts in bash. Also
>>> necessary for copy/pasting from the Internet.
>>>
>>> -Isaac
>>>
>>
>>
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Fish-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/fish-users
>
>
--
Steven Scott
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Fish-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fish-users
