Re: Function "w32_abort" not defined
> From: Juri Linkov <[EMAIL PROTECTED]> > Cc: emacs-pretest-bug@gnu.org > Date: Sat, 24 Dec 2005 21:51:31 +0200 > > Usually I don't configure Emacs with --without-x, so I don't see a similar > message. I see it a lot. > It would be good to somehow suppress this message (by using some GDB option?). I tried very hard to find a way to do that, but failed. I'm open to suggestions. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: existing work on TODO items
> Well, it is another outliner, so it would need to include the basic > functionality of outlines. Are you saying that it could use > outline.el instead of duplicate it? That would indeed be cleaner--if > it is feasible. allout is backwards compatable with outline.el in that it supports outline.el's format, and provides similar navigation functionality. the reverse is not the case - outline.el cannot handle most common formatted outlines, I think we're having a miscommunication. The question is not whether allout.el provides features beyond outline.el. Clearly it does. The question is whether allout.el could be built "on top of" outline.el, to avoid redoing that basic outline functionality. I said I don't know whether this would be a good idea. i'll devote some attention to that. i'm reluctant to spend much energy changing to invisiblity and tuning that when i'm ultimately heading towards widgets. What does "heading towards widgets" mean? ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: query-replace-regexp and read-only text properties
> When I try it, it replaces both instances of `foo '. > Are you using the development Emacs? Yes: emacs-version "22.0.50.2". A few days old from HEAD. Strange. Can you debug what's happening inside the loop? ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Fwd: size of the slider bar
We've discussed this before and I've replied to the report below already. Yet I would like to forward it to this list so people know that users are complaining about this. Begin forwarded message: From: Bardia Sadri <[EMAIL PROTECTED]> Date: 24 December 2005 22:53:42 GMT+01:00 To: [EMAIL PROTECTED] Subject: [Aquamacs-bugs] size of the slider bar Symptoms: This is a bug every single version of emacs on Mac OS X suffers from. The length of the slider bar, the blue bar that slides inside the scroll bar track (I'm not sure about the terminology) changes randomly as you scroll up and down the text. I'm sure you know that the ratio of the length of this bar to the total length of the scroll bar must represent the ratio between the number of lines in the window to the number of lines in the file. So, the ratio, and therefore the length of this bar, must remain the same so long as neither the number of lines in the file nor the height of the window are changed. If emacs crashed, and you have the emacs process in the gdb debugger, please include the output from the following gdb commands: `bt full' and `xbacktrace'. If you would like to further debug the crash, please read the file /Applications/Aquamacs Emacs.app/Contents/Resources/etc/DEBUG for instructions. In GNU Emacs 22.0.50.1 (powerpc-apple-darwin7.9.0) of 2005-12-21 on rodrigues.inf.ed.ac.uk - Aquamacs Distribution 0.9.8 X server distributor `Apple Computers', version 10.4.3 configured using `configure '--without-x' '--prefix=/usr/local'' ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: existing work on TODO items
On 12/23/05, Richard M. Stallman <[EMAIL PROTECTED]> wrote: > Changes were installed for encryption in allout in some specific way, > using packages that aren't in Emacs rather than the support that is in > Emacs, perhaps with modifications. perhaps you're referring to my initial allout topic encryption changes, which used facilities from crypt++ and mailcrypt? someone suggested using pgg instead, and started some changes there (to implement symmetric-key encryption) which would enable me to do so. i refined their pgg changes, added some general pgg fixes, and switched over allout's new encryption to use the modified pgg. it's all checked in to the gnu repository, and comes with the head emacs 22 checkout. > Could you please be more specific? I never knew all that much about > allout. All I know is that it does a more powerful kind of outlining. > > Oh, I see allout.el was changed to use pgg.el, which was also used by > Gnus. Is that the change you are criticizing? > > Allout isn't actually documented i have no texinfo documentation for allout. there are a lot of instructions and other information in the docstrings, eg the one for allout-mode, but no cohesive user guide. > and appears to duplicate the standard outline functionality except > with the obsolete selective display method of ooutline.el. if you are saying that allout provides no more functionality than outline.el, you are mistaken. as far as i can see, outline.el provides only for navigating outlines. allout provides for topic-oriented authoring and editing, including topic creation, cohesive topic/subtopic promotion, demotion, and structured cut and paste across varying depths. it also provides dynamic exposure and reconcealment of hidden items during isearch, customizable topic prefix strings, topic encryption, and much more. you are right that it still uses the old selective display mechanism. i recently received a suggestion to use invisibility, instead (with some example code) and am consider switching over to that. i am more interested in switching over to hierarchical widgets (something derived from the tree widget), and am actively working on a long-term project along those lines, using allout format as the external representation. i don't expect to have releasable code for that for a while, though. > Well, it is another outliner, so it would need to include the basic > functionality of outlines. Are you saying that it could use > outline.el instead of duplicate it? That would indeed be cleaner--if > it is feasible. allout is backwards compatable with outline.el in that it supports outline.el's format, and provides similar navigation functionality. the reverse is not the case - outline.el cannot handle most common formatted outlines, much less custom ones, outline.el lacks some of allout's navigation features (eg, hotspot navigation), and completely lacks (as far as i can tell) the outline authoring and editing features. > It would be good to make that change, after the release--if it really > results in an improvement. Sometimes duplicating code makes > maintenance harder, and sometimes it makes maintenance easier. > > allout was initially installed in 1993, which was before the old > outline.el became ooutline.el. Thus, what happened was that we > updated outline.el to use overlays but didn't update allout.el. > > It would be good to make that change, after the release. i'll devote some attention to that. i'm reluctant to spend much energy changing to invisiblity and tuning that when i'm ultimately heading towards widgets. ken manheimer [EMAIL PROTECTED] ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: describe-char
>> It is called before the old contents of the help buffer is replaced with >> the output of `describe-char'. This is necessary to record the previous >> position of point. But since at this moment the help buffer doesn't contain >> the new output of `describe-char', we should use nil for the first >> argument `item' of the function `help-setup-xref' here, and should set >> `help-xref-stack-item' explicitly later when the help buffer is ready. > > AFAICT it's the exact same situation as in all other cases, except that you > use (buffer-string). All other cases call `help-setup-xref' with the same function name and its arguments just before calling `(with-output-to-temp-buffer (help-buffer) ...)' and replacing old contents of the help buffer with the new contents. But this is not possible when the new contents should be stored in the help xref stack. > Instead of using (help-insert-string (buffer-string)) I'd use > (describe-char pos buf), which admittedly forces you to add a `buf' > optional argument. This is not reliable way to restore the old output of `describe-char' since the original buffer might be killed or the character at the old position might be deleted, and also this won't work when `describe-char' was called on a character in the help buffer itself. -- Juri Linkov http://www.jurta.org/emacs/ ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Function "w32_abort" not defined
>> What is the purpose of the error message: >> >> Function "w32_abort" not defined. >> >> printed when Emacs is started under GDB on GNU/Linux? > > There's no _purpose_ to it, it's a _consequence_ of GDB trying to set > a breakpoint on a function that doesn't exist in the GNU/Linux binary. > Don't you see a similar message for x_error_quitter if you configure > and build Emacs --without-x? Usually I don't configure Emacs with --without-x, so I don't see a similar message. So a new error message about w32_abort is slightly distracting. It would be good to somehow suppress this message (by using some GDB option?). -- Juri Linkov http://www.jurta.org/emacs/ ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: font-lock-add-keywords in hi-lock.el
> I just did another update this morning and now the highlighting goes > away in Gnus buffers even faster than before (or I just got lucky with > what I was doing). I managed to reproduce it twice already this morning. > When this happens, I also notice that the highlighting is also broken in > *Help* buffers. > > I think it was last week where I didn't observe this behavior at all. > Hard to say if I got lucky, or whether there was a good change a week > before that and a bad change this week. But it's what I observed. > > Sorry, this is so sporadic that I haven't been able to generate a recipe > to reproduce it yet. Do you use Hi-Lock (either by putting global-hi-lock-mode in .emacs or by using highlight-regexp or other hi-lock functions)? -- Juri Linkov http://www.jurta.org/emacs/ ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: describe-char
>>> + (setq help-xref-stack-item (list 'help-insert-string (buffer-string))) >> >> This is wrong. There are functions like help-setup-xref to do this job. > The function help-setup-xref is already used in describe-char as > (help-setup-xref nil (interactive-p)) > It is called before the old contents of the help buffer is replaced with > the output of `describe-char'. This is necessary to record the previous > position of point. But since at this moment the help buffer doesn't contain > the new output of `describe-char', we should use nil for the first > argument `item' of the function `help-setup-xref' here, and should set > `help-xref-stack-item' explicitly later when the help buffer is ready. AFAICT it's the exact same situation as in all other cases, except that you use (buffer-string). Instead of using (help-insert-string (buffer-string)) I'd use (describe-char pos buf), which admittedly forces you to add a `buf' optional argument. > Unless you propose a better solution, I will add a comment. Thanks, Stefan ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: Function "w32_abort" not defined
What is the purpose of the error message: Function "w32_abort" not defined. printed when Emacs is started under GDB on GNU/Linux? It has no purpose, it happens because the command `b w32_abort' gets an error. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: loaddefs.el on Windows incomplete
> From: Ralf Angeli <[EMAIL PROTECTED]> > Cc: emacs-pretest-bug@gnu.org > Date: Mon, 19 Dec 2005 12:23:37 +0100 > > > Is there any reasonable chance that MSYS maintainers will fix this? > > Could you check with them, or maybe try their latest snapshot of > > ported Bash and see if the problem went away? > > I reported the issue back in July, see > http://thread.gmane.org/[EMAIL PROTECTED]>. > So they are aware of it but I don't know if this is fixed yet. I've > been waiting for ages for a new release of MSYS. IIRC I checked a > beta version of Bash 2.05 for MSYS back in July which did not solve > the problem. Unfortunately I cannot find that beta on their download > page anymore for testing. And the last beta of MSYS itself is from > April 2004. > > > If they don't intend to fix that any time soon, we will need to find a > > much simpler solution, one for which we could know with high > > probability that it will not break anything else. I'll give it a > > thought while you talk to the MSYS people. > > Well, I am. (c: I installed a change that should fix this problem for you. Can you sync with the repository and see if autoloads now work even with MSYS munging of the command line? ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: query-replace-regexp and read-only text properties
On Fri, 23 Dec 2005 21:36:59 -0500 Richard M. Stallman wrote: > When I try it, it replaces both instances of `foo '. > Are you using the development Emacs? Yes: emacs-version "22.0.50.2". A few days old from HEAD. David ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
