unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Markus Triska <triska@metalevel.at>
Cc: 34038@debbugs.gnu.org
Subject: bug#34038: 26.1; set-window-start sometimes fails to set window start
Date: Fri, 11 Jan 2019 08:37:53 -0800 (PST)	[thread overview]
Message-ID: <8328cef7-c568-469d-a9bb-4fd6825131ee@default> (raw)
In-Reply-To: <<83sgxzhe04.fsf@gnu.org>>

> > Is there a way to reliably set the window-start in such situations?
> 
> I think this happens because you call set-window-start with last
> argument non-nil.  Doing that tells the display engine that the
> window-start point is just a suggestion, not a hard requirement.

Sorry for jumping in here ignorantly.  I just looked
at the doc string for `set-window-start' and got a
very different impression of what that 3rd arg means.
Am I mistaken?  How to reconcile your description
with what the doc string says?

  Optional third arg NOFORCE non-nil inhibits next
  redisplay from overriding motion of point in order
  to display at this exact start.





       reply	other threads:[~2019-01-11 16:37 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<m2ftu05lqv.fsf@metalevel.at>
     [not found] ` <<83sgxzhe04.fsf@gnu.org>
2019-01-11 16:37   ` Drew Adams [this message]
2019-01-11 16:49     ` bug#34038: 26.1; set-window-start sometimes fails to set window start Eli Zaretskii
2019-01-10 19:57 Markus Triska
2019-01-11  7:03 ` Eli Zaretskii
2019-01-11 12:20   ` Markus Triska
2019-01-11 13:36     ` Eli Zaretskii
2019-01-11 14:31       ` Markus Triska
2019-01-11 15:10         ` martin rudalics
2019-01-11 17:45           ` Markus Triska
2019-01-11 19:07             ` Eli Zaretskii
2019-01-12  8:12             ` martin rudalics
2019-01-12 13:25               ` Markus Triska
2019-01-12 13:53                 ` Eli Zaretskii
2019-01-12 14:12                 ` martin rudalics
2019-01-12 19:08                   ` Markus Triska
2019-01-12 20:28                     ` Eli Zaretskii
2019-01-11 21:23     ` Alan Mackenzie
2019-01-12  8:13       ` martin rudalics
2019-01-12 18:22         ` Alan Mackenzie
2019-01-12 20:29           ` Eli Zaretskii
2019-01-12 20:42             ` Alan Mackenzie
2019-01-13  3:30               ` Eli Zaretskii
2019-01-13  7:32       ` Markus Triska
2019-01-13  8:40         ` martin rudalics
2019-01-13 11:32           ` Eli Zaretskii
2019-01-13 13:40             ` martin rudalics
2019-01-13 15:21               ` Eli Zaretskii
2019-03-24 10:35                 ` Markus Triska
2019-03-24 17:28                   ` Eli Zaretskii
2019-03-24 19:56                     ` Markus Triska
2019-03-28 16:21                       ` Eli Zaretskii
2019-03-29  7:16                         ` Markus Triska
2019-03-29  8:29                           ` Eli Zaretskii
2019-04-06  8:23                             ` Eli Zaretskii

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=8328cef7-c568-469d-a9bb-4fd6825131ee@default \
    --to=drew.adams@oracle.com \
    --cc=34038@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=triska@metalevel.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).