From: Agustin Martin <agustin.martin@hispalinux.es>
To: 6993@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#6993: Enabling Flyspell mode gave an error
Date: Tue, 7 Sep 2010 17:54:31 +0200 [thread overview]
Message-ID: <20100907155431.GA9663@agmartin.aq.upm.es> (raw)
In-Reply-To: <87tym1zk1c.fsf@jidanni.org>
On Tue, Sep 07, 2010 at 10:48:47PM +0800, jidanni@jidanni.org wrote:
> $ emacs -Q -nw -f flyspell-mode
> Enabling Flyspell mode gave an error
> $ apt-cache policy emacs-snapshot
> Installed: 1:20100903-2
Hi, Dan,
If you are using Debian emacs-snapshot please test
$ emacs-snapshot -Q -nw -f flyspell-mode
That is causing no problems here (1:20100903-2 too).
Note that a similar error recently happened in Debian with normal Emacs
(not the snapshots) because of change in options for (called-interactively-p)
between emacs23.1 and 23.2, when upgrading to a more recent flyspell.el
from FSF Emacs bzr repo.
I currently use in Debian
(condition-case nil ;; XEmacs does not have `called-interactively-p',
(called-interactively-p 'interactive) ;; emacs23.1 does not allow option and emacs23.2
(error (interactive-p)))) ;; needs it and mark `interactive-p' obsolete
to make that work for all, but since 23.1 is not to be shipped I may change
it back to something like
(if (fboundp 'called-interactively-p)
(called-interactively-p 'interactive)
(interactive-p))
to keep XEmacs happy. One of both may go into FSF Emacs bzr to decrease
XEmacs incompatibilities. Suggestions welcome.
Please confirm if problem persists when explicitly using emacs-snapshot.
--
Agustin
next prev parent reply other threads:[~2010-09-07 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 14:48 bug#6993: Enabling Flyspell mode gave an error jidanni
2010-09-07 15:54 ` Agustin Martin [this message]
2010-09-07 16:14 ` Agustin Martin
2010-09-07 18:13 ` Agustin Martin
2010-09-07 19:55 ` Thierry Volpiatto
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=20100907155431.GA9663@agmartin.aq.upm.es \
--to=agustin.martin@hispalinux.es \
--cc=6993@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
/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).