26266 – multi-aterm's "-tn" option doesn't work (doesn't do anything?)

Bug 26266 - multi-aterm's "-tn" option doesn't work (doesn't do anything?)

Summary: multi-aterm's "-tn" option doesn't work (doesn't do anything?)

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	High normal
Assignee:	Masatomo Nakano (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2003-08-09 07:12 UTC by Shahar Goldin
Modified:	2003-10-23 20:07 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Shahar Goldin 2003-08-09 07:12:40 UTC

after emerging 'x11-shells/multi-aterm" I quickly became irritated with having
to set the terminal type to 'xterm' every time I ran it. Hence I was pleased
when I discovered the -tn option (multi-aterm -help)     -tn string            
           value of the TERM environment variable


except it doesn't do anything... running multi-aterm -tn xterm maintains the
TERM as 'dumb' which causes many things to not function or not function properly.

Reproducible: Always
Steps to Reproduce:
1.emerge multi-aterm
2.run 'multi-aterm -tn xterm'
3.in the new multi-aterm, 'echo $TERM'

Actual Results:  
bash-2.05b$ echo $TERM       
dumb


Expected Results:  
bash-2.05b$ echo $TERM
xterm

(this is the result of manually running 'export TERM=xterm')


I believe this is a bug in multi-aterm which should be passed on to the upstream
developers, re the Gentoo Social Contract

Comment 1 Shahar Goldin 2003-10-23 20:07:35 UTC

fixed in latest version (0.0.5)
(closing)