From: "Juanma Barranquero" <lekktu@gmail.com>
Cc: martin rudalics <rudalics@gmx.at>,
help-gnu-emacs@gnu.org, michael@cadilhac.name
Subject: Re: MY window tree!
Date: Mon, 15 Jan 2007 14:50:55 +0100 [thread overview]
Message-ID: <f7ccd24b0701150550r946ac0dwda4318cca2d7afb9@mail.gmail.com> (raw)
In-Reply-To: <45AB7C99.6050002@gmail.com>
>From your package:
;; Juanma Barranquero has pointed out there is a serious limitation in
;; this way of doing it when overlays with 'window properties are
;; used. The problem is that any pointers to windows are made invalid
;; since they are deleted. So in fact any code that relies on saved
;; pointers to windows will have problem if the window is one of those
;; that are involved here.
I was talking of modes that maintain a list of *overlays*, not
windows, but this other point, though not mine, is also valid :)
All in all, I think all this is complicated stuff for something that
would perhaps be easier at the C level, without the need to delete and
recreate windows.
/L/e/k/t/u
next prev parent reply other threads:[~2007-01-15 13:50 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-13 10:11 MY window tree! martin rudalics
2007-01-14 9:35 ` Lennart Borgman (gmail)
2007-01-14 11:26 ` martin rudalics
2007-01-14 11:45 ` Lennart Borgman (gmail)
2007-01-14 15:03 ` Juanma Barranquero
2007-01-14 15:29 ` Lennart Borgman (gmail)
2007-01-14 17:41 ` martin rudalics
2007-01-14 17:56 ` Lennart Borgman (gmail)
2007-01-14 21:35 ` Lennart Borgman (gmail)
2007-01-14 22:57 ` Juanma Barranquero
2007-01-14 23:15 ` Lennart Borgman (gmail)
2007-01-15 7:27 ` martin rudalics
2007-01-15 13:07 ` Lennart Borgman (gmail)
2007-01-15 13:50 ` Juanma Barranquero [this message]
2007-01-15 14:09 ` Lennart Borgman (gmail)
2007-01-15 14:33 ` Juanma Barranquero
2007-01-15 14:41 ` Lennart Borgman (gmail)
2007-01-15 14:56 ` Juanma Barranquero
2007-01-15 16:32 ` Lennart Borgman (gmail)
2007-01-15 17:33 ` martin rudalics
2007-01-15 17:47 ` Lennart Borgman (gmail)
2007-01-15 17:58 ` martin rudalics
2007-01-15 18:16 ` Lennart Borgman (gmail)
2007-01-15 18:44 ` martin rudalics
2007-01-15 18:52 ` Lennart Borgman (gmail)
2007-01-15 17:26 ` martin rudalics
2007-01-15 17:56 ` Lennart Borgman (gmail)
2007-01-15 18:33 ` martin rudalics
2007-01-15 18:14 ` Lennart Borgman (gmail)
2007-01-15 19:22 ` martin rudalics
2007-01-15 20:26 ` Lennart Borgman (gmail)
2007-01-15 22:44 ` martin rudalics
2007-01-16 0:14 ` Lennart Borgman (gmail)
2007-01-16 7:46 ` martin rudalics
2007-01-16 10:32 ` Lennart Borgman (gmail)
2007-01-16 14:23 ` martin rudalics
2007-01-16 17:59 ` Lennart Borgman (gmail)
2007-01-16 18:32 ` martin rudalics
2007-01-16 18:57 ` Lennart Borgman (gmail)
2007-01-16 21:57 ` martin rudalics
2007-01-16 22:32 ` Lennart Borgman (gmail)
2007-01-17 6:36 ` martin rudalics
-- strict thread matches above, loose matches on Subject: below --
2007-01-13 0:17 Michaël Cadilhac
2007-01-13 0:33 ` Lennart Borgman (gmail)
2007-01-13 0:46 ` Michaël Cadilhac
2007-01-13 1:24 ` Lennart Borgman (gmail)
[not found] ` <mailman.3023.1168651462.2155.help-gnu-emacs@gnu.org>
2007-01-13 6:17 ` Stefan Monnier
2007-01-13 9:20 ` Michaël Cadilhac
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=f7ccd24b0701150550r946ac0dwda4318cca2d7afb9@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael@cadilhac.name \
--cc=rudalics@gmx.at \
/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.
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).