unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Douglas Lewan <d.lewan2000@gmail.com>
To: Joost Kremers <joostkremers@fastmail.fm>, help-gnu-emacs@gnu.org
Subject: Re: wrong type error in local variables
Date: Thu, 2 Jul 2020 11:59:57 -0400	[thread overview]
Message-ID: <a2383409-37a5-56e5-297e-4810b32c52f1@gmail.com> (raw)
In-Reply-To: <87wo3m9csw.fsf@fastmail.fm>

On 7/2/20 11:06 AM, Joost Kremers wrote:
>
> On Thu, Jul 02 2020, Douglas Lewan wrote:
>> I have a TeX file with the following local variables:
>>
>>      Local Variables:
>>      eval: (ab-new-buffer (prog1 (find-file "chapter16.tex")      
>> (message "After find file.")))
>>      End:
>>
>> The (find-file) succeeds. (There's a buffer with that file and I see 
>> the message.) However, overall I get this error:
>>
>>      File local-variables error: (wrong-type-argument stringp      nil)
>>
>> I assume the call to (ab-new-buffer) gets the error, but as far as I 
>> can tell that call never happens. (ab-new-buffer) has the following 
>> definition:
>>
>>      (defun ab-new-buffer (buffer-or-name)
>>        (error "Now in (ab-new-buffer)."))
>>
>> I never see that error.
>> What am I missing?
>>
>> FYI The data above are obviously reduced to a minimal case. With the 
>> correct definition of (ab-new-buffer) a full battery of tests passes.
>
> Seems to work fine for me. Are you sure you have nothing else in your 
> local variables block? And what about the local variables block of the 
> file you're finding in your local variables block (i.e., 
> "chapter16.tex")?

I do have other things in the local variables, but that suggestion 
prompted me to try this in emacs -Q where I do see the above error.  
I'll try again in a clean emacs.

Now I have to wonder just how dirty I've made emacs....

Thanks for the prompt.

-- 
,Doug
d.lewan2000@gmail.com
(908) 720 7908

If this is what winning looks like, I'd hate to see what losing is.




  reply	other threads:[~2020-07-02 15:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 14:46 wrong type error in local variables Douglas Lewan
2020-07-02 15:06 ` Joost Kremers
2020-07-02 15:59   ` Douglas Lewan [this message]
2020-07-02 15:56 ` Stefan Monnier
2020-07-02 16:36   ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-07-02 17:09     ` Douglas Lewan
2020-07-02 17:45       ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-07-02 17:42     ` Stefan Monnier
2020-07-03  1:19       ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-07-03  1:40         ` Douglas Lewan
2020-07-03  2:00           ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-07-03  2:24             ` Douglas Lewan
2020-07-03  3:45           ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-07-03  5:13             ` Douglas Lewan
2020-07-03  6:05               ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-07-02 17:04   ` Douglas Lewan
2020-07-02 17:15   ` Douglas Lewan
  -- strict thread matches above, loose matches on Subject: below --
2020-07-03  8:33 Anders Munch
2020-07-03 10:36 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-07-03 14:07 ` Douglas Lewan

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=a2383409-37a5-56e5-297e-4810b32c52f1@gmail.com \
    --to=d.lewan2000@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=joostkremers@fastmail.fm \
    /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).