Thanks for these suggestions. Would you like to read a chapter or two straight through to notice things that we haven't changed that are obsolete? That is really important.
FYI. I am reading currently the following two chapters of the actual emacs cvs manual (co on 2002-09-06): - Fundamental Editing Commands - Important Text-Changing Commands I will send my results as b
Sorry about that. It's a bit of a mess and badly needed testing properly. I don't understand some of these straight off, but I don't have time to look at it now. I don't think it should be toggled; i
Safer I don't know (though I suspect it doesn't really make all that much difference), but easier? Modifying a buffer is _far_ more straight-forward than using display-modification properties (becaus
I don't think we want to make MORE branches. If it is not judged safe enough to go in 21.4, then it should go straight into the unicode branch IMO. We clearly don't have enough resources to keep two
As far as I have checked, this double correction occurs just with PNG since it is apparently just the PNG library that offers gamma correction straight from inside the library. The whole lookup busin
OK. Here's the combined patch from yours 1-6 and the stuff from patch 7 that's supposedly trouble-free (adding the cygwin system-type to the docs, the etc/NEWS entry and some ChangeLog changes, a few
Ah, thank you! That explains the strange behaviour I noticed after I applied my patch, and is fixed by adjusting buf_charpos in increment_row_positions. But... Oops, I didn't know about string_buffer
OK. After thinking about it a bit more, I agree. You're absolutely right that a run-time setting would be better. However, part of the problem is that this policy is currently handled by the external
OK. After thinking about it a bit more, I agree. You're absolutely right that a run-time setting would be better. However, part of the problem is that this policy is currently handled by the external
commence Stefan Monnier quotation: Just a thought: Matt doesn't say much about the conditions under which the test was done. For example, if the machine was freshly booted, and the 21.2 test run was
Colin told me that making Ibuffer the default was contingent upon it taking less space or consing less. Ibuffer does use the header-line, but for displaying what filters (not filter groups) are activ
Yeah, given the popularity of using it for showing aligned stuff, there definitively should at least be an option for the header-line to start exactly at the text's left edge. This could even be some
Agreed. BTW, I suspect that the `spaces' calculation should ideally be enhanced to take into account window margins rather than only scrollbars and fringes.... clearly this is a nightmare and should
This patch solves a problem with determining the font width in a platform independent manner, causing a build from cvs on a non-X platform to fail. The fix should be straight-forward: use the FRAME_F
[Test using Emacs-21.2.95.1.] The variable `after-init-hook' is useful for packages where part of the initialization has to be performed very late, e.g., to ensure the correct order of functions in a
I noticed something strange with C-l while playing around with the native scrollbar code. It has no connection with the scrollbar, however. First of all is the behavior reproducible? I got rid of all
If you want to do splitting on the message contents as well, the documentation contains the following suggestion: (defun split-on-body () (save-excursion (set-buffer " *nnmail incoming*") (goto-char
Because it's much more confusing? `concrete bindings' are not only very cryptic as names, but by mixing concepts like that, you provide lots of room for confusion about what's going on. If I were des
They are documented in the Emacs manual, where the commands are documented. I'm not against putting them in the Lisp manual, but is there a place where they would fit? The evaluation commands are not