This is a discussion on OT My command line is driving me crazy. Where to set wrap? within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> On this particular computer, when typing a command line, the cursor gets near the right edge (about column 77 ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| On this particular computer, when typing a command line, the cursor gets near the right edge (about column 77 or 78) and the whole line shifts left instead of wrapping. I HATE THAT. I expect LF CR after column 80. I wish to see what I have typed, not a "<". I have changed TERM from xterm to vt400 to no avail. PLEASE can someone tell me how to stop the "scoot|shift" so the line wraps instead? buck |
| |||
| Hi buck schrieb: > On this particular computer, when typing a command line, the cursor gets > near the right edge (about column 77 or 78) and the whole line shifts left > instead of wrapping. In an xterm/rxvt/whatever or 'real' text-console? Have you tried 'setterm -linewrap on'? Juergen |
| |||
| Juergen Frieling <juergen@beer.com> wrote in news:cftbif$975$1@online.de: > Hi > > buck schrieb: > >> On this particular computer, when typing a command line, the cursor >> gets near the right edge (about column 77 or 78) and the whole line >> shifts left instead of wrapping. > > In an xterm/rxvt/whatever or 'real' text-console? > Have you tried 'setterm -linewrap on'? > > Juergen "Real" text console. I just tried setterm -linewrap on and the same thing still occurs. I also tried -linewrap off just to see if that made any difference. No Joy. Thanks for trying. Buck |
| |||
| buck <buck@private.mil> wrote: > Juergen Frieling <juergen@beer.com> wrote in > news:cftbif$975$1@online.de: > > > Hi > > > > buck schrieb: > > > >> On this particular computer, when typing a command line, the cursor > >> gets near the right edge (about column 77 or 78) and the whole line > >> shifts left instead of wrapping. > > > > In an xterm/rxvt/whatever or 'real' text-console? > > Have you tried 'setterm -linewrap on'? > > > > Juergen > > "Real" text console. I just tried > setterm -linewrap on > and the same thing still occurs. I also tried -linewrap off just to see > if that made any difference. No Joy. > It's not one of those wierd commands that takes + arguments is it, e.g.:- setterm +linewrap (No it isn't according to my system, so ignore the above) I suspect your problem is that the terminal size isn't being set properly somewhere, in this case we need more information about OS, window manager, etc. on "this particular computer". -- Chris Green |
| |||
| On 18 Aug 2004 07:45:05 GMT, usenet@isbd.co.uk wrote: >buck <buck@private.mil> wrote: >> Juergen Frieling <juergen@beer.com> wrote in >> news:cftbif$975$1@online.de: >> >> > Hi >> > >> > buck schrieb: >> > >> >> On this particular computer, when typing a command line, the cursor >> >> gets near the right edge (about column 77 or 78) and the whole line >> >> shifts left instead of wrapping. >> > >> > In an xterm/rxvt/whatever or 'real' text-console? >> > Have you tried 'setterm -linewrap on'? >> > >> > Juergen >> >> "Real" text console. I just tried >> setterm -linewrap on >> and the same thing still occurs. I also tried -linewrap off just to see >> if that made any difference. No Joy. > >I suspect your problem is that the terminal size isn't being set >properly somewhere, in this case we need more information about OS, >window manager, etc. on "this particular computer". No window mgr, this is a TEXT console; X is not even installed. Slackware 10.0 upgraded from 8.1 beta. Matrox MGA200 AGP video card. Lilo boot "vga = normal". Intel 440BX MoBo with Celeron CPU. Kernel 2.4.26. /etc/rc.d/rc.font has 644 permissions. NOTE: This computer has behaved this way since Slackware 8.1 beta was loaded on it. The problem has nothing to do with kernel version, Slackware version or Lilo. (That's why the "OT" in the Subject). It _could_ have to do with the Matrox card, or with /usr/share/terminfo (which one of the many there is selected), Etc. Q: I have nothing special set up as far as bash is concerned, but could a bash setting cause / fix this? Or something in init? buck |
| |||
| On 2004-08-18, buck wrote: > On 18 Aug 2004 07:45:05 GMT, usenet@isbd.co.uk wrote: > >>buck <buck@private.mil> wrote: >>> Juergen Frieling <juergen@beer.com> wrote in >>> news:cftbif$975$1@online.de: >>> >>> > Hi >>> > >>> > buck schrieb: >>> > >>> >> On this particular computer, when typing a command line, the cursor >>> >> gets near the right edge (about column 77 or 78) and the whole line >>> >> shifts left instead of wrapping. >>> > >>> > In an xterm/rxvt/whatever or 'real' text-console? >>> > Have you tried 'setterm -linewrap on'? >>> > >>> > Juergen >>> >>> "Real" text console. I just tried >>> setterm -linewrap on >>> and the same thing still occurs. I also tried -linewrap off just to see >>> if that made any difference. No Joy. >> >>I suspect your problem is that the terminal size isn't being set >>properly somewhere, in this case we need more information about OS, >>window manager, etc. on "this particular computer". > > No window mgr, this is a TEXT console; X is not even installed. > Slackware 10.0 upgraded from 8.1 beta. Matrox MGA200 AGP video card. > Lilo boot "vga = normal". Intel 440BX MoBo with Celeron CPU. Kernel > 2.4.26. /etc/rc.d/rc.font has 644 permissions. > > NOTE: This computer has behaved this way since Slackware 8.1 beta was > loaded on it. The problem has nothing to do with kernel version, > Slackware version or Lilo. (That's why the "OT" in the Subject). It > _could_ have to do with the Matrox card, or with /usr/share/terminfo > (which one of the many there is selected), Etc. > Check in /etc/termcap to see if you have the wide option set for whatever TERM you are using. It is set by prepending '-w' to the name, for example vt102-w, as opposed to vt102. For example, if you see an entry like: v2|vt102-w|DEC vt102 compatible:\ change it to: v2|vt102|DEC vt102 compatible:\ -- Mike Peters mike [-AT-] ice2o [-DOT-] com http://www.ice2o.com |
| |||
| On Wed, 18 Aug 2004 19:56:05 GMT, Mike Peters <o0__mike__0oREMOVE@THIShotmail.com> wrote: >On 2004-08-18, buck wrote: >> On 18 Aug 2004 07:45:05 GMT, usenet@isbd.co.uk wrote: >> >>>buck <buck@private.mil> wrote: >>>> > buck schrieb: >>>> > >>>> >> On this particular computer, when typing a command line, the cursor >>>> >> gets near the right edge (about column 77 or 78) and the whole line >>>> >> shifts left instead of wrapping. >> >Check in /etc/termcap to see if you have the wide option set for >whatever TERM you are using. It is set by prepending '-w' to the name, >for example vt102-w, as opposed to vt102. For example, if you see an >entry like: >v2|vt102-w|DEC vt102 compatible:\ >change it to: >v2|vt102|DEC vt102 compatible:\ BLESS YOU. While that is not the fix, it led me to it. There was no /etc/termcap So I linked termcap-Linux to termcap and BEHOLD, the problem is fixed. (Rhetorical: I wonder how it happened that termcap did not get created during the original installation? NOT RHETORICAL: Why don't termcap-Linux and termcap-BSD _say_ at the top to copy to termcap?!! This is typical in my experience; you are expected to KNOW that so it is not documented. Grr. And 'man termcap' says termcap is obsolete. OH FSCK.) buck |
| ||||
| buck <buck@private.mil> wrote: > > > >I suspect your problem is that the terminal size isn't being set > >properly somewhere, in this case we need more information about OS, > >window manager, etc. on "this particular computer". > > No window mgr, this is a TEXT console; X is not even installed. > Slackware 10.0 upgraded from 8.1 beta. Matrox MGA200 AGP video card. > Lilo boot "vga = normal". Intel 440BX MoBo with Celeron CPU. Kernel > 2.4.26. /etc/rc.d/rc.font has 644 permissions. > It can still be that the application doesn't know the size of the window, even if it's a console window something, somewhere has to tell the display routines to wrap lines at 80 columns (or some other width). If the shell sets the window size wrong (or doesn't set it correctly) then it might explain the problem. -- Chris Green |