unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 16649@debbugs.gnu.org, esabof@gmail.com
Subject: bug#16649: Right margin overflows on neighboring windows.
Date: Fri, 07 Feb 2014 13:51:03 +0200	[thread overview]
Message-ID: <83k3d7xhso.fsf@gnu.org> (raw)
In-Reply-To: <52F4C003.5040106@gmx.at>

> Date: Fri, 07 Feb 2014 12:14:11 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: E Sabof <esabof@gmail.com>, 16649@debbugs.gnu.org
> 
>  > Could you please tell what exactly is wrong with display in the above
>  > test case?  And what does "the margin overflows" mean?  Maybe I'm
>  > blind, but I don't see anything wrong when I eval the above code.
> 
> You have to do C-x 3 and enlarge one of the windows to see the effects.

I did, and still didn't see any problems.

Anyway, thanks for taking care of this.

> There were plenty of them - mostly related to not returning the right
> values via window box related functions.  I also now adjust the window
> margins when a window gets to narrow because otherwise the redisplay
> engine gets confused when inserting new text.  Still pretty toothless
> when confronted with more drastic specifications but the best I came up
> with so far.

Any mode that gets to these extreme situations should be shot through
the head.





  reply	other threads:[~2014-02-07 11:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-05  7:41 bug#16649: Right margin overflows on neighboring windows E Sabof
2014-02-05 10:49 ` martin rudalics
2014-02-05 16:20   ` E Sabof
2014-02-07  2:45     ` E Sabof
2014-02-07  7:52       ` Eli Zaretskii
2014-02-07 11:14         ` martin rudalics
2014-02-07 11:51           ` Eli Zaretskii [this message]
2014-02-07 12:06             ` martin rudalics
2014-02-07 11:12       ` martin rudalics
2014-02-21 13:08         ` martin rudalics
2014-02-21 13:16           ` E Sabof

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=83k3d7xhso.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=16649@debbugs.gnu.org \
    --cc=esabof@gmail.com \
    --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).