Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 156422
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Fabian Groffen <grobian@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Matus UHLAR - fantomas <uhlar@fantomas.sk>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 156422 depends on: Show dependency tree
Bug 156422 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2006-11-27 09:28 0000 
the /etc/csh.login contains this line:

    if ( -x "`which tset`" ) tset -I -Q

it causes tset ask for the correct terminal type, but does not set it
according to tset manpage, it should look like:

    if ( -x "`which tset`" ) eval `tset -I -Q`

------- Comment #1 From Fabian Groffen 2006-11-27 13:33:46 0000 ------- 
hmmm... I can't find anything about that.  The command doesn't output anything
for me either.

------- Comment #2 From Matus UHLAR - fantomas 2006-11-27 13:40:49 0000 ------- 
Oops!
eval `tset -Q -I -s`
should do the trick

------- Comment #3 From Fabian Groffen 2006-12-02 06:04:23 0000 ------- 
Fixed in revision -r4 now.  Including your comment on setting SHELL.

Thanks!

------- Comment #4 From Matus UHLAR - fantomas 2006-12-05 06:15:09 0000 ------- 
Thank you.
btw, it would be nice if user could handle this (terminal setting) itself. This
requires either indication that user will take care of it himself, or even move
this section to skeleton .login file.

------- Comment #5 From Fabian Groffen 2006-12-05 06:21:32 0000 ------- 
well, I was wondering while changing it, what it is supposed to do.  Because it
only sets the TERM variable, which is already set by the terminal.  And if not,
the if-block just makes it term=linux.  So maybe the whole tset thing should
go?

------- Comment #6 From Matus UHLAR - fantomas 2006-12-05 06:37:08 0000 ------- 
it asks for terminal type if the current $TERM is not recognized by the system.
(I have currently problems with xterm-debian, which was already supported by
ncurses, but is not now, see bug 18486)

I use to set up xterm-color automatically in such case in my .login, but the
system-wide csh.login still asks me for this, because it's run before the one
in ~

------- Comment #7 From Fabian Groffen 2006-12-05 06:59:04 0000 ------- 
what?!? that tool is interactive?!?  Ok, it's completely out as that is not
acceptable for sure.  If you want to do it, you have to do it yourself. 
Thanks!

------- Comment #8 From Matus UHLAR - fantomas 2006-12-05 07:04:28 0000 ------- 
I don't think it's THAT bad, as long as it is in the .login file, which is only
invoked when the shell is executed as login shell (which is expected to be
interactive).
However, do as you decide :)
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug