Wed, Apr 3 2002
18:39:56
|
|
Request created by guest
|
|
Subject: Vask (curses) problems with KDE terminal
Platform: GNU/Linux/i386
grass obtained from: Trento Italy site
grass binary for platform: Compiled from Sources
GRASS Version: CVS
Hi,
a long term problem on KDE is that in KDE terminal the carriage return (or whatever)
doesn't seem to work properly. The problem must be related to curses in the
VASK library.
It happens in all coordinate windows (g.region etc) as well as v.digit etc.
A screenshot (46kb) is here:
http://mpa.itc.it/markus/tmp/kde_term_problem.gif
Here, using "t" in Digitize menu to toggle the vector type, end up with
above result.
When entering the raster resolution in g.region (menu1), the second line is reached
at mid of the line, not at the beginning.
I think that quite a few people are using KDE and KDE-term. It would be great
to
have that problem fixed. In xterm everything is fine.
Thanks,
Markus
|
|
Wed, Apr 3 2002
22:17:52
|
|
Mail sent by glynn.clements@virgin.net
|
|
Return-Path |
<glynn.clements@virgin.net>
|
Delivered-To |
grass-bugs@lists.intevation.de
|
From |
Glynn Clements <glynn.clements@virgin.net>
|
MIME-Version |
1.0
|
Content-Type |
text/plain; charset=us-ascii
|
Content-Transfer-Encoding |
7bit
|
Message-ID |
<15531.25380.261976.167218@cerise.nosuchdomain.co.uk>
|
Date |
Wed, 3 Apr 2002 21:16:36 +0100
|
To |
Request Tracker <grass-bugs@intevation.de>
|
Cc |
grass5@grass.itc.it
|
Subject |
Re: [GRASS5] [bug #998] (grass) Vask (curses) problems with KDE terminal
|
In-Reply-To |
<20020403163956.81573139FF@lists.intevation.de>
|
References |
<20020403163956.81573139FF@lists.intevation.de>
|
X-Mailer |
VM 6.94 under 21.4 (patch 4) "Artificial Intelligence (candidate #1)" XEmacs Lucid
|
X-Spam-Status |
No, hits=0 required=5 tests= |
Request Tracker wrote:
> Subject: Vask (curses) problems with KDE terminal
> a long term problem on KDE is that in KDE terminal the carriage return (or
whatever)
> doesn't seem to work properly. The problem must be related to curses in the
> VASK library.
This sounds like a curses problem; in which case, GRASS can't do
anything about it.
--
Glynn Clements <glynn.clements@virgin.net>
|
|
Wed, Apr 3 2002
22:41:07
|
|
Mail sent by neteler@itc.it
|
|
Return-Path |
<neteler@itc.it>
|
Delivered-To |
grass-bugs@lists.intevation.de
|
Date |
Wed, 3 Apr 2002 22:41:02 +0200
|
From |
Markus Neteler <neteler@itc.it>
|
To |
Glynn Clements <glynn.clements@virgin.net>
|
Cc |
Request Tracker <grass-bugs@intevation.de>, grass5@grass.itc.it
|
Subject |
Re: [GRASS5] [bug #998] (grass) Vask (curses) problems with KDE terminal
|
Message-ID |
<20020403224102.B32747@itc.it>
|
Mail-Followup-To |
Glynn Clements <glynn.clements@virgin.net>, Request Tracker <grass-bugs@intevation.de>, grass5@grass.itc.it
|
References |
<20020403163956.81573139FF@lists.intevation.de> <15531.25380.261976.167218@cerise.nosuchdomain.co.uk>
|
Mime-Version |
1.0
|
Content-Type |
text/plain; charset=us-ascii
|
Content-Disposition |
inline
|
User-Agent |
Mutt/1.2.5.1i
|
In-Reply-To |
<15531.25380.261976.167218@cerise.nosuchdomain.co.uk>; from glynn.clements@virgin.net on Wed, Apr 03, 2002 at 09:16:36PM +0100
|
X-Spam-Status |
No, hits=0 required=5 tests= |
On Wed, Apr 03, 2002 at 09:16:36PM +0100, Glynn Clements wrote:
>
> Request Tracker wrote:
>
> > Subject: Vask (curses) problems with KDE terminal
>
> > a long term problem on KDE is that in KDE terminal the carriage return (or
whatever)
> > doesn't seem to work properly. The problem must be related to curses in the
> > VASK library.
>
> This sounds like a curses problem; in which case, GRASS can't do
> anything about it.
... if so: why does it work well for xterm? Or does curses behave
differently in xterm and KDE (or other) terminals?
Markus
|
|
Wed, Apr 3 2002
23:03:09
|
|
Mail sent by glynn.clements@virgin.net
|
|
Return-Path |
<glynn.clements@virgin.net>
|
Delivered-To |
grass-bugs@lists.intevation.de
|
From |
Glynn Clements <glynn.clements@virgin.net>
|
MIME-Version |
1.0
|
Content-Type |
text/plain; charset=us-ascii
|
Content-Transfer-Encoding |
7bit
|
Message-ID |
<15531.28119.588136.144224@cerise.nosuchdomain.co.uk>
|
Date |
Wed, 3 Apr 2002 22:02:15 +0100
|
To |
Markus Neteler <neteler@itc.it>
|
Cc |
Request Tracker <grass-bugs@intevation.de>, grass5@grass.itc.it
|
Subject |
Re: [GRASS5] [bug #998] (grass) Vask (curses) problems with KDE terminal
|
In-Reply-To |
<20020403224102.B32747@itc.it>
|
References |
<20020403163956.81573139FF@lists.intevation.de> <15531.25380.261976.167218@cerise.nosuchdomain.co.uk> <20020403224102.B32747@itc.it>
|
X-Mailer |
VM 6.94 under 21.4 (patch 4) "Artificial Intelligence (candidate #1)" XEmacs Lucid
|
X-Spam-Status |
No, hits=0 required=5 tests= |
Markus Neteler wrote:
> > > Subject: Vask (curses) problems with KDE terminal
> >
> > > a long term problem on KDE is that in KDE terminal the carriage return
(or whatever)
> > > doesn't seem to work properly. The problem must be related to curses in
the
> > > VASK library.
> >
> > This sounds like a curses problem; in which case, GRASS can't do
> > anything about it.
>
> ... if so: why does it work well for xterm? Or does curses behave
> differently in xterm and KDE (or other) terminals?
Yes and no.
In general[1], curses uses the value of $TERM to obtain a terminal
description from either termcap or terminfo[2]. It uses that
description to determine exactly which codes should be sent to the
terminal to redraw the screen.
If curses doesn't redraw the screen correctly, this indicates that the
terminfo (or termcap) entry corresponding to $TERM doesn't accurately
describe the behaviour of the terminal.
Note that terminal emulators (e.g. xterm) have historically been
problematic. Their behaviour is often highly configurable, but any
given terminal description corresponds to a specific configuration.
The usual way to support this is to provide multiple terminal
descriptions (look in e.g. /usr/share/terminfo/x for all of the
different xterm variants), corresponding to different option settings.
However, this only works if the user ensures that TERM is set to the
variant which matches the settings which are actually in use.
[1] Some systems allow a complete terminal description to be specified
via $TERMCAP.
[2] Depending upon how curses was compiled. Some older systems only
support termcap. Newer systems may either only use terminfo, or try
terminfo first, then try termcap if a terminfo entry can't be found.
--
Glynn Clements <glynn.clements@virgin.net>
|
|
Sat, Apr 13 2002
14:27:05
|
|
Status changed to resolved by gclements
|
|