[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re:Re: Emacs's set-frame-size can not work well with gnome-shell?
From: |
tumashu |
Subject: |
Re:Re: Emacs's set-frame-size can not work well with gnome-shell? |
Date: |
Thu, 23 Jan 2020 06:30:21 +0800 (CST) |
At 2020-01-23 01:33:25, "martin rudalics" <address@hidden> wrote:
> > Mark set
> > Elapsed time: 0.235007s (0.050980s in 2 GCs)
> > "Elapsed time: 0.235007s (0.050980s in 2 GCs)"
> > Elapsed time: 0.209364s (0.025391s in 1 GCs)
> > "Elapsed time: 0.209364s (0.025391s in 1 GCs)"
> > Mark activated
> > Elapsed time: 0.250710s (0.052309s in 2 GCs)
> > "Elapsed time: 0.250710s (0.052309s in 2 GCs)"
> > Elapsed time: 0.241979s (0.051069s in 2 GCs)
> > "Elapsed time: 0.241979s (0.051069s in 2 GCs)"
> > Mark set
>
>Sorry, what are these numbers? Do they represent GTK builds with the
>same options as the Lucid build that takes 0.684959s? Did you test all
>with emacs -Q in the same buffer and at the same position?
>
Sorry, finally I find it is set-frame-position's reason, it too slow, not
posn-at-point
When I test, I replace posn-at-point to a fix value, and posframe has cached
this value,
not call set-frame-positon, so speed is fast,
>martin
Re: Emacs's set-frame-size can not work well with gnome-shell?, tumashu, 2020/01/22
Re: Emacs's set-frame-size can not work well with gnome-shell?, Eli Zaretskii, 2020/01/22