unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Cardaci <cyrus.and@gmail.com>
Cc: npostavs@gmail.com, 31312@debbugs.gnu.org
Subject: bug#31312: Segmentation fault with doom-emacs, NeoTree and Zoom
Date: Wed, 02 May 2018 18:06:47 +0300	[thread overview]
Message-ID: <83zi1ip054.fsf@gnu.org> (raw)
In-Reply-To: <CACMsj9M9tBJxjabpkLGU-8bcOS3iVj0TukTyL-tQ8HRMQ2yKbg@mail.gmail.com> (message from Andrea Cardaci on Wed, 2 May 2018 15:27:12 +0200)

> From: Andrea Cardaci <cyrus.and@gmail.com>
> Date: Wed, 2 May 2018 15:27:12 +0200
> Cc: bug-gnu-emacs@gnu.org, Noam Postavsky <npostavs@gmail.com>, 
> 	martin rudalics <rudalics@gmx.at>, 31312@debbugs.gnu.org
> 
> Any advice on this part? I needed to force the size of windows and hooking `select-window` (via `advice-add`)
> is apparently not enough to catch all the cases.
> 
> Is there a better way to achieve what I want?

If what Martin suggested somehow doesn't fit the bill, and no other
ideas are brought up, then I prefer to discuss new features or
infrastructure to satisfy similar needs, rather than force
applications to use such fragile techniques.  E.g., we could provide
some customizable controls in the code that resizes windows when
needed.





  parent reply	other threads:[~2018-05-02 15:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-29 10:56 bug#31312: Segmentation fault with doom-emacs, NeoTree and Zoom Andrea Cardaci
2018-05-01 13:25 ` Noam Postavsky
2018-05-01 14:33   ` martin rudalics
2018-05-01 23:10     ` Noam Postavsky
2018-05-02  6:16       ` martin rudalics
2018-05-02 11:52         ` Eli Zaretskii
2018-05-02 12:21         ` Noam Postavsky
2018-05-02 12:45           ` Eli Zaretskii
2018-05-02 13:27             ` Andrea Cardaci
2018-05-02 13:47               ` martin rudalics
2018-05-02 15:06                 ` Andrea Cardaci
2018-05-02 15:06               ` Eli Zaretskii [this message]
2018-05-02 15:14                 ` Andrea Cardaci
2018-05-02 15:30                   ` Eli Zaretskii
2018-05-02 13:42             ` martin rudalics
2018-05-02 15:03               ` Eli Zaretskii
2018-05-02 18:43                 ` martin rudalics
2018-05-02 19:02                   ` Eli Zaretskii
2018-05-03  7:11                     ` martin rudalics
2018-05-03  0:04               ` Noam Postavsky
2018-05-03  2:32                 ` Eli Zaretskii
2018-05-03 12:21                   ` Noam Postavsky
2018-05-03 17:54                     ` Eli Zaretskii
2018-05-04  1:18                       ` Noam Postavsky
2018-05-02 13:42           ` martin rudalics

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=83zi1ip054.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=31312@debbugs.gnu.org \
    --cc=cyrus.and@gmail.com \
    --cc=npostavs@gmail.com \
    /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).