debugging odd startup message

debugging odd startup message

[Perry E. Metzger]

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.

Not sure how to figure out exactly where this is happening -- I'm
guessing some file I'm loading, but I'm unsure. I'm not
running bytecomp on startup, which also makes the error a bit odd.

Anyway, if anyone can give me suggestions on how to figure out how to
pin down what's causing this so I can fix it, I'd appreciate it.

-- 
Perry E. Metzger		perry@piermont.com

Re: debugging odd startup message

[Joost Kremers]

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.
>
> Not sure how to figure out exactly where this is happening -- 
> I'm
> guessing some file I'm loading, but I'm unsure. I'm not
> running bytecomp on startup, which also makes the error a bit 
> odd.
>
> Anyway, if anyone can give me suggestions on how to figure out 
> how to
> pin down what's causing this so I can fix it, I'd appreciate it.

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.

-- 
Joost Kremers
Life has its moments

Re: debugging odd startup message

[Stefan Monnier]

"Perry E. Metzger" <perry@piermont.com> writes:

> 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.
>
> Not sure how to figure out exactly where this is happening -- I'm
> guessing some file I'm loading, but I'm unsure. I'm not
> running bytecomp on startup, which also makes the error a bit odd.
>
> Anyway, if anyone can give me suggestions on how to figure out how to
> pin down what's causing this so I can fix it, I'd appreciate it.

You can add something like

    (trace-function 'byte-compile)

at the beginning of your ~/.emacs file.  Or alternatively something like

    (debug-on-entry 'byte-compile)

might give you more information.


        Stefan

Re: debugging odd startup message

[Noam Postavsky]

On 15 June 2018 at 16:13, Perry E. Metzger <perry@piermont.com> 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.

It's a warning inside some defadvice, I think. You can get a better
message (i.e., with filename) by setting after-init-time to non-nil.

Previous occurrence:

https://lists.gnu.org/archive/html/emacs-devel/2017-01/msg00290.html
https://lists.gnu.org/archive/html/emacs-devel/2017-02/msg00625.html

Re: debugging odd startup message

[Perry E. Metzger]

On Fri, 15 Jun 2018 17:54:57 -0400 Noam Postavsky
<npostavs@gmail.com> wrote:
> On 15 June 2018 at 16:13, Perry E. Metzger <perry@piermont.com>
> 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.  
> 
> It's a warning inside some defadvice, I think. You can get a better
> message (i.e., with filename) by setting after-init-time to non-nil.

So, this is the crazy thing, if I run:

emacs -q --eval '(setq after-init-time nil)' -l ~/.emacs

the error message vanishes entirely. Nothing goes wrong at all.

This is a giant WTF to me.

Perry
-- 
Perry E. Metzger		perry@piermont.com

Re: debugging odd startup message

[Perry E. Metzger]

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

Re: debugging odd startup message

[Perry E. Metzger]

On Fri, 15 Jun 2018 18:43:56 -0400 "Perry E. Metzger"
<perry@piermont.com> wrote:
> So, this is the crazy thing, if I run:
> 
> emacs -q --eval '(setq after-init-time nil)' -l ~/.emacs
> 
> the error message vanishes entirely. Nothing goes wrong at all.
> 
> This is a giant WTF to me.

I blew away my elpa directory, reinstalled all my packages, and now
the error has gone away. I have no explanation for any of this, but I
suppose for the moment my problem is gone.

Perry
-- 
Perry E. Metzger		perry@piermont.com