On Wed, Oct 31, 2007 at 04:18:24PM +0100, Frans Pop <[EMAIL PROTECTED]> was
heard to say:
> Package: aptitude
> Version: 0.4.6.1-1.1
> Severity: normal
>
> If I use aptitude in an SSH session to my s390 system (running in the
> Hercules emulator) and there is a dependency conflict that invokes the
> resolver, the bottom lines of the screen will look like this:
>
> [1(1)/...] Suggest 1 removal, 2 keeps
> : Examine : Apply : Next : Previous
>
> As you can see, the actual keys that need to be pressed for the resolver
> actions (e ! . ,) are missing. Otherwise the interface is fine; in the
> top menu bar (starting with C-T:) for example, the shortcut keys are
> displayed fine.
I think this patch should fix it. Can you try it out on the system
where you see a problem?
Thanks,
Daniel
diff -r 3764f15c3fb4 src/broken_indicator.cc
--- a/src/broken_indicator.cc Wed Oct 31 06:10:22 2007 -0700
+++ b/src/broken_indicator.cc Wed Oct 31 19:58:17 2007 -0700
@@ -115,7 +115,7 @@ private:
vector<fragment *> key_hints;
- key_hints.push_back(fragf(_("%s: Examine"),
+ key_hints.push_back(fragf(_("%ls: Examine"),
examine.c_str()));
@@ -123,15 +123,15 @@ private:
bool can_next = (state.selected_solution < state.generated_solutions &&
!(state.selected_solution + 1 == state.generated_solutions && state.solutions_exhausted));
- key_hints.push_back(style_fragment(fragf(_("%s: Apply"),
+ key_hints.push_back(style_fragment(fragf(_("%ls: Apply"),
apply.c_str()),
can_apply ? st_normal : st_disabled));
- key_hints.push_back(style_fragment(fragf(_("%s: Next"),
+ key_hints.push_back(style_fragment(fragf(_("%ls: Next"),
next.c_str()),
can_next ? st_normal : st_disabled));
bool can_prev = (state.selected_solution > 0);
- key_hints.push_back(style_fragment(fragf(_("%s: Previous"),
+ key_hints.push_back(style_fragment(fragf(_("%ls: Previous"),
prev.c_str()),
can_prev ? st_normal : st_disabled));
