all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: <jsj.register@gmail.com>
To: "phillip.lord@russet.org.uk" <phillip.lord@russet.org.uk>,
	 "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Regarding performance issues with the Emacs 25.1 Windows-build
Date: Sun, 8 Jan 2017 22:33:27 -0800	[thread overview]
Message-ID: <58732ebd.8778630a.25994.c3c9@mx.google.com> (raw)

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

Hi,

I encountered huge lags when using org mode (detailed below) on build “emacs-25.1-2-x86_64-w64-mingw32.zip” with “emacs-25-x86_64-deps.zip” (from ftp.gnu.org).
With the same configuration and the same org file, everything is fine on Mac (emacs 25) and on Windows (emacs 24.5), so I think I might post is here. I am sorry if this is the wrong place.

Reproducing it is a little bit tricky.
It seems to happen when certain utf8 symbols are displayed in the buffer.
By saying "certain utf8 symbols”, I refer to those that are not with the common width, so it depends on the font you are using.
What I did is the following.

I am using the latest org mode (version 9) and have turned on “org-pretty-entities” , which replaces some latex codes (eg. \alpha) with their corresponding utf-8 symbols.
The font I use in emacs is “Hack”. With this font, greek letters are all OK, they have the same width as the English letters.
One example to show the lag is “\gg”.
Simply open an org file and put in “\gg” followed by a space and some other letters. “\gg” will be displayed as a utf8 symbol.
Then try to move the cursor quickly. You should experience huge lags.

Any help is appreciated.

Best,
jsj

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

             reply	other threads:[~2017-01-09  6:33 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-09  6:33 jsj.register [this message]
2017-01-09  7:40 ` Regarding performance issues with the Emacs 25.1 Windows-build Richard Copley
2017-01-10  7:28   ` jsj.register
2017-01-09  7:57 ` Nikolay Kudryavtsev
2017-01-10  7:30   ` jsj.register
  -- strict thread matches above, loose matches on Subject: below --
2016-11-21 23:35 Fernando Febles Armas
2016-11-22  3:44 ` Eli Zaretskii
2016-11-09  8:34 Jostein Kjønigsen
2016-11-09 16:22 ` Eli Zaretskii
2016-11-09 16:55   ` Noam Postavsky
2016-11-09 17:18     ` Eli Zaretskii
2016-11-10 15:16       ` Phillip Lord
2016-11-10 22:04       ` Phillip Lord
2016-11-11  7:56         ` Eli Zaretskii
2016-11-11 20:53           ` Phillip Lord
2016-11-14 15:56             ` Phillip Lord
2016-11-14 16:19               ` Eli Zaretskii
2016-11-14 16:55                 ` Phillip Lord
2016-11-14 18:12                   ` Eli Zaretskii
2016-11-15 10:49                     ` Jostein Kjønigsen
2016-11-15 11:42                       ` Jostein Kjønigsen
2016-11-15 13:17                         ` Phillip Lord
2016-11-15 13:30                           ` Jostein Kjønigsen
2016-11-15 15:17                             ` Eli Zaretskii
2016-11-15 15:39                               ` Jostein Kjønigsen
2016-11-20  9:31                                 ` Phillip Lord
2016-11-29 18:26                                   ` Jostein Kjønigsen
2016-11-29 21:47                                     ` Phillip Lord
2016-11-30  7:56                                       ` Fabrice Popineau
2016-11-30  8:36                                         ` Jostein Kjønigsen
2016-11-30 12:51                                           ` Fabrice Popineau
2016-11-30 20:11                                           ` Richard Stallman
2016-11-30 14:48                                         ` Eli Zaretskii
2016-12-09 21:09                                           ` Fabrice Popineau
2016-12-12 17:18                                             ` Phillip Lord
2016-11-11 19:13         ` Jostein Kjønigsen
2016-11-09 17:21   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=58732ebd.8778630a.25994.c3c9@mx.google.com \
    --to=jsj.register@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=phillip.lord@russet.org.uk \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.