GNU bug report logs - #28492
27.0.50; File mode specification error for some files during desktop-read

Previous Next

Full log

Message #10 received at 28492-done <at> debbugs.gnu.org (full text, mbox):

From: Kaushal Modi <kaushal.modi <at> gmail.com>
To: 28492-done <at> debbugs.gnu.org
Subject: 27.0.50;
 File mode specification error for some files during desktop-read
Date: Mon, 18 Sep 2017 14:36:05 +0000

[Message part 1 (text/plain, inline)]

Sorry about the noise.

Turns out that a string-match-p was doing with a nil values variable in a
function I added to the verilog-mode-hook. (And that variable was
evaluating to nil only for a particular project.)

The error backtrace was confusing though.. it looked like set-auto-mode was
throwing the error.

But actually it was

set-auto-mode
  - set-auto-mode-0
    - (funcall mode)
      - run-hooks .. (running the major mode hook)
        - One of the functions in that hook

Is there a way so that an error like

    Error in one of the functions in verilog-mode-hook while running
some.file

gets printed instead of a misleading message that doesn't even mention the
file causing it:

File mode specification error: (wrong-type-argument stringp nil)
-- 

Kaushal Modi

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.