unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Robert Thorpe <rt@robertthorpeconsulting.com>
To: AW <alexander.willand@t-online.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: ispell/hunspell/Windows: a fully-worked example
Date: Fri, 04 Apr 2014 22:56:37 +0100	[thread overview]
Message-ID: <87zjk0zrl6.fsf@robertthorpeconsulting.com> (raw)
In-Reply-To: <2656962.XDx7xcfxFm@linux-j9m3.site> (message from AW on Fri, 04 Apr 2014 16:30:33 +0200)

AW <alexander.willand@t-online.de> writes:

> [SOLVED]
> I took the opportunity and cleaned out my site-lisp directory. Whatever it 
> was, some relict *.el, it's gone now and I'll test hunspell.
>
> Thanks to everybody who read this thread and thought about it!

I know you've solved it now, but I think it's worth mentioning another
complication.

On MS Windows the icon link files contain a path to an executable and
another path, the current directory to run that executable in.  Let's
say you install a new version of Emacs.  Instead of installing the new
menus and links with "addpm.exe" you just change the executable path in
the icon link file on your desktop.  In that case the new version of
Emacs is starting in the current directory of the old version.  That can
make Emacs confused if it searches for things in the current directory.

If this happens starting emacs from a command window will behave
differently to clicking the icon.

BR,
Robert Thorpe



  reply	other threads:[~2014-04-04 21:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03  7:39 ispell/hunspell/Windows: a fully-worked example djc
2014-04-04  7:41 ` djc
2014-04-04 10:29   ` AW
2014-04-04 10:42     ` Eli Zaretskii
2014-04-04 12:47       ` AW
2014-04-04 13:03         ` Eli Zaretskii
2014-04-04 14:00           ` AW
2014-04-04 14:30             ` AW
2014-04-04 21:56               ` Robert Thorpe [this message]
2014-04-05  6:49                 ` Eli Zaretskii
2014-04-05  9:43                   ` Robert Thorpe
     [not found]                 ` <mailman.18956.1396680552.10748.help-gnu-emacs@gnu.org>
2014-04-05  6:59                   ` David Masterson
2014-04-05  8:13                     ` Eli Zaretskii

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=87zjk0zrl6.fsf@robertthorpeconsulting.com \
    --to=rt@robertthorpeconsulting.com \
    --cc=alexander.willand@t-online.de \
    --cc=help-gnu-emacs@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. 
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).