unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 7027@debbugs.gnu.org
Subject: bug#7027: 24.0.50; Dired error (wrong-type-arg stringp nil) with cons arg with wildcard in name
Date: Tue, 01 Oct 2019 21:59:37 +0200	[thread overview]
Message-ID: <87r23ww82e.fsf@gnus.org> (raw)
In-Reply-To: <3F599FB93CFD4CA1BDAA1A6E038C7B9F@us.oracle.com> (Drew Adams's message of "Sun, 12 Sep 2010 15:08:23 -0700")

"Drew Adams" <drew.adams@oracle.com> writes:

> Eval this: (dired '("TTTT" "111.el" "b*.el")), assuming there is a file
> 111.el and some file matching b*.el (but no file with name "b*.el",
> i.e. with a literal `*' in the name).
>
> You get this error: (wrong-type-argument stringp nil)

Can you post the backtrace?

[...]

> This gets eval'd (where the ^@ is really a control char):
>
> (ls-lisp-insert-directory nil (97 108) nil "\\`b[^^@]*\\.el\\'" nil)
>
> That happens because of this call:
>
> (insert-directory "b*.el" "-al" nil nil)
>
> which calls (string-match "[[?*]" "b*.el") returning 1 (non-nil).
>
> (file-exists-p "b*.el") then returns nil,
> and (wildcard-to-regexp "b*.el") returns the regexp shown above.

I tried reproducing with

(ls-lisp-insert-directory nil '(97 108) nil (wildcard-to-regexp "b*.el") nil)

but that fails with a different error since FILE can't be nil.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-10-01 19:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-12 22:08 bug#7027: 24.0.50; Dired error (wrong-type-arg stringp nil) with cons arg with wildcard in name Drew Adams
2019-10-01 19:59 ` Lars Ingebrigtsen [this message]
2020-04-17 10:22   ` Stefan Kangas

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=87r23ww82e.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=7027@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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).