LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   slackware problem with aterm and vi (https://www.linuxquestions.org/questions/linux-newbie-8/slackware-problem-with-aterm-and-vi-130895/)

infamous41md 01-02-2004 12:40 PM
slackware problem with aterm and vi
 
when i try to use vi and aterm i get all sorts of broken output. the document never opens correctly, only the first lines are displayed and it's halfway down the screen. i've been researching trying to see if anyone else has had this problem, and it seems not. any ideas on where to start? vi works fine in xterm and rxvterm.

synaptical 01-02-2004 12:48 PM
what about vim?

infamous41md 01-02-2004 01:09 PM
yes vim works perfectly! now i just need to figure out how to get my syntax highlighting back. thanks!

synaptical 01-02-2004 01:16 PM
this might work as a template:
http://mail.linux.ie/pipermail/cork/...il/000961.html

otherwise, there are plenty of sites on google about it. :)

zer0python 01-02-2004 03:57 PM
here is my ~/.vimrc file that works under Slackware 9.1 with vim/aterm, hope it helps..

Code:

if v:progname =~? "evim"
  finish
endif

set nocompatible
set backspace=indent,eol,start
set autoindent
set nobackup
set history=50
set ruler
set showcmd
set incsearch

map Q gq

if &t_Co > 2 || has("gui_running")
  syntax on
  set hlsearch
endif

if has("autocmd")
  filetype plugin indent on
  autocmd FileType text setlocal textwidth=78
  autocmd BufReadPost *
    \ if line("'\"") > 0 && line("'\"") <= line("$") |
    \  exe "normal g`\"" |
    \ endif
endif
:)

Kovacs 01-02-2004 05:29 PM
I have had the same problem. I set all my aterm properties in ~/.Xdefaults (with settings from ikaro's fluxmod site). One line sets the geometry of the window:

aterm*geometry: 80x35

ie. the aterm is meant to open 80 columns wide by 35 lines deep. However when using fluxbox 9.6, if I changed the size of the aterm window and then set it to remember the window size, I would get the broken output in vi that you mentioned. The window was opening at whatever dimensions I had set it to remember to open at, yet aterm still thought it was meant to run at 80x35, so the output was garbled.

The solution in my case was to delete the remembered settings for the aterm window, and let aterm start with whatever dimensions were set in .Xdefaults.

infamous41md 01-02-2004 06:41 PM
thanks for the help! i was going to have a look at 'info vi' again but ya saved me the trip :)
my current problem is figuring out why 'Ctrl-l' no longer clears my aterm screen. 'Ctrl-l' works fine on all my other terminals :(


All times are GMT -5. The time now is 10:34 PM.