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.

Sign up for GitHub

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

Jump to bottom

sidebar and S/MIME interfere with each other #29

Closed

RichiH opened this issue May 23, 2016 · 4 comments

Assignees

Labels

type:bug

RichiH commented May 23, 2016 •

edited by flatcap

I never used sidebar before, but I gave it a try, now.

When signing email in the compose view, sidebar and signature key info are rendered upon each other.

Unsigned:

xxx@xxxxx.x972/1100|    Security: None
xxx@xxxxx.xxx/INBO0|

Signed:

xxx@xxxxx.x972/1100|    Security: Sign (S/MIME)
xxx@ sign as: b4f63045.0

The text was updated successfully, but these errors were encountered:

RichiH mentioned this issue

Debian's patches #23

Closed

flatcap added the bug label

flatcap self-assigned this

Member

flatcap commented May 23, 2016

Hmm, I'd thought I'd got all of those.
I can't repeat your problem in my latest version of Sidebar -- I'm confident it's already fixed.
I'm planning another release very soon. I'll leave this issue open until you can test that.

Author

RichiH commented May 23, 2016

I'll leave this issue open until you can test that.

Sounds good; thanks :)

Member

flatcap commented May 26, 2016

Whilst rebuilding the master patchset, I found out why you see a bug and I don't.
The fix got put into my bug-fix branch. It should have been in Sidebar as well.

Member

flatcap commented May 30, 2016

The new release: NeoMutt-20160530 should fix this problem.
The patch is in both NeoMutt and the separate Sidebar patch.

flatcap closed this as completed

guyzmo added type:bug and removed status:new-bug labels

JonJFineman mentioned this issue

notmuch query #4055

Closed

szaszg mentioned this issue

neomutt freeze (IMAP config) #4197

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment