21 May 2011 16:50
[ mh-e-Bugs-3305567 ] can't "q" after "Fu"
SourceForge.net <noreply <at> sourceforge.net>
2011-05-21 14:50:16 GMT
2011-05-21 14:50:16 GMT
Bugs item #3305567, was opened at 2011-05-21 07:48 Message generated for change (Comment added) made by minshall You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113357&aid=3305567&group_id=13357 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General Group: None Status: Open Resolution: None >Priority: 3 Private: No Submitted By: minshall (minshall) Assigned to: Nobody/Anonymous (nobody) Summary: can't "q" after "Fu" Initial Comment: if i "emacs -q" (no init file), then "Fr" (to give me a message to play with), then "o" (to move that message to a folder), then (THIS IS KEY) "Fu" and reply "yes" (to undo all pending changes in the current folder), then, if i say "q", i get "mh-quit: Wrong type argument: consp, nil" (after colon in minibuffer; full message in *Messages*). ---------------------------------------------------------------------- >Comment By: minshall (minshall) Date: 2011-05-21 07:50 Message: here's (what i assume to be) a backtrace: ---- Debugger entered--Lisp error: (wrong-type-argument consp nil) mh-update-sequences() mh-quit() call-interactively(mh-quit) mh-show-quit() call-interactively(mh-show-quit nil nil) ---- ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=113357&aid=3305567&group_id=13357 ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay
RSS Feed