Hi, EZ> To answer that, we need someone with good knowledge of both the EZ> requirements of the Emacs display engine and of the features and EZ> possibilities of the Gnome Canvas library. Do we have
Wow, that's some pretty easy, straight-forward code. ;-) It looks to me that I could copy the `completion-pcm-all-completions' function and add a FILTER for deleting the entries consisting of too man
I don't find that persuasive. Before I scrolled to see this part I was already thinking "=" is unmodified, "*" is fine for modified since that's what it means for buffers. If you think that the Emacs
Is something like (if (char-displayable-p ?≠) "≠" "#") going to work reliably? However, I am not sure I consider it appropriate since equality is not the same as being unmodified. -- David Kastru
Just to set the record straight: The MS-DOS build has its own version of `select', see msdos.c:sys_select. I guess by "does not need it" you meant that the DOS build does not support networking and
So for what we use the revision information? How it helps to know which was the last commit from trunk included on a build? What's the use case? AFAIU the info is for knowing the source code used for
It relates his code to the one in our repository, i.e. to something about which we know something. When he reports a bug that's supposedly been fixed recently, we can know whether his report is beca
That looks right, yes, except for a missing "bzr merge ../work" before the last commit. Yes. Indeed. Note that the steps you describe above are the normal steps to do a merge (except they go through
Sure. Compiling to native code will probably yield some benefits, but I think we tend to overestimate the benefits. To take a random example from code I just wrote (part of `gnus-range-nconcat'), whi
Actually, in this case it might be faster, since there are special opcodes like Bcar, Bcons, Bsetcar, etc. Whether it is "faster enough" is hard to guess; lexbind comes into play because with lexbin
I know. I could get my old sources of generational garbage collector, to work. However it is a daunting job (the worse I could imagine, garbage collectors are nasty), plugging and debugging a new gar
It is always ok to ask for help. The current collector is very simple to understand. If you read alloc.c, and look through the data structures representing lisp objects (in lisp.h), you will have a
Thanks, I will keep in mind it. It's open already :). Yep, we would need barriers for the second heap. For young heap it is OK to just scan it. Maybe that work should be actually done even without th
Yes, I am aware about impreciseness of this. Currently I may not think about this for some other unrelated reasons as well... If you could point me out with the tools you used for this job, I would b
I've only loosely followed this thread so its possible I'm off the mark (in which case - sorry) but, i'm pretty sure it might be helpful to remark about a variant of what I guess Tromey is suggesting
On Sep 19, 2010, at 3:39 PM, Joe Brenner wrote: (Of late, the gnus emacs team seems to be having trouble with the idea of stable interfaces.) I don't think any of these have anything to do with gnus,
I don't think it matters. It ought to be impossible to get there via SIGINT except in batch mode, and if somehow Emacs does get there, it's going to exit anyway, so it's just a question of if it goes
Oh, fun. The first of those URLs claims that as a verb it is (only) transitive ("You obsoleted the bike"). The second of those claims that as a verb it is (only) intransitive ("You obsoleted, but th