top does not save settings
 

This is another little nuisance that I have noticed on this new amd64 laptop:

In an aterm I launch top. Then press z c and Shift+W. I get:

Wrote configuration to '/home/michael/.toprc'

Fine I think, Ctrl+c to end it and move on. Next time I fire up top, even
from the same terminal, it's all looking white with no colour, no
highlighting, or anything else. Why is this? This is what the contents of
.toprc show:
=================================
Cfile for "top with windows" # shameless braggin'
Id:a, Mode_altscr=0, Mode_irixps=1, Delay_time=3.000, Curwin=0
fieldscur=AEHIOQTWKNMbcdfgjplrsuvyzX
winflags=64953, sortindx=10, maxtasks=0
summclr=1, msgsclr=1, headclr=3, taskclr=1
fieldscur=ABcefgjlrstuvyzMKNHIWOPQDX
winflags=62777, sortindx=0, maxtasks=0
summclr=6, msgsclr=6, headclr=7, taskclr=6
fieldscur=ANOPQRSTUVbcdefgjlmyzWHIKX
winflags=62777, sortindx=13, maxtasks=0
summclr=5, msgsclr=5, headclr=4, taskclr=5
fieldscur=ABDECGfhijlopqrstuvyzMKNWX
winflags=62777, sortindx=4, maxtasks=0
summclr=3, msgsclr=3, headclr=2, taskclr=3
=================================

Same thing happens in xterm and konsole.
--
Regards,
Mick

top does not save settings
 

Mick writes:

> In an aterm I launch top. Then press z c and Shift+W. I get:
>
> Wrote configuration to '/home/michael/.toprc'

Cool. Didn't know about this yet.

> Fine I think, Ctrl+c to end it and move on. Next time I fire up top,
> even from the same terminal, it's all looking white with no colour, no
> highlighting, or anything else. Why is this? This is what the
> contents of .toprc show:
> =================================
> Cfile for "top with windows" # shameless braggin'
> Id:a, Mode_altscr=0, Mode_irixps=1, Delay_time=3.000, Curwin=0
> fieldscur=AEHIOQTWKNMbcdfgjplrsuvyzX
> winflags=64953, sortindx=10, maxtasks=0
> summclr=1, msgsclr=1, headclr=3, taskclr=1
> fieldscur=ABcefgjlrstuvyzMKNHIWOPQDX
> winflags=62777, sortindx=0, maxtasks=0
> summclr=6, msgsclr=6, headclr=7, taskclr=6
> fieldscur=ANOPQRSTUVbcdefgjlmyzWHIKX
> winflags=62777, sortindx=13, maxtasks=0
> summclr=5, msgsclr=5, headclr=4, taskclr=5
> fieldscur=ABDECGfhijlopqrstuvyzMKNWX
> winflags=62777, sortindx=4, maxtasks=0
> summclr=3, msgsclr=3, headclr=2, taskclr=3
> =================================
>
> Same thing happens in xterm and konsole.

Works here, in konsole and xterm.

My .toprc looks similar, but it has additional keywords Def, Job, Mem and
Usr. Are they missing in your .toprc, or did they get lost during
copy&paste? If I remove them, my top also looks like without .toprc.

=================================
RCfile for "top with windows" # shameless braggin'
Id:a, Mode_altscr=0, Mode_irixps=1, Delay_time=3.000, Curwin=0
Def fieldscur=AEHIOQTWKNMbcdfgjplrsuvyzX
winflags=64953, sortindx=10, maxtasks=0
summclr=1, msgsclr=1, headclr=3, taskclr=1
Job fieldscur=ABcefgjlrstuvyzMKNHIWOPQDX
winflags=62777, sortindx=0, maxtasks=0
summclr=6, msgsclr=6, headclr=7, taskclr=6
Mem fieldscur=ANOPQRSTUVbcdefgjlmyzWHIKX
winflags=62777, sortindx=13, maxtasks=0
summclr=5, msgsclr=5, headclr=4, taskclr=5
Usr fieldscur=ABDECGfhijlopqrstuvyzMKNWX
winflags=62777, sortindx=4, maxtasks=0
summclr=3, msgsclr=3, headclr=2, taskclr=3
=================================

Wonko

top does not save settings
 

Le Thursday 18 Mar 2010 à 12:06:12 (+0100), Alex Schuster a écrit :
> Mick writes:
>
> > In an aterm I launch top. Then press z c and Shift+W. I get:
> >
> > Wrote configuration to '/home/michael/.toprc'
>
> Cool. Didn't know about this yet.
>
> > Fine I think, Ctrl+c to end it and move on. Next time I fire up top,
> > even from the same terminal, it's all looking white with no colour, no
> > highlighting, or anything else. Why is this? This is what the
> > contents of .toprc show:
> > =================================
> > Cfile for "top with windows" # shameless braggin'
> > Id:a, Mode_altscr=0, Mode_irixps=1, Delay_time=3.000, Curwin=0
> > fieldscur=AEHIOQTWKNMbcdfgjplrsuvyzX
> > winflags=64953, sortindx=10, maxtasks=0
> > summclr=1, msgsclr=1, headclr=3, taskclr=1
> > fieldscur=ABcefgjlrstuvyzMKNHIWOPQDX
> > winflags=62777, sortindx=0, maxtasks=0
> > summclr=6, msgsclr=6, headclr=7, taskclr=6
> > fieldscur=ANOPQRSTUVbcdefgjlmyzWHIKX
> > winflags=62777, sortindx=13, maxtasks=0
> > summclr=5, msgsclr=5, headclr=4, taskclr=5
> > fieldscur=ABDECGfhijlopqrstuvyzMKNWX
> > winflags=62777, sortindx=4, maxtasks=0
> > summclr=3, msgsclr=3, headclr=2, taskclr=3
> > =================================
> >
> > Same thing happens in xterm and konsole.
>
Same thing here, nothing was highlighted and my .toprc looked like yours
I added Def, Job, Mem and usr in the file and it's fine now.
The question is why is the file not having the right syntax?
here:
top: procps version 3.2.8 on amd64



> Works here, in konsole and xterm.
>
> My .toprc looks similar, but it has additional keywords Def, Job, Mem and
> Usr. Are they missing in your .toprc, or did they get lost during
> copy&paste? If I remove them, my top also looks like without .toprc.
>
> =================================
> RCfile for "top with windows" # shameless braggin'
> Id:a, Mode_altscr=0, Mode_irixps=1, Delay_time=3.000, Curwin=0
> Def fieldscur=AEHIOQTWKNMbcdfgjplrsuvyzX
> winflags=64953, sortindx=10, maxtasks=0
> summclr=1, msgsclr=1, headclr=3, taskclr=1
> Job fieldscur=ABcefgjlrstuvyzMKNHIWOPQDX
> winflags=62777, sortindx=0, maxtasks=0
> summclr=6, msgsclr=6, headclr=7, taskclr=6
> Mem fieldscur=ANOPQRSTUVbcdefgjlmyzWHIKX
> winflags=62777, sortindx=13, maxtasks=0
> summclr=5, msgsclr=5, headclr=4, taskclr=5
> Usr fieldscur=ABDECGfhijlopqrstuvyzMKNWX
> winflags=62777, sortindx=4, maxtasks=0
> summclr=3, msgsclr=3, headclr=2, taskclr=3
> =================================
>
> Wonko
>

top does not save settings
 

o0o.atlantis.o0o@gmail.com writes:

> Same thing here, nothing was highlighted and my .toprc looked like
> yours I added Def, Job, Mem and usr in the file and it's fine now.
> The question is why is the file not having the right syntax?
> here:
> top: procps version 3.2.8 on amd64

I tried with sys-process/procps-3.2.7, sys-process/procps-3.2.8 and sys-
process/procps-3.2.8-r1 (all x86), all without the problem.

Wonko

top does not save settings
 

On Thu, 18 Mar 2010 13:06:20 +0100, Alex Schuster wrote:

> I tried with sys-process/procps-3.2.7, sys-process/procps-3.2.8 and sys-
> process/procps-3.2.8-r1 (all x86), all without the problem.

I had a similar problem in that I could save changes as a user but not
when logged in as root. In that case, I just copied the user's .toprc
to /root.


--
Neil Bothwick

"When you play a Microsoft CD backwards you can hear demonic Voices...
that's nothing - when you play it forward it installs Windows"

top does not save settings
 

Hi!

On Wed, 17 Mar 2010 23:19:34 +0000 Mick <michaelkintzios@gmail.com>
wrote:
> In an aterm I launch top. Then press z c and Shift+W. I get:
>
> Wrote configuration to '/home/michael/.toprc'
>
> Fine I think, Ctrl+c to end it and move on. Next time I fire up top,
> even from the same terminal, it's all looking white with no colour,
> no highlighting, or anything else. Why is this?

Maybe it will help if you quit from top gracefully by pressing 'q'
instead of killing it by sending a SIGTERM. I suppose top doesn't flush
the write buffer if you just kill it.


Cheers,
Renat

--
Probleme kann man niemals mit derselben Denkweise loesen,
durch die sie entstanden sind.
(Einstein)

top does not save settings
 

On Thursday 18 March 2010 14:07:37 Renat Golubchyk wrote:
> Hi!
>
> On Wed, 17 Mar 2010 23:19:34 +0000 Mick <michaelkintzios@gmail.com>
>
> wrote:
> > In an aterm I launch top. Then press z c and Shift+W. I get:
> >
> > Wrote configuration to '/home/michael/.toprc'
> >
> > Fine I think, Ctrl+c to end it and move on. Next time I fire up top,
> > even from the same terminal, it's all looking white with no colour,
> > no highlighting, or anything else. Why is this?
>
> Maybe it will help if you quit from top gracefully by pressing 'q'
> instead of killing it by sending a SIGTERM. I suppose top doesn't flush
> the write buffer if you just kill it.

Thank you all for your responses. Since I installed this amd64 system I have
found a couple of 'unexplained' behaviours compared to my x86 systems. This
must be one of them. However, some of you also run amd64 and you do not seem
to experience the same. This particular problem is rather weird. Why on
earth do these four missing keywords are not in my .toprc files? Neither in
my root or my plain user accounts. Even more weird is that I added these in
both .toprc files and as if by magic my changes in colour etc. showed up when
I relaunched top! Now, as soon as I made some more changes and pressed
Shift+W the Def, Job, Mem, Usr keywords disappeared again and all changes
were no longer visible.

What can be causing this? Should I report it as a bug?
--
Regards,
Mick