Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Dtterm and KDE

10 views
Skip to first unread message

Adam M.

unread,
Nov 14, 2002, 2:20:38 PM11/14/02
to
I recently installed KDE on my U60, to replace CDE. It runs great but
dtterm has begun to behave funny. ^c no longer works as a break (del
has taken over this function) and when I type the @ symbol on the
command line it behaves like ^u (clears the line). Anyone know what
is going on, or how to fix it? Also, does anyone know how to make the
front key (sun type 5 keyboard) work under kde?

thanks
-Adam

dttermkdecde

Michael Piotrowski

unread,
Nov 16, 2002, 7:46:22 AM11/16/02
to
seve...@excite.com (Adam M.) writes:

> I recently installed KDE on my U60, to replace CDE. It runs great but
> dtterm has begun to behave funny. ^c no longer works as a break (del
> has taken over this function) and when I type the @ symbol on the
> command line it behaves like ^u (clears the line). Anyone know what
> is going on, or how to fix it?

dtterm can use the ttyModes resource to set up the terminal
characteristics, so that it's not necessary to call stty every time a
dtterm window is created. If you're using CDE, this resource will be
set automatically to something like this:

*ttyModes: erase ^H intr ^C kill ^U start ^Q stop ^S swtch ^@ susp ^Z

Now, if you're not running CDE, you'll either have to set the resource
yourself (in ~/.Xdefaults, or wherever you put them in KDE), or you'll
have to make sure that stty is run (e.g., in .kshrc, .bashrc or
whatever you're using).

--
Michael Piotrowski, M.A. <m...@dynalabs.de>
Public key at <http://www.dynalabs.de/mxp/pubkey.txt>

bad_knee

unread,
Nov 18, 2002, 2:49:38 PM11/18/02
to
try this in your .bashrc (may work in .cshrc) I had the same
problem with icewm.

stty intr \^C
stty erase \^H
stty susp \^Z
stty eof \^D
stty kill \^U


And in ~/.Xdefaults
(! is a comment and only here for reference)

! The CDE fonts are only set by resources, so there is no unique switch
! that will override them. You should be able to set them by using the
! following resources, with your application's class instead of "Dtterm".
! Dtterm*font: terminal10
! Dtterm*Font: -misc-fixed-bold-*-*-*-18-*-*-*-*-*-iso8859-1
! Dtterm*XmFontList: -misc-fixed-bold-*-*-*-18-*-*-*-*-*-iso8859-1
!Dtterm*FontList: -misc-fixed-bold-*-*-*-18-*-*-*-*-*-iso8859-1
!Dtterm*FontSet: -misc-fixed-bold-*-*-*-18-*-*-*-*-*-iso8859-1
!Dtterm*XmText*FontList: -misc-fixed-bold-*-*-*-18-*-*-*-*-*-iso8859-1
!Dtterm*XmTextField*FontList: -misc-fixed-bold-*-*-*-18-*-*-*-*-*-iso8859-1
!Dtterm*userFontList: -dt-interface user-medium-r-normal-l*-*-*-*-*-m-*
!Dtterm*userFontList: -misc-fixed-bold-*-*-*-18-*-*-*-*-*-iso8859-1
!Dtterm*userFont: -misc-fixed-bold-*-*-*-18-*-*-*-*-*-iso8859-1
!Dtterm*Font: -misc-fixed-bold-*-*-*-18-*-*-*-*-*-iso8859-1
!Dtterm*systemFont: -misc-fixed-bold-*-*-*-18-*-*-*-*-*-iso8859-1
!Dtterm*textFontList: -misc-fixed-bold-*-*-*-14-*-*-*-*-*-iso8859-1

Dtterm*textFontList: -schumacher-clean-*-*-*-*-14-*-*-*-*-*-*-*
Dtterm*background: black
Dtterm*foreground: gray80

Logan Shaw

unread,
Nov 18, 2002, 9:52:42 PM11/18/02
to
In article <e817ca4d.02111...@posting.google.com>, bad_knee wrote:
> try this in your .bashrc (may work in .cshrc) I had the same
> problem with icewm.
>
> stty intr \^C
> stty erase \^H
> stty susp \^Z
> stty eof \^D
> stty kill \^U

It might be a little more efficient to invoke stty only once instead
of 5 times:

stty intr ^C erase ^H susp ^Z eof ^D kill ^U

I've left out the backslashes because they're not needed when you
put a command in a .bashrc or .cshrc. The reason for this is that
they serve to protect the special "^" command history character,
and that character is only recognized when you're working interactively
with the shell (not when it's reading a file of commands).

- Logan

bad_knee

unread,
Nov 19, 2002, 5:13:11 PM11/19/02
to
>
> It might be a little more efficient to invoke stty only once instead
> of 5 times:
>
> stty intr ^C erase ^H susp ^Z eof ^D kill ^U

hmm. That's cool. Definately cleans things up.


> with the shell (not when it's reading a file of commands).

man, that's going to be a time saver. Thanks!

0 new messages