unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "RICHARD MUNITZ (BLOOMBERG/ 731 LEXIN)" <rmunitz1@bloomberg.net>
To: eliz@gnu.org
Cc: josh@foxtail.org, 15261@debbugs.gnu.org
Subject: bug#15261: Re: bug#15261: 24.2; Cursor not visible while moving point in transient mark mode
Date: Wed, 4 Sep 2013 20:43:22 -0000	[thread overview]
Message-ID: <52279B6A012800800039203D_0_105803@p057> (raw)
In-Reply-To: <52262A3E01F7038E003915DB_0_85638@p057>

When I log in to the Solaris server through a PuTTY client, I do not experience the problem.  The problem does occur within the Exceed X terminal window if I start Emacs with the -nw option.

----- Original Message -----
From: eliz@gnu.org
To: RICHARD MUNITZ (BLOOMBERG/ 731 LEXIN)
Cc: 15261@debbugs.gnu.org, josh@foxtail.org
At: Sep  4 2013 16:22:06

> Date: Wed, 4 Sep 2013 15:47:56 -0000
> From: "RICHARD MUNITZ (BLOOMBERG/ 731 LEXIN)" <rmunitz1@bloomberg.net>
> Cc: 15261@debbugs.gnu.org
> 
> Client and server machine are LAN connected.  Yes, it is a Solaris server.  A tracert from my machine to the server shows 7 hops, but all under 1ms latency.  
> The reported behavior consistently occurs 100% of the time and has for the 4 weeks I have been working in this environment - including off-hours.  So I don't think bandwidth is a factor either.  
> Note that Bloomberg's core business is distributing real-time market data to the financial industry, so they are rather obsessive about high performance networks.

Does the problem happen for you when you run Emacs locally on that
machine?  Or does it only happen in this particular configuration,
when you use Exceed to access a Solaris server from a Windows machine?

> For comparison, I just tried running gvim and repeated the same "highlight text" test (from top of file I hit "v" (visual mode) and then pressed and held the "j" (down) key. gvim was able to continuously move the cursor and highlight line after line, scrolling screen after screen without ever freezing up. 

Comparisons with gvim are meaningless, because there's no primitive
"highlight this text" operation that both Emacs and gvim use.  Each
one of them highlights text using very different methods.  In Emacs,
the portion of the text that is highlighted is actually fully
redisplayed.

  parent reply	other threads:[~2013-09-04 20:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03 18:28 bug#15261: 24.2; Cursor not visible while moving point in transient mark mode RICHARD MUNITZ (BLOOMBERG/ 731 LEXIN)
2013-09-03 19:25 ` Eli Zaretskii
2013-09-04 15:07   ` Josh
2013-09-04 15:47 ` RICHARD MUNITZ (BLOOMBERG/ 731 LEXIN)
2013-09-04 20:21   ` bug#15261: " Eli Zaretskii
2013-09-05  3:35   ` Josh
2013-09-04 20:43 ` RICHARD MUNITZ (BLOOMBERG/ 731 LEXIN) [this message]
2022-01-30 21:34 ` Lars Ingebrigtsen
2022-02-28  9:53   ` Lars Ingebrigtsen
     [not found] <5227427F0203021400392334_0_59558@p057>
2013-09-04 14:43 ` bug#15261: " 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=52279B6A012800800039203D_0_105803@p057 \
    --to=rmunitz1@bloomberg.net \
    --cc=15261@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=josh@foxtail.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).