>> - On my OS X system mouse always generates chars on screen, instead of >> moving any mouse pointer. >> Even in xterm. How can that be fixed? > > You will have to exactly check what this character means. > Probably your terminal program uses non standard escap sequence for > mouse events or you have wrong terminal description in your termcap/terminfo > database or simply TERM envvar is wrongly set. > BTW what echo $TERM shows and what terminal program you are using?
'xterm' in this case, this is what 'echo $TERM' shows. >> - When I login using my admin acc in terminal, left/right keys don't work, >> instead I see 'A' and 'B' chars. >> Also the colors are missing. > > The same problem as above. > mc -c > forces using colors even if termcap/terminfo do not contain valid entries > for color output. > Anyhow it does not seems to be MC problem. I'm just the dumb user here. Could be that someone at Apple (or elsewhere) messed up something but it won't help my case unfortunately. >> - I use keyboard cut/paste using Shift+Arrows a lot. Any replacement for >> that in MC? > > It will depend on used window manager. I.e. I can use mouse to mark any text > and paste it using middle key or SHIFT+INSERT and it's not done by MC but > by terminal program and how it's integrated with the desktop. Please remember > that MC can be executed on completely different computers then the one you > are using directly so the sense of C&P buffer is different here. > Anyhow except the access to main desktop C&P buffer given by terminal program > MC has own copy & past buffer which you can use between different MC instances > on the same user account. You can safe any block in this buffer by pressing > CTRL+F (in fact it's a simple file so you can use many different > buffers/files) > and the past it using F15 (or SHIFT+F5). > Of course extended Fn keys needs well configured terminal. I know about the mouse copy/paste, but it's just not very convenient, since it slows down work quite much. There are case, f.e. long cmdlines which wrap (BTW completely messing up the screen), where such method doesn't work, or same is true when field content is larger than visible editing area. >>> - I want to put current file name into command line. How can I do that? >>> (Ctrl+Enter in Far do the job). >> It's Esc then Enter. >>> - Find file command shortcut is "M-?". What does it mean? >> I've found that file find is Ctrl+S then you type filename you look for. >> BTW file selection is Ctrl+T on OS X if anyone is interested. > > If you look closer at inkey code in inkey.ch then you will find that > all keys like: > CTRL+[A-Z] > give values which can be calculated as ASC( "[A-Z]" ) - 64 and the same > fact exists in all terminal programs. So if your terminal program does > not accept some key combination which has corresponding direct value <n> > between 1 and 26 then you can simply use CTRL+<letter> where <letter> > is <n>-th letter, i.e. CTRL+ENTER is CHR(10) and it's the same as > CTRL+M because M is 10-th letter, etc. > CTRL+<letter> combinations works in practice with all devices, as you > can see they are supported for a long time (though looks that even hipper > advanced Clipper users forgot about it ;-)) and very often helps to resolve > problems with non standard keyboards. After 25 years of PC domination > we have again many devices like PDA or cellar phones with often really > strange keyboards so the problem will return in the future. I remember these mappings, but my simple problem is that they are just not convenient. I mean if I have a bloody 'Ins' key on my keyboard, and an 'End' key, why on earth should I remember a Ctrl combination? It's not only *nix terminal issue (but for the most part it is), some parts of it is OS X, missing Insert is a common OS X complaint. F.e. even in my own app this is a huge problem and makes terminal based GTs useless for me and even GTXWC needing some getting used to. My app uses pretty much all key combinations available on dos/win/os2, and if I have to drop some combinations, like all "Shift+key" ones, it's real trouble. It's even worse since I have to drop different combinations depending on various factors, like term type, keys, OS, etc. I understand MC got designed to adapt to these problems, but the end result is a quite clumsy keyboard interface IMO, and inconsistent behavior depending on these platforms. Pretty much off topic rant, but anyway I wish sometimes *nix systems in general would focus on those dumb human beings who are sitting next to those computers and make their job easier, I know there is lots of things to focus on, plus general portability needs some sacrifices, but perhaps eventually these will get resolved. At least I hope. Maybe a GUI app what emulates CUI and has access to all the keys in a proper way is the solution. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
