On Wed, Dec 2, 2009 at 8:35 AM, Bodaniel Jeanes <[email protected]> wrote: > git reset 'HEAD^' also works or you could do 'git reset HEAD~1' but yes that > bothered me at first too. > For those that don't know ^ is the stderr redirection character. Instead of > having ugly 2>&1/dev/null or whatever it is, you just do ^/dev/null. It's > nice because stdin, stdout, stderr are respectively <, >, ^. Works well IMO
sorry to be pedantic Bo, but ^ is the fishquivalent of 2> (redirect filehandle 2 (stderr)) ^&1 is thus the fishquivalent of 2>&1 (redirect filehandle 2 and make filehandle 1 (stdout) be 2) And Ian, I totally agree ^ blows with HEAD^ (*cough*). It'd be nice to have a way to switch it off, or make it context sensitive (switch off when command is git?) > On Wed, Dec 2, 2009 at 3:42 AM, Ian White <[email protected]> wrote: >> >> I have a minor gripe with fish, that is probably a total n00b one. >> Otherwise I'm enjoying it immensley >> git reset HEAD^ # <= fish thinks the caret is a special token >> git reset HEAD\^ works, but it feels icky. In a few days it might not I >> guess >> Cheers, >> Ian >> >> On 1 Dec 2009, at 02:52, David Lee wrote: >> >> I don't really use fish much, but I find the equivalents of these >> invaluable in zsh: >> >> function gemcd >> cd $argv[1] >> end >> >> function gemedit >> mate $argv[1] >> end >> >> complete -x -c gemcd -a"(__fish_complete_directories ($GEMPATH))" >> complete -x -c gemedit -a"(__fish_complete_directories ($GEMPATH))" >> >> >> >> On Tue, Dec 1, 2009 at 1:38 PM, Josh Price <[email protected]> wrote: >>> >>> Thanks for the responses. >>> >>> They've confirmed my suspicion that fish's 'features' are many, and >>> deeply subtle as opposed to being obvious and easily expressible. >>> >>> I like it enough out of the box to persist with the mild pain of >>> switching. >>> >>> That said, if anyone has any more tips and tricks, I'm keen to hear >>> them! >>> >>> Cheers, >>> Josh >>> >>> >>> On 01/12/2009, at 10:24, Lachie <[email protected]> wrote: >>> >>> > I think that the core of fish is that it has user experience as a >>> > priority. >>> > >>> > "Traditional shells" (sh, bash, ksh) came from being scripting >>> > languages and job control systems with terminal based "UI" evolving >>> > out of electric typewriters rigged to serial lines. >>> > >>> > "Shells" like irb or rush aren't shells in the sense we're talking >>> > about. >>> > >>> > Fish (and zsh i suspect, tho I've not used it) fundamentally accepts >>> > that its primary use will be by apes at terminals. Design decisions >>> > are therefore made with us in mind, rather like a usable web or >>> > desktop app. >>> > >>> > For example the colours used everywhere in fish aren't just for >>> > prettiness; they're a considered, legitimate feature which help you >>> > work more quickly and robustly. >>> > >>> > For more on fish's tenets read >>> > http://fishshell.org/user_doc/design.html >>> > >>> > On Tue, Dec 1, 2009 at 10:07 AM, Bodaniel Jeanes <[email protected]> >>> > wrote: >>> >> To actually be helpful, here are some of the features that make me >>> >> love Fish >>> >> (yes you can get some of these with config in other shells, but >>> >> this is all >>> >> out of the box): >>> >> * Directories are executable (type in it's name, and it will CD to it >>> >> automatically) >>> >> ** Combine this with $CDPATH and I can type in a project name from >>> >> any shell >>> >> to be taken to that directory >>> >> * Global variables (shared across sessions) >>> >> * Tab completion is on speed (look up known_hosts for SSH command, >>> >> for >>> >> instance) >>> >> * Functions can be registered to events (such as when the value of >>> >> a certain >>> >> ENV variable changes, when the prompt is about to be displayed, or >>> >> when a >>> >> command look up failed). >>> >> See >>> >> http://bjeanes.com/2009/10/07/using-fish-shells-event-system-to-behave-like-method-missing >>> >> for an example >>> >> * variables can be arrays (try running: echo $PATH[1] >>> >> * better shell expansion (try ls -1 */**/*.log or something) >>> >> That's all I can think of right now >>> >> >>> >> On Tue, Dec 1, 2009 at 9:00 AM, Lachie <[email protected]> wrote: >>> >>> >>> >>> completions are OFF THE HOOK >>> >>> >>> >>> type ls<TAB> >>> >>> >>> >>> on my machine i get back >>> >>> >>> >>> ls (List directory contents) lsip (sudo lsof | grep -i >>> >>> ipv4 ) lsof (List open files) >>> >>> lsbom (List contents of a bom file) lsm (Latent Semantic Mapping >>> >>> tool) lsvfs (List known virtual file systems) >>> >>> >>> >>> not to say you couldn't do this in bash, but this is out of the box >>> >>> >>> >>> >>> >>> On Tue, Dec 1, 2009 at 9:54 AM, Lachie <[email protected]> wrote: >>> >>>> type (any) part of a command you once used >>> >>>> >>> >>>> hit the up arrow >>> >>>> >>> >>>> >>> >>>> On Tue, Dec 1, 2009 at 9:46 AM, Josh Price <[email protected]> >>> >>>> wrote: >>> >>>>> Fish friends, >>> >>>>> >>> >>>>> Yesterday I tried fish for the second time. This time it's in >>> >>>>> earnest. >>> >>>>> >>> >>>>> Converting from bash required a bit of rejigging my bash profile >>> >>>>> and >>> >>>>> reprogramming my aliases. This was all fine, but other than a >>> >>>>> nicer >>> >>>>> scripting language, autocompletion and a sprinkling of colour, I >>> >>>>> couldn't >>> >>>>> help feeling I was missing something more important, something >>> >>>>> more subtle >>> >>>>> and powerful than just the surface stuff. >>> >>>>> >>> >>>>> I've installed the fish nuggets as per Dave Bolton's suggestion >>> >>>>> from >>> >>>>> the previous fish thread. This provides handy git and rake >>> >>>>> completions and a >>> >>>>> few other bits and pieces >>> >>>>> >>> >>>>> Can anyone suggest what other great fish features I might be >>> >>>>> missing? >>> >>>>> I'm just not finding fish as compelling as I thought I would. >>> >>>>> >>> >>>>> Josh >>> >>>>> >>> >>>>> >>> >>>>> -- >>> >>>>> >>> >>>>> You received this message because you are subscribed to the Google >>> >>>>> Groups "Ruby or Rails Oceania" group. >>> >>>>> To post to this group, send email to [email protected] >>> >>>>> . >>> >>>>> To unsubscribe from this group, send email to >>> >>>>> [email protected]. >>> >>>>> For more options, visit this group at >>> >>>>> http://groups.google.com/group/rails-oceania?hl=en. >>> >>>>> >>> >>>>> >>> >>>>> >>> >>>> >>> >>> >>> >>> -- >>> >>> >>> >>> You received this message because you are subscribed to the Google >>> >>> Groups >>> >>> "Ruby or Rails Oceania" group. >>> >>> To post to this group, send email to [email protected]. >>> >>> To unsubscribe from this group, send email to >>> >>> [email protected]. >>> >>> For more options, visit this group at >>> >>> http://groups.google.com/group/rails-oceania?hl=en. >>> >>> >>> >>> >>> >> >>> >> -- >>> >> >>> >> You received this message because you are subscribed to the Google >>> >> Groups >>> >> "Ruby or Rails Oceania" group. >>> >> To post to this group, send email to [email protected]. >>> >> To unsubscribe from this group, send email to >>> >> [email protected]. >>> >> For more options, visit this group at >>> >> http://groups.google.com/group/rails-oceania?hl=en. >>> >> >>> > >>> > -- >>> > >>> > You received this message because you are subscribed to the Google >>> > Groups "Ruby or Rails Oceania" group. >>> > To post to this group, send email to [email protected]. >>> > To unsubscribe from this group, send email to >>> > [email protected] >>> > . >>> > For more options, visit this group at >>> > http://groups.google.com/group/rails-oceania?hl=en >>> > . >>> > >>> > >>> >>> -- >>> >>> You received this message because you are subscribed to the Google Groups >>> "Ruby or Rails Oceania" group. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]. >>> For more options, visit this group at >>> http://groups.google.com/group/rails-oceania?hl=en. >>> >>> >> >> >> >> -- >> cheers, >> David Lee >> >> -- >> >> You received this message because you are subscribed to the Google Groups >> "Ruby or Rails Oceania" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/rails-oceania?hl=en. >> >> -- >> >> You received this message because you are subscribed to the Google Groups >> "Ruby or Rails Oceania" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/rails-oceania?hl=en. > > -- > > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
