unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "David M. Karr" <davidmichaelkarr@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs (nowindows) get confused about line display
Date: Fri, 20 May 2016 17:51:10 -0700	[thread overview]
Message-ID: <573FB0FE.6080205@gmail.com> (raw)
In-Reply-To: <573FAF95.2060203@gmail.com>

On 05/20/2016 05:45 PM, David M. Karr wrote:
> On 05/20/2016 04:28 PM, Emanuel Berg wrote:
>> "David M. Karr" <davidmichaelkarr@gmail.com>
>> writes:
>>
>>> On my CentOS laptop, I have a CentOS VM that
>>> I created with Vagrant. I have Emacs 24.3.1
>>> on the VM.
>>>
>>> I start a terminal window on the laptop and ssh
>>> to the VM. I run Emacs, but I don't have X11,
>>> so it's in "no windows" mode.
>>>
>>> Sometimes, when I start emacs on the VM, it
>>> starts up fine and displays properly.
>>>
>>> Quite often, and pretty continuously when it
>>> gets into this state, it will start up with
>>> a blank editor view, with no menu bar, and
>>> the cursor displays on the SECOND line of the
>>> window. When I then view or edit files, it
>>> appears that Emacs is confused about its line
>>> rendering. The cursor appears at the bottom
>>> of the window, even though it "thinks" it's
>>> on the top line of the file I'm viewing.
>>> I can scroll the cursor to the right, and it
>>> will jump back to the beginning when it
>>> reaches the length of the first line, and
>>> so on.
>>>
>>> Emacs is completely useless in this state.
>>>
>>> What can I do at this point?
>> You can analyze the whole chain of invocation.
>> What is the terminal emulator, shell, ssh
>> command, and Emacs invocation command? And if
>> you have tmux or something to that extent in
>> between any of those, that can influence, also.
>>
> Ok, well, $TERM appears to be "xterm-256color", shell is bash, I got 
> there with "vagrant ssh", and I execute Emacs with "emacs".
>
> That gave me the idea to run "emacs -q", and that does provide a 
> clue.  The display is fine after that, but when I load my .emacs after 
> the fact (eval-current-buffer), it's then messed up.  Before I do a 
> binary search to narrow down what initially creates the symptom, are 
> there any other guidelines for narrowing down something like this?
Actually, narrowing it down didn't take very long, but I'd still like to 
understand this better.

The 2-3rd line of my .emacs file has this:
--------------------------
(set-frame-position (selected-frame) 0 0)
(set-frame-height (selected-frame) 60)
----------------

This is obviously not relevant in a emacs-nw situation, but I copied 
this from my "home" .emacs file.  Why would this cause the symptom that 
I'm seeing?

It's easy enough to wrap this with a "(display-graphic-p)" call, but I'd 
like to understand why this is happening.



  reply	other threads:[~2016-05-21  0:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-20 21:28 Emacs (nowindows) get confused about line display David M. Karr
2016-05-20 23:28 ` Emanuel Berg
2016-05-21  0:45   ` David M. Karr
2016-05-21  0:51     ` David M. Karr [this message]
2016-05-21  1:19       ` John Mastro
2016-05-21  6:42         ` Eli Zaretskii
     [not found]   ` <mailman.9.1463791518.1216.help-gnu-emacs@gnu.org>
2016-05-21  2:36     ` Emanuel Berg

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=573FB0FE.6080205@gmail.com \
    --to=davidmichaelkarr@gmail.com \
    --cc=help-gnu-emacs@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.
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).