-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Search & New Mail Features - any open issues? #213
Comments
I apologize for the delay. I will be looking into this issue this week. Thanks for reporting it. |
The search failure might not be related to Vmail. The function Vmail generates logs in a file called vmail.log found inside If you tail the vmail.log contents while performing the search, the information will help us further debug this. |
@notalex - thanks alot, appreciate the reply. Will try to find time to return to this, and do some debugging. |
For the new email issue |
If you are using OSx, this hack might help: https://github.com/danchoi/vmail/wiki/Simple-Auto-Update-Without-VIM-Clientserver |
@arcseldon, may I close this ticket? |
@danchoi @notalex - Hi, thanks v.much for all the investment you guys made with
vmail
Set it up today and am mostly delighted.
Unfortunately there are 2 issues I'd really like to resolve.
1). Search is broken for me - or at least partly. When I do
,s
and then enter my search - and similarly when i first load vmail from command line startup, i see this appear in status window.2). No new mails arrive when I hit
u
in normal mode. It tells me it is checking for new emails in status window. If I exit and come back in, new messages are fetched.Particularly 1) is a pain as search. Any help much appreciated. Am technical, and happy to pair, share a screen, offer further information regarding versions etc etc to iron out the issues. Am slightly anxious as it appears vmail hasn't had so much ongoing maintenance of late. If you respond to this issue, then as i say happy to invest time in solving these problems. Thank you!
The text was updated successfully, but these errors were encountered: