On 04/11/2018 04:20 PM, David C. Rankin wrote:
> It's ironic the configuration allowing the choice between the new/old
> interfaces isn't described clearly, or at all, in 'man top'. The Alternate
> Display 'A', has nothing whatsoever to do with whether modern top is display.
> From my read of the man page, neither an option concerning the modern top
> display, or its build flag are discussed at all.

Since I don't use top, I wouldn't know... if the modern-top definition
is not described there, you could, I dunno, *reproduce* it? By learning
how it works.

> In fact, the only reference to the build flag is on line 8633 of the 
> configure.ac:
> AC_ARG_ENABLE([modern-top],
>   AS_HELP_STRING([--disable-modern-top], [disable new startup defaults, return
> to original top]),
>   [], [enable_modern_top=yes]
> )
> The only changes (in source code - NEWS file) relevant to modern-top and
> config file, is that as of 3.3.5 modern-top will honor the old config file
> without having to --disable-modern-top, but this has nothing to do with the
> interface and there is no discussion whatsoever about configuring between the
> two interfaces.

It defines ORIG_TOPDEFS which gets used in places like

> Did I miss something obvious? Are you suggesting there is a simply toprc flag
> that allows choosing between old and new top interfaces?

I didn't suggest that, I suggested the new top interface could almost
certainly be reimplemented if you know the right top options... probably
by like reading documentation.

I consider top to be an exercise in frustration, so won't try myself,
but analyzing top.h as I referenced would probably let you do this. :)

Eli Schwartz
Bug Wrangler and Trusted User

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to