unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Rainer Stengele <rainer.stengele@online.de>, help-gnu-emacs@gnu.org
Subject: RE: icicles Lisp error
Date: Wed, 17 Dec 2014 07:05:22 -0800 (PST)	[thread overview]
Message-ID: <73008f0b-1d75-4c57-a413-5314b9fa22ee@default> (raw)
In-Reply-To: <m6rqal$bvd$1@ger.gmane.org>

I could be wrong, but this looks like an Emacs bug. This code:

(file-relative-name "/home/rainer/.emacs.d/icicles/icicles-mode.el"
                    ".")

is raising an error.  This is what `file-relative-name' does
with its DIRECTORY argument (immediately):

(file-name-as-directory
  (expand-file-name (or DIRECTORY default-directory)))

And for DIRECTORY = "." that should give the working directory as
a file name.  I don't think the call to `file-relative-name' here
should be problematic.

Please consider reporting this to Emacs Dev: `M-x report-emacs-bug'.

> When starting up Emacs I run into this Lisp error when requiring
> icicles.
> GNU Emacs 24.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.8.2) of 2013-
> 07-27 on roseapple, modified by Debian
> 
> icicles is from this morning, uncompiled.
> 
> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>   compare-strings("/home/rainer/.emacs.d/icicles/icicles-mode.el/"
> nil 0 nil nil nil nil)
>   file-relative-name("/home/rainer/.emacs.d/icicles/icicles-mode.el"
> ".")
>   byte-compile-abbreviate-
> file("/home/rainer/.emacs.d/icicles/icicles-mode.el" ".")
>   byte-compile-warning-prefix(:error (:error "Error%s: "))
>   display-warning(bytecomp "Wrong type argument: stringp, nil"
> :error "*Compile-Log*")
>   byte-compile-log-warning("Wrong type argument: stringp, nil" nil
> :error)
>   byte-compile-report-error((wrong-type-argument stringp nil))
>   #[257 "\300\x01!\207" [byte-compile-report-error] 3 "\n\n(fn ERROR-
> INFO)"]((wrong-type-argument stringp nil))
>   funcall(#[257 "\300\x01!\207" [byte-compile-report-error] 3 "\n\n(fn
> ERROR-INFO)"] (wrong-type-argument stringp nil))
>   byte-compile(advice-compilation)
>   ad-compile-function(describe-face)
>   ad-activate-advised-definition(describe-face nil)
>   ad-activate(describe-face nil)



      reply	other threads:[~2014-12-17 15:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17 11:44 icicles Lisp error Rainer Stengele
2014-12-17 15:05 ` Drew Adams [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=73008f0b-1d75-4c57-a413-5314b9fa22ee@default \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=rainer.stengele@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.
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).