From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: wrong type error in local variables
Date: Thu, 02 Jul 2020 19:45:51 +0200 [thread overview]
Message-ID: <87zh8hq08g.fsf@ebih.ebihd> (raw)
In-Reply-To: 221f58fd-49fc-cd67-1634-ec8dd02258fc@gmail.com
Douglas Lewan wrote:
>>> `find-file` should not be called from Elisp.
>>> Use `find-file-noselect` instead.
>>
>> Oups, if so I have 15 changes to make.
>>
>> Why doesn't the byte compiler say this?
>
> Or even the docstring? Lots of docstrings mention
> such things.
... and the more the better!
Well, the ideal would be that everything could be
used from everywhere.
Put a `cond' in `find-file' and branch to
`find-file-noselect' if called from Lisp :)
--
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal
next prev parent reply other threads:[~2020-07-02 17:45 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
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 [this message]
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=87zh8hq08g.fsf@ebih.ebihd \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).