Emacs 25: Warning (bytecomp): Use ‘with-current-buffer’

Emacs 25: Warning (bytecomp): Use ‘with-current-buffer’

[Arash Esbati]

Hi all,

I can successfully build emacs-25 branch on Win7 64bit with:

--8<---------------cut here---------------start------------->8---
PKG_CONFIG_PATH=/mingw64/lib/pkgconfig \
CPPFLAGS='-DNDEBUG'    \
CFLAGS='-O3 -g0 -pipe' \
LDFLAGS='-s -Wl,-s'    \
./configure            \
--host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32  \
--build=x86_64-w64-mingw32 --with-wide-int --with-jpeg \
--with-xpm --with-png --with-tiff --with-rsvg          \
--with-xml2 --with-gnutls --with-xft \
--without-imagemagick --without-dbus
--8<---------------cut here---------------end--------------->8---

(and then `make' and `make install').  When I start it from bash with
`./emacs &', I get:

--8<---------------cut here---------------start------------->8---
Warning (bytecomp): Use ‘with-current-buffer’ rather than save-excursion+set-buffer
--8<---------------cut here---------------end--------------->8---

I don't get this warning with `emacs -Q &' or Emacs 24.5.  Since the
message is somewhat sparse, can somebody give me a hint how to search in
my `.emacs' for the culprit?

TIA, Arash

Re: Emacs 25: Warning (bytecomp): Use ‘with-current-buffer’

[Artur Malabarba]

Arash Esbati <esbati@gmx.de> writes:

> Warning (bytecomp): Use ‘with-current-buffer’ rather than save-excursion+set-buffer
>
> I don't get this warning with `emacs -Q &' or Emacs 24.5.  Since the
> message is somewhat sparse, can somebody give me a hint how to search in
> my `.emacs' for the culprit?

You could try an `M-x rgrep' for `set-buffer'.

Keep in mind the warning could also be coming from a package inside
`.emacs.d/elpa', instead of your `.emacs'.

RE: Emacs 25: Warning (bytecomp): Use ‘with-current-buffer’

[Drew Adams]

> > Warning (bytecomp): Use ‘with-current-buffer’ rather than save-
> > excursion+set-buffer
> >
> > I don't get this warning with `emacs -Q &' or Emacs 24.5.  Since the
> > message is somewhat sparse, can somebody give me a hint how to search in
> > my `.emacs' for the culprit?
> 
> You could try an `M-x rgrep' for `set-buffer'.
> 
> Keep in mind the warning could also be coming from a package inside
> `.emacs.d/elpa', instead of your `.emacs'.

Is there a good reason why the warning should not reference
(elisp) Excursions, which explains the issue?