unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: dalanicolai <dalanicolai@gmail.com>
To: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Question about weird vscroll behavior
Date: Sun, 5 Nov 2023 21:17:57 +0100	[thread overview]
Message-ID: <CACJP=3m=8TbFcRQvq63FZTNLPfkYL3EAcs2Lj-ZLzshRNmgX4A@mail.gmail.com> (raw)
In-Reply-To: <CACJP=3kswyxUVjYp75mYp2QQYaWXAUy7ivMg2k4-UHWTFfiXDg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1846 bytes --]

Hi all,

If there is anybody on Fedora here, could you please try to evaluate the
code
from the original message starting from emacs -Q, and afterwards check what
is the value of

M-: (window-vscroll nil t)
>

Do you get 0 or 300?

For some reason this does not work here. I have just built emacs from `HEAD`
without using any `configure` flags. It does not work here, neither on
emacs 28.3, 29.1 or on the latest 30.5.

I have also tried on Ubuntu on another laptop, where the code works fine.
Would be great if possible.

Thanks!

On Sun, 5 Nov 2023 at 19:14, dalanicolai <dalanicolai@gmail.com> wrote:

> Haha, okay Eli. It was just to be sure, because otherwise I have
> no idea why setting the vscroll using the above code, does not
> work here.
>
> I have tried with the Fedora system Emacs 28.3, and with my own
> build of Emacs 29.1 (with PGTK, but I guess that is the default now
> on Emacs 29). Also, I have tried on wayland and x-org. But the code
> does not set the vscroll when starting from emacs -Q, while, strangely
> it works when I load my configuration.
>
> Anyway, I guess I have to investigate some more then.
>
> Thanks a lot for checking!
>
>
> On Sun, 5 Nov 2023 at 18:01, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> > From: dalanicolai <dalanicolai@gmail.com>
>> > Date: Sun, 5 Nov 2023 17:36:26 +0100
>> > Cc: emacs-devel@gnu.org
>> >
>> > I just realized I forgot to be clear about my question.
>> > The problem is that after evaluating the code, here,
>> > after starting from emacs -Q, the vscroll value is still
>> > zero.
>> >
>> > So I was wondering what is the value when doing
>> >
>> >  M-: (window-vscroll nil t)
>> >
>> > after evaluating the example code.
>> >
>> > So Eli, when you say it works, do you mean that
>> > vscroll value is 300?
>>
>> Of course!  How else could I have claimed that "it works"?
>>
>

[-- Attachment #2: Type: text/html, Size: 3149 bytes --]

  reply	other threads:[~2023-11-05 20:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-05 15:49 Question about weird vscroll behavior dalanicolai
2023-11-05 16:20 ` Eli Zaretskii
2023-11-05 16:36   ` dalanicolai
2023-11-05 17:01     ` Eli Zaretskii
2023-11-05 18:14       ` dalanicolai
2023-11-05 20:17         ` dalanicolai [this message]
2023-11-10 18:51           ` dalanicolai
2023-11-10 19:49             ` 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='CACJP=3m=8TbFcRQvq63FZTNLPfkYL3EAcs2Lj-ZLzshRNmgX4A@mail.gmail.com' \
    --to=dalanicolai@gmail.com \
    --cc=emacs-devel@gnu.org \
    /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).