[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Implementing child frames on terminal
From: |
Po Lu |
Subject: |
Re: Implementing child frames on terminal |
Date: |
Tue, 12 Jul 2022 13:13:01 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.91 (gnu/linux) |
Akib Azmain Turja <akib@disroot.org> writes:
> Your idea is good, but until the child frame crosses the edges of it's
> parent. Then it'll cause a segmentation fault (the best case) or
> continue without any symptom and corrupt your files or something else
> silently (the worst case).
Fixing that (assuming you clip the contents of the child frame to the
parent) sounds easier than what you propose further on here:
> I think we should somehow render the child frame glyph matrix before
> processing it's parents. Then we can copy the it's glyph matrix to it's
> parent's one. And, in case the child frame doesn't cross parent's
> edges, we can use a floating window (as you suggested) as an
> optimization (although I don't think we need this optimization, since
> terminal don't usually have many characters).
- Implementing child frames on terminal, Akib Azmain Turja, 2022/07/11
- Re: Implementing child frames on terminal,
Po Lu <=
- Re: Implementing child frames on terminal, Eli Zaretskii, 2022/07/12
- Re: Implementing child frames on terminal, Akib Azmain Turja, 2022/07/12
- Re: Implementing child frames on terminal, Eli Zaretskii, 2022/07/12
- Re: Implementing child frames on terminal, Akib Azmain Turja, 2022/07/13
- Re: Implementing child frames on terminal, Eli Zaretskii, 2022/07/13