Indenting Warnings for readability?

[eternaleye@…]

I just started using paludis, and right away I saw this kind of output (--log-level warn):

Query error:

• In program paludis -pi world:
• When performing install action from command line:
• When executing install task:
• When adding PackageDepAtom? 'x11-themes/emerald-themes':
• When adding package 'x11-themes/emerald-themes-0.1.9999.1::xeffects':
• When adding build dependencies as pre dependencies:
• When adding PackageDepAtom? '~x11-wm/emerald-0.1.9999.1':
• When adding package 'x11-wm/emerald-0.1.9999.1::xeffects':
• When adding build dependencies as pre dependencies:
• When adding PackageDepAtom? '~x11-wm/beryl-core-0.1.9999.1':
• When adding package 'x11-wm/beryl-core-0.1.9999.1::xeffects':
• When adding post dependencies as post dependencies:
• When adding PackageDepAtom? '~x11-plugins/beryl-plugins-0.1.9999.1':
• When adding package 'x11-plugins/beryl-plugins-0.1.9999.1::xeffects':
• When adding post dependencies as post dependencies:
• When adding PackageDepAtom? '~x11-plugins/beryl-plugins-vidcap-0.1.9999.1':
• All versions of '~x11-plugins/beryl-plugins-vidcap-0.1.9999.1' are masked. Candidates are:
  • x11-plugins/beryl-plugins-vidcap-0.1.9999.1::xeffects: Masked by keyword ( ~amd64 ~ppc ~ppc64 ~x86 )

Is there any chance we could leave the "what I was doing" line where it is, and move the "What I was doing it to" line in a few spaces for readability? Example:

Query error:

• In program paludis -pi world:
• When performing install action from command line:
• When executing install task:
  • When adding PackageDepAtom? 'x11-themes/emerald-themes':
  • When adding package 'x11-themes/emerald-themes-0.1.9999.1::xeffects':
• When adding build dependencies as pre dependencies:
  • When adding PackageDepAtom? '~x11-wm/emerald-0.1.9999.1':
  • When adding package 'x11-wm/emerald-0.1.9999.1::xeffects':
• When adding build dependencies as pre dependencies:
  • When adding PackageDepAtom? '~x11-wm/beryl-core-0.1.9999.1':
  • When adding package 'x11-wm/beryl-core-0.1.9999.1::xeffects':
• When adding post dependencies as post dependencies:
  • When adding PackageDepAtom? '~x11-plugins/beryl-plugins-0.1.9999.1':
  • When adding package 'x11-plugins/beryl-plugins-0.1.9999.1::xeffects':
• When adding post dependencies as post dependencies:
  • When adding PackageDepAtom? '~x11-plugins/beryl-plugins-vidcap-0.1.9999.1':
  • All versions of '~x11-plugins/beryl-plugins-vidcap-0.1.9999.1' are masked. Candidates are:
• x11-plugins/beryl-plugins-vidcap-0.1.9999.1::xeffects: Masked by keyword ( ~amd64 ~ppc ~ppc64 ~x86 )

Tad bit clearer, no?

[eternaleye@…]

Forgot to put my email.

[ciaranm]

Hrm. Thing is... There're multiple code paths that can be used to reach all of those points. I'm not sure that there's a way of differentiating between the two types of context entries that makes sense in the general case.