From: Angelo Graziosi <angelo.g0@libero.it>
To: Eli Zaretskii <eliz@gnu.org>
Cc: hong@topbug.net, sebastian_rose@gmx.de,
plunix@users.sourceforge.net, emacs-devel@gnu.org
Subject: Re: Current master does not work with sr-speedbar package (W64 build)
Date: Thu, 6 Dec 2018 00:07:27 +0100 (CET) [thread overview]
Message-ID: <1181980169.366424.1544051247329@mail.libero.it> (raw)
In-Reply-To: <835zw7961j.fsf@gnu.org>
> Il 5 dicembre 2018 alle 19.34 Eli Zaretskii <eliz@gnu.org> ha scritto:
> Can you explain why you need the above ad-deactivate?
>
> > ;;(add-hook 'emacs-startup-hook 'start-sr-speedbar) ; the old way
> > (add-hook 'window-setup-hook 'start-sr-speedbar)
>
> And why do you start sr-speedbar from window-setup-hook?
OK, I have renounced to start sr-speedbar with Emacs and created this simple init.el initialization file:
$ cat init.el
(require 'sr-speedbar)
;; Setup sr-speedbar
(setq sr-speedbar-default-width 30)
(setq sr-speedbar-width 30)
(setq sr-speedbar-max-width 30)
(setq sr-speedbar-auto-refresh t)
with it, Emacs starts with *GNU Emacs* buffer and minibuffer has "For information....", as it is expected...
...but if now I open the sr-speedbar window:
M-x sr-speedbar-open
I get the same BAD behavior... and the minibuffer shows "Opening directory: No such file or directory, c:/msys64/tmp/emacs-master/src/"!
WHY it refers to its build directory???
Why all this occurs with the Windows build? I have built the same emacs-master.tar.gz source on GNU/Linux and macOS and there all works fine. On these systems I use the same method to start sr-speedbar (almost the same init.el). I start to think my Windows build was corrupted in some manner.. I will try a new build just to see if this fixes this annoying issue.
Thanks,
Angelo.
next prev parent reply other threads:[~2018-12-05 23:07 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 [this message]
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
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=1181980169.366424.1544051247329@mail.libero.it \
--to=angelo.g0@libero.it \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=hong@topbug.net \
--cc=plunix@users.sourceforge.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.