From: "Perry E. Metzger" <perry@piermont.com>
To: Joost Kremers <joostkremers@fastmail.fm>
Cc: emacs-devel@gnu.org
Subject: Re: debugging odd startup message
Date: Fri, 15 Jun 2018 18:46:59 -0400 [thread overview]
Message-ID: <20180615184659.63b2ccbd@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <87o9gbohqq.fsf@fastmail.fm>
On Fri, 15 Jun 2018 23:35:41 +0200 Joost Kremers
<joostkremers@fastmail.fm> wrote:
> On Fri, Jun 15 2018, Perry E. Metzger wrote:
> > On emacs startup, I'm getting this message:
> >
> > Warning (bytecomp): Use ‘with-current-buffer’ rather than
> > save-excursion+set-buffer
> > Warning (bytecomp): ‘next-line’ is for interactive use only; use
> > ‘forward-line’ instead.
> First thing I'd do is check the *Messages* buffer (C-h e). You
> should find the errors there as well, but sometimes the *Messages*
> buffer also tells you which file produced the error.
>
> Otherwise, comment out any files you're loading in your init file
> one by one and see which one produces the error.
I have narrowed this down to a single file being loaded, which has
neither "with-current-buffer" or "next-line" in it.
I have to admit to being very very confused. :(
--
Perry E. Metzger perry@piermont.com
next prev parent reply other threads:[~2018-06-15 22:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 20:13 debugging odd startup message Perry E. Metzger
2018-06-15 21:35 ` Joost Kremers
2018-06-15 22:46 ` Perry E. Metzger [this message]
2018-06-15 21:48 ` Stefan Monnier
2018-06-15 21:54 ` Noam Postavsky
2018-06-15 22:43 ` Perry E. Metzger
2018-06-16 0:59 ` Perry E. Metzger
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=20180615184659.63b2ccbd@jabberwock.cb.piermont.com \
--to=perry@piermont.com \
--cc=emacs-devel@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.
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).