unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Angelo Graziosi <angelo.g0@libero.it>
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: Tue, 04 Dec 2018 19:57:46 +0200	[thread overview]
Message-ID: <831s6x9ntx.fsf@gnu.org> (raw)
In-Reply-To: <1723869815.291238.1543945851468@mail.libero.it> (message from Angelo Graziosi on Tue, 4 Dec 2018 18:50:51 +0100 (CET))

> Date: Tue, 4 Dec 2018 18:50:51 +0100 (CET)
> From: Angelo Graziosi <angelo.g0@libero.it>
> 
> Current Emacs master (f745cf8c438) does not work with the sr-speedbar package (https://github.com/emacsorphanage/sr-speedbar/blob/master/sr-speedbar.el) from MELPA.
> 
> Usually I have it configured so that Emacs opens in a single frame with 2 window: one for the text (80 characters in width showing the buffer text) and one for sr-speedbar (30 characters in width showing folders and files).
> 
> After the upgrade to the last Emacs master, the sr-speedbar window has the same width as before but it shows the buffer text... if I remove the desktop file, Emacs start with 2 window each containing the scratch buffer.
> 
> If, now, I allow for saving the desktop file, at the next start, I get 3 window (3 scratch buffers): one window 50 characters in width and 2 window 30 characters in width. At the next start, 4 window, about: 25, 30, 30, 30 and so on...

Please show the way you configure Emacs for these windows.  My guess
is that you call functions that create windows while the selected
window is dedicated to its buffer, or something similar.



  reply	other threads:[~2018-12-04 17: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 [this message]
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
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

  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=831s6x9ntx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=angelo.g0@libero.it \
    --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 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).