Bug 130517 - top -bn1 no longer ignores $TERM
Summary: top -bn1 no longer ignores $TERM
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: procps
Version: 2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Karel Zak
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-08-20 23:04 UTC by Jamie Zawinski
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-06-27 15:07:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jamie Zawinski 2004-08-20 23:04:34 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)
Gecko/20040803

Description of problem:
"top -bn1" should produce plain-text output and exit.  It does not
address the screen, and so should not consult $TERM.  In 2.0.11, it
did not, but in 3.2.0 it does.

With procps-2.0.11-6 on Red Hat 9:

     % setenv TERM no-such-terminal-type
     % top -bn1 | head
       (works)

With procps-3.2.0-1.1 on Fedora Core 2:

     % setenv TERM no-such-terminal-type
     % top -bn1 | head
     'no-such-terminal-type': unknown terminal type.

     % setenv TERM dumb
     % top -bn1 | head
       (works)

So, even though top does not make use of the terminal entry, it
insists on there being one anyway.

This is a problem because Emacs *shell* buffers set $TERM to "emacs",
which has no termcap entry, so when I do top-ish grep-ish things in
Emacs, I have to screw around with $TERM to make it work.

Version-Release number of selected component (if applicable):
procps-3.2.0-1.1

How reproducible:
Always

Expected Results:
"top -bn1" should work the same regardless of the $TERM setting.

Comment 1 Daniel Walsh 2004-08-30 20:04:19 UTC
Fixed in procps-3.2.3-3



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