When I byte-compile certain code, the results are different than when it's not byte-compiled. It seems to wrongly merge lists. The one unusual thing I was doing with the code is using a macro to gene
Your message dated Sat, 02 Jan 2010 19:38:20 +0200 with message-id <83eim8e7ar.fsf@gnu.org> and subject line Re: 23.1; two common doc strings too wide - shows up in most uses of `C-h m' has caused th
Processing commands for control@emacsbugs.donarmstrong.com: Stopping processing here. Please contact me if you need assistance. Don Armstrong (administrator, Emacs bugs database)
What do you mean by "stop on EOB"? If end of the buffer is the newline immediately following the last line of non-newline chars, then how can showing up to a screenful of blank vertical space be con
No, that's not what I see. The last line can be scrolled completely off of the screen, so all that can be seen is blank space. And yes, I do see the same thing in Emacs 22.3. But *not* in Emacs 21.3
The doc strings of the following variables are not formatted correctly. Their longest lines have these many chars (all are > 80): * byte-catch: 85 chars * byte-constant2: 86 * byte-save-restriction:
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the bug report if necessary, and/or fix the problem forthwith. (NB: If
This change: * faces.el (set-face-attribute): Set family and foundry before other attributes. (face-spec-set-2): Pass unmodified args to set-face-attribute. breaks a face definition I have been using
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the bug report if necessary, and/or fix the problem forthwith. (NB: If
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the bug report if necessary, and/or fix the problem forthwith. (NB: If
i am not sure how to proceed with this problem. as demonstrated by the pggprob.el script, i consistently get encryption and decryption problems without the contrived delay in my pgg-gpg-process-regio
allout encryption, which depends on pgg.el &c, has been failing due to a weird timing problem i've narrowed down to the pgg-gpg-process-region function. this is in emacs 23.0.60 built from a CVS HEAD
Yep. It's OK if the function name says to do something with a hook (e.g. `add-hook', `mmm-run-major-mode-hook'), but I don't see it as appropriate for many of those you cited. Just one opinion, of c