Summary: | pinentry messes up mutt and vim input and display. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Abraham Smith <adsmith> |
Component: | Current packages | Assignee: | Crypto team [DISABLED] <crypto+disabled> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | devnull, gentoo, net-mail+disabled |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Abraham Smith
2006-01-17 17:07:12 UTC
The patch mentioned in the thread has never been integrated by upstream into mutt. Okay, I just tried their patch by hand in mutt-1.5.11, by just commenting out the "if" and the brackets. It appears to work for mutt on its own: Line 71 of curs_lib.c // if (!getenv ("DISPLAY")) // { keypad (stdscr, TRUE); clearok (stdscr, TRUE); set_option (OPTNEEDREDRAW); // } However, this problem still occurs within GNU/screen. Any thoughts on how to patch it there? I guess the best solution is to track down the problem in pinentry itself instead of every program it shares a terminal with... Not really sure this is a vim-specific problem. Feel free to re-add us to the CC if it ends up seeming that way. I don't have time to look into this at present, but an ugly workaround when in GNU screen is to just pretend you're not. e.g. in my .bashrc I have the following line: alias mutt="TERM=rxvt-unicode; mutt" Hi, Please take this to upstream. It is not Gentoo specific issue. Thanks. |