[Techtalk] making a terminal wider than 80 columns
sara
neuroticia at neuroticia.net
Thu Feb 13 00:35:11 EST 2003
If you create another temporary user with the default home folder, log
in as that, and use eterm--does it work? Or does it only work under
root? If only under root, that suggests permissions issues. If only
"not" under your "you" account, then it suggests a problem with your
personal settings.
I've found that under Debian I often break my default user, and that the
quickest (though non-impressive, and non-geeky) thing to do is back up
my files, re-create the home directory in its default state, and restore
the files--saving the permission related files for last. Helps me narrow
things down a bit when I'm not sure what's causing it to break.
-Sara
> -----Original Message-----
> From: techtalk-admin at linuxchix.org [mailto:techtalk-
> admin at linuxchix.org] On Behalf Of Emma Jane Hogbin
> Sent: Wednesday, February 12, 2003 11:29 PM
> To: techtalk at linuxchix.org
> Subject: Re: [Techtalk] making a terminal wider than 80 columns
>
> On Wed, Feb 12, 2003 at 01:10:00PM -0500, Caitlyn M. Martin wrote:
> > Anyway, I am not having the problem you described. Which version of
> > ETerm are you running? On what distro?
>
> Eterm 0.9.2
> Fluxbox
> Debian (Sid)
>
> Ah, this is helpful: it only breaks when I'm being myself. Root is
> fine.... ... ... .. :/
>
> > I'm interested because I'd rather compile a newer version when I
> upgrade
> > to Red Hat 8.1 than continue to use this old one.
>
> You're probably safe...especially considering that Eterm works as root
> but
> not as me.
>
> > BTW, I've noticed vi complains (and doesn't work) if you have a
> terminal
> > width greater than 80 characters. Is there a fix for that? Anyone?
>
> Mine's ok...I'm using vim (which is what you're probably using if
> you're
> using RedHat). Have you tried setting textwidth?
>
> set bs=2 " allow backspacing over everything in insert
> mode
> set ai " always set autoindenting on
> set nobackup " do not keep a backup file
> set viminfo='20,\"50 " read/write a .viminfo file, don't store more
> " than 50 lines of registers
> set history=50 " keep 50 lines of command
> line history
> set ruler " show the cursor position
> all the time
> set number " show line numbers
> set textwidth=75 " create a new line automagically at
> " column number 75
>
> I have the above in my .vimrc file-- which is my standard. Then when
> I'm
> editing PHP I use vii (instead of vi). In my .bashrc file I have:
> alias vii="vi -c ':set textwidth=0'"
> ^^^^^^^^^^^ means don't automagically make new
> lines when you get to column X
>
> (don't forget to source .bashrc if you add this).
>
> I have a few other programs that have "programming" defaults vs.
> "regular"
> defaults. I just double the last letter of the program name to run the
> "programming" version.
>
> emma
>
> --
> Emma Jane Hogbin
> [[ 416 417 2868 ][ www.xtrinsic.com ]]
> _______________________________________________
> Techtalk mailing list
> Techtalk at linuxchix.org
> http://mailman.linuxchix.org/mailman/listinfo/techtalk
More information about the Techtalk
mailing list