On 9/15/06, Martin Bähr <[EMAIL PROTECTED]> wrote: > hi, > > here is a suggestion related to the fact that completions in fish are so > informative that sometimes the completion is all i want. > > this bites me when the item i want to lookup has only one completion, > because then the completion is just filled in and the informative pager > output is never shown.
I have been bitten by this a few times as well. > > so therefore i would like to request to always show the pager with the > info about the completed item, even if it is only a single item to show. I'll try to add a patch that implements this behaviour and add it to the darcs tree. Everyone can try it out and see how it works. Feel free to remind me if I haven't done it in a few weeks time. > > related to that, it would also be helpful to see all completions that > include wildcards with the wildcards expanded. so that it > is possible to use completions to verify that the wildcards actually > expand to the desired selection. This could be done either by including the full filename in the description or by allowing a per-completion prefix that is the expanded string instead of the string to be completed. Both should be doable, though I fear that the latter is a bad idea because the competions won't line up anymore. The main problem I see with this is that completions may become too wordy and take up too much space. But we won't know for sure unless we try, I guess. > > currently, i often find myself in the middle of a longer command that > involved wildcards, being forced to abort and first verify with ls that the > wildcards are actually what i want. > being able to do have wildcards expanded in the completion pager, > would make me quite a bit more productive. Another option here would be to implement the sometimes mentioned status line idea, i.e. whenever possible, a status line tells you what the argument under the cursor will expand to. When moving over a command, if could be something like 'command: /usr/bin/python', and when over a wildcard it could be the list of matches, etc. The obvious trouble is that the wildcard matches will not always fit a single line. You could possibly fit something like: ls ~/a*/w*/s???.txt a* matches 'author' and 'art'; w* has 8 matches; s???.txt has 89 matches It would be possible to add a keybinding for describing all the details of the current command, including wildcard matches, history commands (if those are ever implemented) etc., but I don't really like this path since I feel it is not very discoverable. > > 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
