VMD-L Mailing List

From: Sabuj Pattanayek (sabuj.pattanayek_at_Vanderbilt.Edu)
Date: Thu Apr 21 2005 - 17:46:59 CDT

Ahh, thanks for pointing out that line it seems the "-0-0" of the
"80x11-0-0" is causing the problems with this xterm version so I just
modified:

setenv VMD_WINGEOM "-geometry 80x11-0-0"

to

setenv VMD_WINGEOM "-geometry 80x11"

in the /usr/bin/vmd startup script and now it works fine. However, I'm
not sure what the -0-0 does.

..Sabuj Pattanayek

John Stone wrote:
> Try running xterm with the same options the VMD startup script uses:
> xterm -geometry 80x11-0-0 -sb -sl 1000 -e /bin/csh
>
> Does that work for you?
>
> John Stone
> vmd_at_ks.uiuc.edu
>
> On Thu, Apr 21, 2005 at 05:32:55PM -0500, Sabuj Pattanayek wrote:
>
>>Yes that is correct. I can open an xterm and see the text. I am using
>>this version of xterm:
>>
>>[ebuild R ] x11-terms/xterm-200-r1
>>
>>
>>John Stone wrote:
>>
>>>Hi,
>>> Is it possible you've got .xdefaults files with odd color
>>>settings for 'xterm' on your account? I assume that running
>>>'xterm' by hand yields a usable terminal?
>>>
>>> John Stone
>>> vmd_at_ks.uiuc.edu
>>>
>>>On Thu, Apr 21, 2005 at 05:19:57PM -0500, Sabuj Pattanayek wrote:
>>>
>>>
>>>>Hi,
>>>>
>>>>When I start the amd64 version of vmd-1.8.3 the console is blank, like
>>>>an xterm with white text on white background. Trying to highlight
>>>>anything in the vmd console does not make it "appear". How do I make
>>>>this return to the default coloring scheme so I can see the text (black
>>>>on white)?
>>>>
>>>>Thanks,
>>>>Sabuj Pattanayek
>>>
>>>
>