From: David.Kastrup@t-online.de (David Kastrup)
Subject: Re: Bug#142608: emacs21: please apply flyspell patch from preview-latex package
Date: 14 Apr 2002 12:28:22 +0200 [thread overview]
Message-ID: <x57kna8th5.fsf@tupik.goethe.zz> (raw)
In-Reply-To: 871ydiq5ju.fsf@raven.i.defaultvalue.org
I have now checked the patch from Emacs-21.1 to Emacs-21.2. The fixes
are not contained in Emacs-21.2, so it seems they would have been
judged not important enough for the bug fix release 21.2, which I find
unfortunate. The bugs are not present in the current CVS version,
however, so it may be hoped that they will not make it into 21.3. As
the main author of preview-latex, and the author of these patches, I
would recommend applying them at the very least when you are
installing preview-latex. They are rather certainly not causing more
trouble than the original behavior. They have been tested, and either
they. or equivalent changes, have been put into the current Emacs
sources long ago.
The bugs will affect every package using overlays with keymaps of
their own, not just preview-latex. I don't know, however, whether
there are packages around where the impact is as annoying as here.
rlb@defaultvalue.org (Rob Browning) writes:
> A recent report suggests Emacs 21.2 may have a bug which interacts
> with the preview-latex package. I've included the two Emacs patches
> provided by the preview-latex source below in case you haven't
> received them yet through other channels.
>
> Please let me know if you'd like me to include these patches in the
> current Debian Emacs 21.2 package.
I will update preview-latex documentation to state that those bugs
remain in Emacs-21.2. Pity.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
Email: David.Kastrup@t-online.de
prev parent reply other threads:[~2002-04-14 10:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E16wEb6-0005Op-00@volition>
2002-04-14 4:15 ` Bug#142608: emacs21: please apply flyspell patch from preview-latex package Rob Browning
2002-04-14 10:28 ` David Kastrup [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x57kna8th5.fsf@tupik.goethe.zz \
--to=david.kastrup@t-online.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).