On 1 Apr 2010, at 22:50, David Frascone wrote: > I'm using the normal mac terminal -- from the console, not ssh'ed > in. And, I have not messed with the fish bindings . . .. . let me > check. Yup - \ck is kill-line. And, that function in kill.c does > not get called. >
That is strange. I'm using the regular terminal, too. On OS/X 10.5.8 As far as I understand, if kill-line is called, then kill_add() has to be called, too. Could it be because fish is my login shell? If what you say is right, i.e. the line editing is not controlled by fish, then if you rebind \ck to something else, it will not affect what happens when you press ctrl-k. Michael > > > On Thu, Apr 1, 2010 at 4:39 PM, michael <[email protected]> wrote: > On 1 Apr 2010, at 21:18, David Frascone wrote: > > > I'm not sure this would work as expected -- at least not in the > > normal terminal windows. It seems like ctrl-k is being processed by > > the terminal or os itself, not by fish. > > i.e. kill_add is *not* being called when I press ctrl-k. > > Strange... it does work for me. But \ck is bound to kill-line? > > Maybe that is why I'm having problems with ctrl-y. How come your ctrl- > k/ctrl-y are processed by the terminal? What terminal are you using? > > > Michael > > > > > -Dave > > > > On Wed, Mar 31, 2010 at 4:28 AM, michael <[email protected]> > wrote: > > Hi, > > > > Since on OSX the X11 server is not always running, it would be > better > > to sync the killring with the pasteboard instead of the X11 > clipboard. > > That is very easy to accomplish: > > > > in kill.c: > > That is actually very easy to fix: in kill.c:99c99 > > < wchar_t *cmd = wcsdupcat(L"echo -n ", escaped_str, > > L"| pbcopy" ); > > --- > > > wchar_t *cmd = wcsdupcat(L"echo ", escaped_str, L"| > > xsel -b" ); > > > > One should do a conditional, so that this is only called in OSX, or > > even have it configurable... > > > > Michael > > > > > > > ------------------------------------------------------------------------------ > > 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 > > > > > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ 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
