all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Angelo Graziosi <angelo.g0@libero.it>
Cc: sebastian_rose@gmx.de, hong@topbug.net, emacs-devel@gnu.org
Subject: Re: Current master does not work with sr-speedbar package (W64 build)
Date: Thu, 06 Dec 2018 14:57:42 +0200	[thread overview]
Message-ID: <D5D79C9B-A284-4F9E-96F0-98B245C36EE5@gnu.org> (raw)
In-Reply-To: <1416933916.408019.1544095693412@mail.libero.it>

On December 6, 2018 1:28:13 PM GMT+02:00, Angelo Graziosi <angelo.g0@libero.it> wrote:
> 
> > Il 6 dicembre 2018 alle 10.17 Eli Zaretskii <eliz@gnu.org> ha
> scritto:
> > 
> > 
> > > Date: Thu, 6 Dec 2018 10:00:29 +0100 (CET)
> > > From: Angelo Graziosi <angelo.g0@libero.it>
> > > Cc: sebastian_rose@gmx.de, emacs-devel@gnu.org, hong@topbug.net
> > > 
> > > Compiling no file at Thu Dec  6 09:46:33 2018
> > 
> > This sounds like bug#33602, which is not Windows-specific.
> 
> I think we have two kind of bugs: I see the Compile-Log buffer also on
> macOS and GNU/Linux builds (20181204 froma master). But the error in
> Pakages buffer shows up only in the Windows build.
> 
> > 
> > > As you see, no sr-speedbar is used at all.
> > 
> > OK, but a Lisp backtrace from an error message about non-existent
> > directory would still be useful.  Maybe it's part of the same
> problem
> > as the "no file" above, but I'm not yet sure it is.
> 
> Please, give me a recipe...

Type "M-x set-variable RET debug-on-error RET t RET", then do the steps needed to trigger the problem.  Emacs should display a buffer with Lisp backtrace; post that here.

Thanks.



  reply	other threads:[~2018-12-06 12:57 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04 17:50 Current master does not work with sr-speedbar package (W64 build) Angelo Graziosi
2018-12-04 17:57 ` Eli Zaretskii
2018-12-04 23:31   ` Angelo Graziosi
2018-12-05 18:34     ` Eli Zaretskii
2018-12-05 22:42       ` Angelo Graziosi
2018-12-05 23:07       ` Angelo Graziosi
2018-12-06  0:07         ` Angelo Graziosi
2018-12-06  0:12           ` Angelo Graziosi
2018-12-06  0:54             ` Angelo Graziosi
2018-12-06  6:48               ` Eli Zaretskii
2018-12-06  9:10               ` martin rudalics
2018-12-06 16:12                 ` Angelo Graziosi
2018-12-06  6:35         ` Eli Zaretskii
2018-12-06  9:00           ` Angelo Graziosi
2018-12-06  9:17             ` Eli Zaretskii
2018-12-06 11:28               ` Angelo Graziosi
2018-12-06 12:57                 ` Eli Zaretskii [this message]
2018-12-06 17:49                   ` Angelo Graziosi
2018-12-06 18:20                     ` Eli Zaretskii
2018-12-06 19:36                       ` Angelo Graziosi
2018-12-06 19:47                         ` Eli Zaretskii
2018-12-06 20:45                           ` Angelo Graziosi
2018-12-06 23:55                             ` Angelo Graziosi
2018-12-07  8:04                               ` Eli Zaretskii
2018-12-07  8:57                                 ` Eli Zaretskii
2018-12-07 16:34                                   ` Angelo Graziosi
2018-12-07 16:44                                     ` Eli Zaretskii
2018-12-07  6:22                             ` Eli Zaretskii
2018-12-07  8:34                               ` Angelo Graziosi
2018-12-07  0:36                     ` Stefan Monnier
2018-12-07  7:13                       ` martin rudalics
2018-12-07 13:00                         ` Stefan Monnier
2018-12-07 13:16                           ` martin rudalics
2018-12-07 13:26                             ` Stefan Monnier
2018-12-07 13:49                               ` martin rudalics
2018-12-10 15:07                                 ` Stefan Monnier
2018-12-07 13:58                               ` Eli Zaretskii
2018-12-07 13:22                           ` Eli Zaretskii
2018-12-06 18:45                 ` martin rudalics
2018-12-06 19:34                   ` Angelo Graziosi

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D5D79C9B-A284-4F9E-96F0-98B245C36EE5@gnu.org \
    --to=eliz@gnu.org \
    --cc=angelo.g0@libero.it \
    --cc=emacs-devel@gnu.org \
    --cc=hong@topbug.net \
    --cc=sebastian_rose@gmx.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.