JS <[EMAIL PROTECTED]> writes: > Could you be a bit more specific > I have no idea how to fix the problem.
one way is to figure out how to fix the problem generally, then apply those techniques to this problem. debugging your ~/.emacs is like debugging anything else that accumulates past a threshold of desirable behavior: revert to pristine and add piecemeal until the threshold is met. that which you have added last is where you then focus your attention. (unlike "the solution to bad speech is more speech", the solution to bad ~/.emacs is usually not more ~/.emacs.) this paring down phase (described above) can be done in various ways, but is important because focus is critical for the next phase: application of the Scientific Method, the bull-dozer of all problem solvers (according to Pirsig). applying the scientific method doesn't mean you have to give up the superstitious method (i.e., casting strange spells and muttering arcane incantations), which is your current approach, from what i've gathered skimming this thread. however, if you can place the superstition on hold for a bit, it may come back and delight you later as some kind of aesthetically pleasing spiritual tinge accompanying the muscle-memory of practice. (or perhaps not -- ymmv.) anyway, good luck w/ your quest for commenting! thi _______________________________________________ Help-gnu-emacs mailing list Help-gnu-emacs@gnu.org http://lists.gnu.org/mailman/listinfo/help-gnu-emacs