Re: [Evolution] has the "go to next unread message" function changed?

On Sat, 2005-01-08 at 18:56 +0100, guenther wrote:
Before upgrading from evo 1.4.6 to 2.0.3 I could:
A: press shift+. to go to the next unread message,
B: press ctrl+h to select a thread,
C: press ctrl+k to mark it as read and finally
D: press shift+. to go to next unread message.

Now in evo 2.0.3 A through C work fine [1] but D doesn't work any more.
Whenever a thread is selected "go to next unread message" appears to be
ignored. Neither the keyboard shortcut nor the menu-option work. 
Doesn't work for me either. After "Select Thread", "Go To / Next Unread
Messages" doesn't work. Neither accelerator, nor menu item.

This actually is cause by Select Thread. Selecting multiple messages
manually (even if it is the entire thread) and going to the next unread
message does work fine.

Please file a bug report in, Component
Evolution, Mailer.

Done bug # 71107 (

[1] although I now have to press Ctrl+Alt Gr+ $ (Alt Gr + $ gives the
right bracket "]" 

Well the dot "." works for me, just like it always did. I never tried
Shift-dot, and the bracket by far isn't accessible as easily on German

Sorry I used inconsistent symbols there. I have a Belgian keyboard
(XkbModel: pc105, XkbLayout: be)
The "." is on the same button as the ";", so I have to press shift + ";"
to get a "." So in the above A should have been:
A: press shift+; to go to the next unread message,

However the dot (i.e. shift + ;) doesn't work on this system any more,
the "," still goes back to the *previous* unread message like it used to
but ";" or "." does nothing any more. I would like to be able to use
some more convenient keys as accelerator but I have been reluctant to
edit the xml files in /usr/share/evolution/2.0/ui/.

Actually after
checking /usr/share/evolution/2.0/ui/evolution-mail-message.xml I see I
was wrong twice: the accelerator isn't Ctrl + bracketright but simply

According to this file "period" should work as accelerator for
MailNextUnread but I can't seem to get it to work. I tested with xev to
see if the button was being reported as "period" and it is. Any idea
what I might have screwed up?

With Num Lock off the "Del" button on the numeric keypad works as
expected: the selected message is marked for deletion. With Num Lock on
the button doesn't work even though I assume it should also work as the
"period" accelerator.

Is there a way to debug this? I always start evo from a little script
which I'll include below but the logfile doesn't shows any

--- startevodebug script ---

#echo "" >> $LOGFILE
echo -e "\n---\nDEBUG OUTPUT\n\n--- $(date +"%R %A, %B %-d, %Y") ---" >>
CAMEL_VERBOSE_DEBUG=1 evolution >> $LOGFILE 2>&1
--- end script ---


Selecting another mail (after step C) by arrow up/down, makes the
accelerator to go to the Next Unread Message work again.

Thanks, I figured this out already and should have mentioned it in my
post. I added it to the bug report for future reference.


# Mertens Bram "M8ram"   <bram-mertens linux be>   Linux User #349737 #
# debian testing            kernel 2.6.8-1-686     i686     512MB RAM #
# 19:44:30 up 3 days,  6:47,  8 users,  load average: 0.19, 0.32, 0.36 #

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]