With today's Emacs: when I do M-x calendar, instead of just telling me
that there are no diary items for today as it used to, Emacs jumps to
the next diary-anniversary entry in my diary, which is on September
25th.
Is this intentional?
--
Romain Francoise <[EMAIL PROTECTED]> | I used to think th
"Chong Yidong" <[EMAIL PROTECTED]> writes:
> (2) Fix recognition of shell's `dirs' command.
> I installed tcsh, turned on command echoing, and was unable to get the
> `dirs' command confused. Let's just close this, unless someone else
> is seeing the problem.
I can reproduce it with bash and 's
> From: Stefan Monnier <[EMAIL PROTECTED]>
> Date: Mon, 12 Sep 2005 17:37:13 -0400
> Cc: emacs-devel@gnu.org
>
> >> > 1) When is the best estimate of when 22.1 will come out?
> >> Not before 2006.
> > I hope it can be done faster than that!
>
> I hope so as well, but my best estimate is still "no
[I sent this to emacs-pretest-bug a few days ago, but it didn't seem
to arrive. I think my email system was flaking out at the time.]
I installed VM to and played around with it trying to make the
string_free_list/compact_small_strings crash happen. I got a crash on
an invalid cons_free_list; du
2005/9/13, Nick Roberts <[EMAIL PROTECTED]>:
> > my impression is that
> > by-and-large, the unicode-2 branch is not going to change
> > dramatically.
>
> That does beg the question as to why unicode-2 hasn't already been merged into
> HEAD given that, using
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (Kim F. Storm) writes:
> The following code in compose_chars_in_text looks suspicious:
That's right. But, it's not used anymore and it seems that
I just forgot to delete that function. :-(
I'm sorry for taking your time on it. I've just deleted
On 9/12/05, Chong Yidong <[EMAIL PROTECTED]> wrote:
> I hope it can be done faster than that!
I'll eat my Emacs reference card if 22.1 is out before *2007*. Yeah,
I've read the rest of the thread. I'll be delighted to be proven
wrong.
> (3) Emacs on Windows crashes on JPEG images from files in u
Miles Bader writes:
> I use unicode-2 as my "secondary" emacs, and it seems pretty stable,
> more or less identical to the trunk.
and
> my impression is that
> by-and-large, the unicode-2 branch is not going to change
> dramatically.
That does beg the que
2005/9/13, Adrian Robert <[EMAIL PROTECTED]>:
> And how stable / bug-free is unicode-2
> right now compared with the will-become-22.1 code?
I use unicode-2 as my "secondary" emacs, and it seems pretty stable,
more or less identical to the trunk. The main problems I've had seem
to mostly be relate
Bill Wohler <[EMAIL PROTECTED]> writes:
> I'll try to send out a proposal by early next week with the list of
> affected image files.
This email lists the images in use by the MH-E package today, explains
how they got there, and proposes new locations in etc/images for them.
At the end, I also su
This is for you
http://adsfree.50megs.com
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
Eli Zaretskii <[EMAIL PROTECTED]> writes:
> I don't know why older Aspell's are no good for us. Magnus, can you
> please comment on that?
The main cause is that aspell >= 0.60 consistently supports UTF-8,
which simplifies the automatic dictionary detection. Supporting
aspell 0.50 would involve
>> > 1) When is the best estimate of when 22.1 will come out?
>> Not before 2006.
> I hope it can be done faster than that!
I hope so as well, but my best estimate is still "not before 2006".
Stefan
___
Emacs-devel mailing list
Emacs-devel@gn
"Chong Yidong" <[EMAIL PROTECTED]> writes:
> Can we start the release process once these five bugs are resolved, or
> is there any more reason to delay?
Starting the release process means to start the pre-test.
IMO, solving the remaining problems don't need to postpone that,
but Richard has the
"Chong Yidong" <[EMAIL PROTECTED]> writes:
> Stefan Monnier <[EMAIL PROTECTED]> writes:
>
>> > 1) When is the best estimate of when 22.1 will come out?
>>
>> Not before 2006.
>
> I hope it can be done faster than that!
[...]
> Can we start the release process once these five bugs are resolved,
>
Stefan Monnier <[EMAIL PROTECTED]> writes:
> > 1) When is the best estimate of when 22.1 will come out?
>
> Not before 2006.
I hope it can be done faster than that!
Looking through FOR-RELEASE, the only major bug left to fix is the
compact_small_strings/string_free_list problem -- which may have
> From: Stefan Monnier <[EMAIL PROTECTED]>
> Date: Mon, 12 Sep 2005 12:22:54 -0400
>
> Now whenever I try to run flyspell-mode (which I use pretty much
> everywhere), I get the following backtrace:
>
> Indeed, my aspell is older than 0.60, but it worked just fine until now.
> It's not like Fedora
Would people be conceptually opposed to making the fsync() call optional
in Fwrite_region? Calling it after each write defeats the kernel's
ability to commit consecutive buffers to disk in one go, which can be
beneficial in a lot of cases (like nnml files in an nnml directory). It
also means that
> 1) When is the best estimate of when 22.1 will come out?
Not before 2006.
> My second question concerns the unicode-2 branch of CVS. As I understand
I don't know much about Aqua/Cocoa/Carbon, and more specifically I don't
know how different are Cocoa and Carbon, so I don't know who much of t
Hi,
I'm maintaining the Emacs-on-Aqua GNUstep / OS X port, currently
based on emacs 20.7 (http://emacs-on-aqua.sf.net/). I want to update
this to a more recent version but would ideally like to do so against
a stabilized / released version of GNU emacs -- just so I know that
bugs are my
Stefan Monnier writes:
> If foo is displayed in a window, it has 2 points: its own and the
> one of the window.
My first thought was to ask if this is a new feature. It isn't.
It's just plain embarrassing that one can work more than ten years
with an editor without ever noting something as fund
Isn't lisp/international/iso-insert.el obsolete?
I mean iso-transl.el (which is preloaded) does the same thing anyway,
only better.
Stefan
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
> $ echo -e "this\nthat" | grep '(this|that)'
Try "grep '\(this\|that\)'"
Stefan
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
Now whenever I try to run flyspell-mode (which I use pretty much
everywhere), I get the following backtrace:
Indeed, my aspell is older than 0.60, but it worked just fine until now.
It's not like Fedora Core 2 is ancient. It's not the latest and greatest,
but it should definitely be among the sy
Jari Aalto <[EMAIL PROTECTED]> writes:
> Andreas Schwab <[EMAIL PROTECTED]> writes:
>
> | Jari Aalto <[EMAIL PROTECTED]> writes:
> |
> | > Could you elaborate a little. The syntax of grep is not sufficient to
> | > make daily searches with M-x find-dired or M-x grep-find that happen
> | > frequen
Andreas Schwab <[EMAIL PROTECTED]> writes:
| Jari Aalto <[EMAIL PROTECTED]> writes:
|
| > Could you elaborate a little. The syntax of grep is not sufficient to
| > make daily searches with M-x find-dired or M-x grep-find that happen
| > frequently during searching system log files or looking into
> --- orig/lisp/startup.el
> +++ mod/lisp/startup.el
> @@ -1004,14 +1004,21 @@
>(not (load (concat term-file-prefix term) t t)))
> ;; Strip off last hyphen and what follows, then try again
> (setq term
> - (if (setq hyph
I'd suggest to add the Message-ID (maybe in addition to sender and
date).
That is feasible.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
> (Would you want to find the URLs for me?)
Given the date and the Subject, it should be very easy to do that,
using the mail-archive Search command.
For me, this is not merely hard, but impossible. I do my work without
internet access, most of the time.
___
I think you are right about the bug, but I think your patch does not
completely fix it. This patch, which seems to work, should fix the bug
completely by accessing the string only through its Lisp object pointer.
*** xdisp.c 08 Sep 2005 20:35:28 -0400 1.1050
--- xdisp.c 12 Sep 2005 0
I have no idea if this will work without some non-trivial re-shuffling
of the code in x-popup-menu. Just looking at the source, it seems to
invoke functions that need X (or its emulation). Someone will have to
work on refactoring the code before we can do what you suggest.
The fo
Jari Aalto <[EMAIL PROTECTED]> writes:
> Could you elaborate a little. The syntax of grep is not sufficient to
> make daily searches with M-x find-dired or M-x grep-find that happen
> frequently during searching system log files or looking into program
> and text document files.
In GNU grep there
"Richard M. Stallman" <[EMAIL PROTECTED]> writes:
| The use of grep(1) command in all of there is not optimal. So my question
| was wheather there were any *nix OS that did not define egrep(1) and thus
| would prevent using "egrep" as a default value.
|
| I do not want to change to eg
> or - but this might disturb people accustomed to the current behavior of
> plain font-lock -
> (when font-lock-multiline
> (setq end (or (text-property-any end (point-max)
>'font-lock-multiline nil)
> (point-ma
The following code in compose_chars_in_text looks suspicious:
if (INTEGERP (val) && XFASTINT (val) == start)
{
to = Fmatch_end (make_number (0));
val = call4 (XCDR (elt), val, to, XCAR (elt), string);
if (INTEGERP
Variable mail-yank-prefix is currently defined in sendmail.el, so in
order to access it's default value, one would formally need to load
sendmail:
(require 'sendmail)
Perhaps few ###autoloads would be in place here? Proposed patch follows.
2005-09-12 Mon Jari Aalto
* mail/sendm
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (Kim F. Storm) writes:
> Kenichi Handa <[EMAIL PROTECTED]> writes:
>> I got a bug report for emacs-unicode-2, and it seems that
>> the same bug exists in HEAD too. The backtrace is this:
>> and never changed in the while loop. So the only reas
Kenichi Handa <[EMAIL PROTECTED]> writes:
> I got a bug report for emacs-unicode-2, and it seems that
> the same bug exists in HEAD too. The backtrace is this:
> and never changed in the while loop. So the only reason I
> can think of why the address pointed by list_string becomes
> out of bound
38 matches
Mail list logo
