[Fish-users] debugging fish

Hi everyone Does anyone know how to run a shell like fish under gdb and separate gdb's and fish's outputs to two different terminals? I tried following thishowto for debugging ncurses programs, but it fails because gdb can't set the sec

Re: [Fish-users] [feature request] preexec to facilitate fasd'ish tool (chdir and xdg-open file based on approximation matching on older pathes)

On Dec 21, 2012, at 10:15 AM, Cheer Xiao wrote: > 2012/12/19 ridiculous_fish : >> After running a command, some processing occurs on a background thread. When >> that's done, it notifies the main thread, which adds the item to the >> history. The earliest that the main thread can respond to the

Re: [Fish-users] Why sometimes a 'cd' command gives me '>' prompt?

Do you have a very wide prompt? If your prompt is so long that it cannot fit in your window, fish will cut it down to just a '>' On Dec 26, 2012, at 1:04 AM, Magicloud Magiclouds wrote: > It is something like the following. > > $ cd files/usr/bin/ > > cd .. > $ > > -- > 竹密岂妨流水过 > 山高哪阻野云飞 >

Re: [Fish-users] debugging fish

Hi Jan, I'm not sure how to do that in one terminal, but it's straightforward with two. I do this in the shell targeted for debugging: > echo %self 26414 And in another window: > gdb attach 26414 In case you were't familiar with that technique, hope that helps! _fish On Dec 27, 2012,

Re: [Fish-users] Why sometimes a 'cd' command gives me '>' prompt?

Ah, I see. The path in prompt sure is very long when this happens. Thank you. On Fri, Dec 28, 2012 at 12:51 PM, Magicloud Magiclouds wrote: > Ah, I see. The path in prompt sure is very long when this happens. > Thank you. > > > 2012/12/28 ridiculous_fish > >> Do you have a very wide prompt? If