alpine 2.0; problem with role selection (#)
Erik Quaeghebeur
I just noticed that role selection with # for replying does not work
anymore for me with my build of alpine 2.0: I get the action (reply,
bounce,...) and role selection menus, but the actual composition still has
the same role as it would without the #, i.e., the default one or the
mailbox specific one.
Has anyone else encountered this?
I consider it possible that it has to do with my local config/build
(gentoo bugzilla ebuild with all-chappa and perhaps some other patches),
but this is the first place to check.
Erik
Chris Game
> Has anyone else encountered this?
It works pretty much as advertised in PC-alpine; I think the screens
come up in the wrong order though, I would expect the 'choose role'
screen to come next when I press '#' instead the 'Reply, Forward or
Bounce?' message comes up as the next action. And the filter to
always use a certain role when in a certain message folder doesn't
work.
--
Chris Game
"There is much pleasure to be gained in useless knowledge."
-- Bertrand Russell
Erik Quaeghebeur
>
> It works pretty much as advertised in PC-alpine; I think the screens
> come up in the wrong order though, I would expect the 'choose role'
> screen to come next when I press '#' instead the 'Reply, Forward or
> Bounce?' message comes up as the next action.
That order is typical as far as I know.
> And the filter to always use a certain role when in a certain message
> folder doesn't work.
Strange, it does for me (unix alpine though...).
Erik
Chris Game
>> It works pretty much as advertised in PC-alpine; I think the
>> screens come up in the wrong order though, I would expect the
>> 'choose role' screen to come next when I press '#' instead the
>> 'Reply, Forward or Bounce?' message comes up as the next action.
>
> That order is typical as far as I know.
It doesn't seem right, intuitively.
--
Chris Game
"It's not a good idea to look too hard at the words, they
resent it." -- T. Pratchet, "Mort".
cha...@washington.edu
Hi Erik,
This is a bug in all.patch, but it was fixed a few weeks ago. If
this is happening with the latest version (as of today) please let me
know and I will take a look at it again. I am sorry for the
inconvenience.
Thank you