From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 19661@debbugs.gnu.org
Subject: bug#19661: wrapping before window-width (new wrap-column text property?)
Date: Sun, 25 Jan 2015 20:00:39 +0200 [thread overview]
Message-ID: <83mw56rb94.fsf@gnu.org> (raw)
In-Reply-To: <54C52BFA.1080308@gmx.at>
> Date: Sun, 25 Jan 2015 18:46:34 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: 19661@debbugs.gnu.org
>
> > Sorry for being dense, this being just the first weekday for me, but
> > what "windows code" does that, please?
>
> The one that calculates the text size of windows.
OK, but I fail to see how this, or anything similar, can provide the
features being discussed.
> > In any case, telling the display engine where to start the display is
> > a far cry from telling it how to lay out the screen from that point
> > onwards.
>
> My point was to _not_ change the code of the display engine.
Why not?
> > Providing an API is not equivalent to implementing it. In order for
> > us to be able to provide such an API, the display engine should
> > implement the support such an API will need. And that's the hard part
> > of the job -- how to perform this layout. Once we figure that out,
> > providing an API for controlling it will be easy.
>
> It essentially would have to subdivide a window into rectangles. And I
> would do that on the window(s) level to avoid the hard part of the job.
Well, like I said, I consider such (ab)using of windows a kludge.
next prev parent reply other threads:[~2015-01-25 18:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP1yDHYm2uJ1fnObdN3F4X44w+9nVxHCaFULH9bM-M8Dz207Mw@mail.gmail.com>
[not found] ` <87ioh4nf8k.fsf@ferrier.me.uk>
[not found] ` <83y4pzptpx.fsf@gnu.org>
[not found] ` <871tnr1gqo.fsf@ferrier.me.uk>
[not found] ` <83bnmvowdb.fsf@gnu.org>
[not found] ` <jwvppbab8xb.fsf-monnier+emacs@gnu.org>
[not found] ` <83ppbanqhe.fsf@gnu.org>
[not found] ` <87vbl2xigp.fsf@ferrier.me.uk>
[not found] ` <83ioh2nlow.fsf@gnu.org>
[not found] ` <87sig6xech.fsf@ferrier.me.uk>
[not found] ` <83fvc5ni0u.fsf@gnu.org>
[not found] ` <E1Y4AVO-00035n-PI@fencepost.gnu.org>
[not found] ` <87k31fwwyv.fsf@ferrier.me.uk>
[not found] ` <E1Y4Snj-0004wy-PF@fencepost.gnu.org>
[not found] ` <87bnmq9ibf.fsf@ferrier.me.uk>
[not found] ` <E1Y50Fd-0003BE-GC@fencepost.gnu.org>
[not found] ` <jwv3880fumd.fsf-monnier+emacs@gnu.org>
[not found] ` <87lhlrx5fc.fsf@building.gnus.org>
[not found] ` <jwvfvbzh54s.fsf-monnier+emacs@gnu.org>
[not found] ` <878uhrcr5l.fsf@building.gnus.org>
[not found] ` <83sifzjflk.fsf@gnu.org>
2014-12-29 7:55 ` bug#19462: shr: use wrap-prefix when possible, instead of filling the text Ivan Shmakov
[not found] ` <87egric2ki.fsf_-_@violet.siamics.net>
2014-12-29 9:55 ` Ivan Shmakov
[not found] ` <jwvtx0eee66.fsf-monnier+emacs@gnu.org>
[not found] ` <877fxaa49w.fsf@violet.siamics.net>
[not found] ` <831tnicji7.fsf@gnu.org>
[not found] ` <jwviogtdei4.fsf-monnier+emacs@gnu.org>
[not found] ` <83y4pp9dku.fsf@gnu.org>
[not found] ` <87387w8r2j.fsf@violet.siamics.net>
2015-01-23 13:17 ` bug#19661: wrapping before window-width (new wrap-column text property?) Ivan Shmakov
2015-01-23 16:11 ` Eli Zaretskii
2015-01-23 16:55 ` martin rudalics
2015-01-23 19:11 ` Ivan Shmakov
2015-01-24 9:08 ` martin rudalics
2015-01-23 20:22 ` Eli Zaretskii
2015-01-24 9:08 ` martin rudalics
2015-01-24 9:47 ` Eli Zaretskii
2015-01-25 10:38 ` martin rudalics
2015-01-25 15:50 ` Eli Zaretskii
2015-01-25 17:46 ` martin rudalics
2015-01-25 18:00 ` Eli Zaretskii [this message]
2015-01-23 19:45 ` Ivan Shmakov
2015-01-23 21:17 ` Eli Zaretskii
2015-01-27 22:47 ` Ivan Shmakov
2015-12-25 17:34 ` bug#19462: shr: use wrap-prefix when possible, instead of filling the text Lars Ingebrigtsen
2015-12-26 9:13 ` Ivan Shmakov
[not found] ` <87bn9ezb2h.fsf@gnus.org>
[not found] ` <567D8E43.8030408@gmail.com>
[not found] ` <87y4ciwe6g.fsf@gnus.org>
[not found] ` <567DC781.8040306@gmail.com>
2015-12-25 22:51 ` Lars Ingebrigtsen
2015-12-26 16:53 ` Clément Pit--Claudel
2015-12-27 3:36 ` Clément Pit--Claudel
2015-12-27 4:19 ` Clément Pit--Claudel
2015-12-27 6:22 ` Lars Ingebrigtsen
2015-12-27 11:16 ` Clément Pit--Claudel
2015-12-27 6:19 ` Lars Ingebrigtsen
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=83mw56rb94.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19661@debbugs.gnu.org \
--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.
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).