unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Agustin Martin <agustin6martin@gmail.com>
To: 19926@debbugs.gnu.org
Subject: bug#19926: 24.4; `ispell-comments-and-strings' (somewhat) unclear docstring
Date: Tue, 24 Feb 2015 13:24:16 +0100	[thread overview]
Message-ID: <20150224122415.GA4507@agmartin.aq.upm.es> (raw)
In-Reply-To: <pfh9uczayx.fsf@fencepost.gnu.org>

On Mon, Feb 23, 2015 at 02:25:42PM -0500, Glenn Morris wrote:
> Agustin Martin wrote:
> 
> > Note that version above is only used in Debian/GNU*
> 
> Why does Debian distribute a duplicate ispell.el (and flyspell.el; both
> in the dictionaries-common package), and why does it differ from the
> version in Emacs (a quick diff seemed to show other differences)?

Initially this was done to have better integration with the spellchecking
dictionaries structure in Debian. However, relevant code has been integrated
in FSF Emacs trunk. Other reason was to add some bug fixes from trunk to all
available flavours and the last one to to use a version that can also be used
for XEmacs. 

I will soon change this, leaving current Debian version only for XEmacs
(ispell.el and flyspell.el shipped with XEmacs are ancient) and relying in
FSF Emacs pristine versions. I still have to commit a couple of things to
the emacs-24 branch, but I'd like to do this change in Debian at some time
after Debian "jessie" release. There are some recent changes in trunk that
will be hard to migrate to XEmacs and differences are expected to become
more and more important with time. If some bug appears that really needs a
fix, it can be fixed in the Emacs package.

> Since it ends up in site-lisp it is always going to shadow the Emacs version.

Should not unless subdirs.el is present in the dir containing the byte-compiled
stuff. According to policy for emacsen add-ons in Debian byte-compiled path
must be explicitly added, so it can be disabled. However, I just noticed that 
/usr/share/emacs24/site-lisp/subdirs.el is also present, so things will be
found even if path is not explicitly added. I think I warned about this some
time ago, because this makes harder to disable the Debian stuff, but I do
not remember having received a reply. Have to re-check.
 
-- 
Agustin





  reply	other threads:[~2015-02-24 12:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-22 23:45 bug#19926: 24.4; `ispell-comments-and-strings' (somewhat) unclear docstring Emanuel Berg
2015-02-23 12:38 ` Agustin Martin
2015-02-23 19:25   ` Glenn Morris
2015-02-24 12:24     ` Agustin Martin [this message]
2015-02-24 20:48       ` Glenn Morris
2015-02-23 17:02 ` Glenn Morris

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=20150224122415.GA4507@agmartin.aq.upm.es \
    --to=agustin6martin@gmail.com \
    --cc=19926@debbugs.gnu.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).