Re: Release timelines and Unicode2 branch

Adrian Robert <[EMAIL PROTECTED]> writes: > On Sep 15, 2005, at 9:00 AM, Richard M. Stallman wrote: > >> That's correct -- or actually the GNUstep "version" and the OS X >> one >> are the same code, with a few ifdefs here and there. The APIs >> provided by GNUstep and Cocoa are almost

Re: (message (format "File %s" file))

> A *lot* of source code contains easy-to-miss bugs like this: > > (message (format "File: %s" file)) I guess one of the reasons of such bugs is the misleading argument name `string' of the function `message'. This name doesn't suggest that it is actually a format string used by the functio

Re: ispell.el doesn't work any more

> So how about the following patch, which fixes the case-fold issue, > improves the doc string, and extends the valid syntax for version > numbers? Your patch works for aspell version 0.60.3-20050121. I also suggest to add another quite common separator `+' to the set of separators `[-_]' in vers

check this

Want to find somebody to have se-x with right now? Find a female (or male) friend that just wants to f-uck! There are also a few who want a serious relationship though So if you want a long-termer, or a one-nighter, you got it ;) Whatever floats your boat pretty much! http://www.achucklehead.com

Re: Release timelines and Unicode2 branch

On Sep 15, 2005, at 9:00 AM, Richard M. Stallman wrote: That's correct -- or actually the GNUstep "version" and the OS X one are the same code, with a few ifdefs here and there. The APIs provided by GNUstep and Cocoa are almost identical (or at least largely overlapping; pleas

Re: Meta-data in source files

Perhaps, but it's surely useful to have that information in the files anyway; otherwise, how would someone know which version of a file they've got? They know what Emacs version it came from, and that is sufficient. ___ Emacs-devel mailing

Re: Bug in window resizing?

What is needed (I believe) is to go up one level in the split tree, find the window under the selected window and then resize this. Or maybe it is even more complicated than that? Yes, I think you are right. It seems that the only feasible way to fix this is to make a new interface.

Re: jit-lock refontifies too much

Are you going to install this patch? --- orig/lisp/font-lock.el +++ mod/lisp/font-lock.el @@ -1058,7 +1058,8 @@ 'font-lock-multiline nil) (point-max))) (goto-char end) - (setq end (line-beginning-position 2)) +

Re: 22.0.50 SEGFAULT

Just a followup for posterity: Kim Storm installed the following simple fix to dispnew.c, which has apparently solved this common (for me) glyph-related SEGFAULT. revision 1.354 date: 2005/08/16 14:58:16; author: kfstorm; state: Exp; lines: +3 -0 (increment_row_positions): Skip non-enabled row

Re: Meta-data in source files

Eric Hanchrow writes: >> "Emilio" == Emilio Lopes <[EMAIL PROTECTED]> writes: Emilio> Putting them in the source files causes spurious Emilio> conflicts > Other revision control systems don't have this problem -- notably > Subversion, which is designed specifical

Re: Meta-data in source files

Richard M Stallman writes: > Could we agree to refrain from storing meta-data in source > files? I'm referring here to things like "Time-stamp: ..." and > CVS' "$Id" and friends. > I have always preferred not to have such things in Emacs source > files. It is the people who wrote th

Re: rxvt.el fix

> rxvt.el lacks a definition for [end]. Done, thank you. Stefan ___ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-devel

Re: Recent changes to Calendar/Diary

>> I think it hides the actual problem. >> A `save-excursion' around `with-current-buffer' is just very weird. > Yup. >> What happens if you revert your patch and apply the one below instead? > My bug is gone, indeed. > I've reverted my change, please install this better patch instead. Done, t

Re: Argument names in Elisp Reference vs docstrings

[completions] doesn't quite fit for an alist, an obarray, or a hash table, or a function to test them. ... Regardless of whether the datatype is alist, obarray, hash table, or function, it represents an ordered set of completion candidates. True, but I do not think

Re: Recent changes to Calendar/Diary

Stefan Monnier <[EMAIL PROTECTED]> writes: > I think it hides the actual problem. > A `save-excursion' around `with-current-buffer' is just very weird. Yup. > What happens if you revert your patch and apply the one below instead? My bug is gone, indeed. I've reverted my change, please install

Re: Recent changes to Calendar/Diary

>> Hmm curious ... I'll take yet another look, > Note that I installed a change yesterday to that effect. I think it hides the actual problem. A `save-excursion' around `with-current-buffer' is just very weird. What happens if you revert your patch and apply the one below instead? S

RE: Argument names in Elisp Reference vs docstrings

[completions] doesn't quite fit for an alist, an obarray, or a hash table, or a function to test them. Unfortunately, `collection' does best. `completions' fails utterly. Moreover, is not the focus on the whole group, not on its individual elements, members, or items?

Re: Recent changes to Calendar/Diary

Stefan Monnier <[EMAIL PROTECTED]> writes: > Hmm curious ... I'll take yet another look, Note that I installed a change yesterday to that effect. -- Romain Francoise <[EMAIL PROTECTED]> | I've become someone else's it's a miracle -- http://orebokech.com/ | nightmare... ___

Re: Potential GC-related problems in compose_chars_in_text

> Actually, it often happens that things like ENABLE_CHECKING add assert > statements in the macro expansion which causes the args to be used more > than once. > As far as I can see, ENABLE_CHECKING has no such effect anywhere. It does. See the definition of XSET: #define XSET(var, t

Re: Recent changes to Calendar/Diary

>> The patch I just installed should have fixed it. > It doesn't, but reversing the order of with-current-buffer and > save-excursion in your new version of the function does. Hmm curious ... I'll take yet another look, Stefan ___ Emacs-

Re: a group as node of a tree widget

> > Is it possible to use a group widget as node of tree widget? > > > > As far as trying following code, a group widget is not handled well. > > You're right. Does it work better with this patch? > > Thanks for your report. Works fine. Thank you. Masatake __

I don't understand this comment on message2

I have studied the code in message2 and the functions called by it quite a lot (hunting for GC-related errors), and I don't understand the restrictions in the second paragraph of message2's commentary (included below). It is indeed not safe to pass data from a lisp string (due to potential GC), b

Re: a group as node of a tree widget

Hi Masatake, > Is it possible to use a group widget as node of tree widget? > > As far as trying following code, a group widget is not handled well. You're right. Does it work better with this patch? Thanks for your report. David 2005-09-19 David Ponce <[EMAIL PROTECTED]> * tree-

Re: Argument names in Elisp Reference vs docstrings

"Richard M. Stallman" <[EMAIL PROTECTED]> writes: > I don't have time to check the guidelines right now, but shouldn't a > boolean > argument's name end in "-p"? That is, wouldn't "must-match-p" be > conventional (and clearer)? > > No. The `-p' convention is for functions (predicates

Re: recentf bug

Hi Richard, > [I sent this message two weeks ago but did not get a response.] Sorry I forgot to reply. > > Can you fix this bug? I did some investigation on this bug but was not able to reproduce it on my version of Emacs: In GNU Emacs 22.0.50.1 (i686-pc-linux-gnu, GTK+ Version 2.4.14) of 20

a group as node of a tree widget

Is it possible to use a group widget as node of tree widget? As far as trying following code, a group widget is not handled well. (defun tree-test () (interactive) (switch-to-buffer "TREE-GROUP-NODE-TEST") (kill-all-local-variables) (let ((inhibit-read-only t)) (erase-buffer))