On 9/1/06, Martin Baehr <[EMAIL PROTECTED]> wrote: > On Fri, Sep 01, 2006 at 04:11:37PM +0200, Axel Liljencrantz wrote: > > True. On the other hand, starting the pager position at e.g. 23% is > > pretty unintuitive. > > i simply disagree on that. i find it quite meaningful. > it's not the start but how much i see. > > > fish_pager will try to [ ... ] make everything fit on one page if even > > remotely possible. If it fails, then the paged output will be given > > much more room again. > > ah, ok, have not noticed that yet.
I think a lot of the little in fish are like that - they're very useful, but you don't notice them, because they're not 'showy'. They simply take a way an annoyance. :-) > > > > builtin (8) e (13) INSTALL p (7) u (3) > > > c (12) f (8) k (3) reader.h w (6) > > > _darcs gen_hdr (2) m (3) README x (13) > > > doc_src h (8) Makefile.in s (7) > > > Doxyfile (2) i (9) output. (2) t (3) > > I think that might be taking it too far. [ ... ] This type of workflow > > would be impossible if the pager was hellbent on always fitting > > everything onto a single screen. > > that is true, didn't think of that. obviously i am not using these > features much yet. it would still be useful for files though. I'm sure there are lots of situations where what you really need is a simply overview of possible completions. The thing is, it's kind of hard for the pager to know when this would make sense and when it wouldn't. > > > Good point. Unfortunatly, the sequence for shift-space and space are > > the same. > > strange. > mozilla uses shift-space for page-up. > maybe in a terminal that's different. Few people know how primitive the terminal interface really is. You read a single stream of characters from a stream. Control-characters use byte values 1-26, which is also used by a few other keys, e.g. enter and tab. That is why e.g Control-j and the enter key both insert a newline - they both send byte value 10 to the terminal. Control-i and tab are the same thing for the same reason. It is impossible to tell these apart for a terminal program. Shortcuts using the Alt key are usually handled by prepending the regular character with an escape character. For example, pressing Alt-p will generate the two characters, first an escape (i.e. byte value 27) and then the letter p. This is exactly the same sequence as generated when first pressing the escape key and then the p key. 'Strange' characters, like the arrow keys, are given magical escape sequences. Left arrow can for example be '\e[D'. Some programs (like vi, emacs and fish) use the timing of the individual keypresses to try and tell the difference between pressing left arrow and manually entering the same sequence, but most programs don't. These sequences also vary between terminal, you have to use a special database to look them up. Unfortunatly, many (most) terminal emulators don't actually do exactly what the database says they should. Konsole is probably the worst in this regard, since it allows you to change what sequence is generated by every single keystroke as well as change what terminal you claim to emulate (And the default configuration is incorrect). Also, the terminfo database simply doesn't contain sequences for all possible key combinations, e.g. Alt-Up isn't covered. To support such 'weird' key combos, you need to manually test all common terminal programs and find out what they do. And many terminal emulators simply dont send any sequence at all for some key combinations, including Ctrl-Space. Alt-Left doesn't work on all terminals either. > > > Alt-Space could be implemented with no trouble. Or Alt-Up and > > Alt-down. > > would not help. most window managers use alt for themselves. > any alt-key combo does not work in my terminal. Bummer. I'm open to suggestions. > > > > it would also be nice if the pager could ask if it is going to show more > > > than a screenful of choices. > > Why would that be useful? > > because i still have my bash motions hardwired here. and am not used to > that yet: > > > If you don't want the completions, you can just keep on typing, > > since pressing any normal key will exit the pager > > ah, i just realized what keeps me from doing that: > to keep on typing i need to see where i am. the pager overwrites the > commandline and so i get lost, because i do not know what to type, > because i don't remember what i have typed already. > > with out the commandline visible i feel that i have to exit the pager > first before i can get back to the commandline. it took me a while to > get used to the fact that any key will exit the pager, and then i > started the habit of always hitting esc to exit it. > > if you could shorten the pager by one line so that the commandline is > always visible then going on typing would feel more natural That should be possible. I'll test it and see how it works. > > > If your terminal emulator supports it, fish_pager will > > even restore the terminal contents from before running fish_pager on > > exit. > > hmm i thought that screen does support that. Unfortunatly, I don't think so. > > 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
