On 8/22/06, Martin Baehr <[EMAIL PROTECTED]> wrote: > On Tue, Aug 22, 2006 at 06:32:31PM +0200, Axel Liljencrantz wrote: > > And if you try to enter the completions that originally caused the > > scrolling? > > same. > > > You can get these using 'complete -C', e.g. to get the > > completions printed when entering 'ls -<TAB>', use 'complete -C "ls > > -"'. > > -C does not work, but this does: > fish_pager 0 "" (complete --do-complete="a")
Oh, of course. The completion string is an optional argument (if unspecified, the current commandline is used). complete -C"ls -" does work. > > however, the output is different because () mangles the newlines, which > i assume fish internally doesn't. I think I figured out the problem. If you look closely at the exit message, I think you will find that it is something like fish: Job 1, "fish_pager 0 foo bar baz ..." terminated by signal SIGINT (Quit request from job control (^C)) In other words, this is expected behaviour. In the next version, this will not be an issue since fish will start sending the completions through a pipeline instead of through the commandline, in order to avoid OS limits on the number of arguments to exec(). (Thanks for the patch, stew!) But I guess there should also be an upper limit to the length of the message, or this might crop up in other places. I'll fix it. > > > [fish_inputrc_path] > > What would you suggest the path should contain? > > @sysconfdir@ and $HOME? > > basicly something like fish_complete_path and fish_function_path, > although it could probably be a path of files instead of directories. > it would then be /etc/inputrc, /etc/fish_inputrc, $HOME/.fish_inputrc > > (note that i have an issue with fish file locations, but more on that in > an extra mail later) A list like that is used right now to find the inputrc file to use. I though this was about providing a search path for the $include command inside the inputrc file. I must have misunderstood. > > > But that would be silly in many ways, since _all_ the functionality > > already lives inside fish, it's just reusing the same code. > > you could put it into a library, and link both programs against it, or, > you could make fish accept the filename as indicator of which > functionality you want to run. (like busybox) > > it would be nice to have the interactive read accessible seperately, > then other shells could pick it up as well. Other shells can just use "fish -c 'read foo; echo $foo'". But I guess it might make sense to have a standalone reading program. Worth considering. > > greetings, martin. > -- > cooperative communication with sTeam - caudium, pike, roxen and unix > offering: programming, training and administration - anywhere in the world > -- > pike programmer travelling and working in europe open-steam.org > unix system- bahai.or.at iaeste.(tuwien.ac|or).at > administrator (caudium|gotpike).org is.schon.org > Martin Bähr http://www.iaeste.or.at/~mbaehr/ > -- Axel ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
