unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jake Goulding <jake.goulding@gmail.com>
Cc: 30320@debbugs.gnu.org
Subject: bug#30320: 26.0.91; Crash when using lsp-ui-doc-mode
Date: Sat, 03 Feb 2018 22:10:23 +0200	[thread overview]
Message-ID: <83mv0pal74.fsf@gnu.org> (raw)
In-Reply-To: <CAEDNNqDodquNwdTHhyfjPiC1ScTWUeeCMKbxYCQWfJAK_ZaSDA@mail.gmail.com> (message from Jake Goulding on Sat, 3 Feb 2018 14:43:50 -0500)

> From: Jake Goulding <jake.goulding@gmail.com>
> Date: Sat, 3 Feb 2018 14:43:50 -0500
> 
> My earlier email included a screenshot in an attempt to show what
> I see. It appears to have been added to the bug report:
> 
> https://debbugs.gnu.org/cgi/bugreport.cgi?msg=23;att=2;filename=Screen+Shot+2018-02-02+at+11.19.02+AM.png;bug=30320

You are right, I missed that somehow.  Sorry about that.

> I see nothing that appears to be 3 rows tall.

Doesn't look that way.  So it means somehow the correct value got
overwritten(?).  Next thing I'd try is run Emacs with a watchpoint on
(tty)->Wcm->cm_rows, that should show us what code changes the value.

> I did not change anything to be `text-mode`.

Your whole session is text-mode, i.e. non-GUI.

Thanks.





  reply	other threads:[~2018-02-03 20:10 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-01 15:10 bug#30320: 26.0.91; Crash when using lsp-ui-doc-mode Jake Goulding
2018-02-01 17:16 ` Eli Zaretskii
2018-02-01 19:52   ` Jake Goulding
2018-02-01 19:54     ` Jake Goulding
2018-02-02  8:21     ` Eli Zaretskii
2018-02-02 16:22       ` Jake Goulding
2018-02-03  9:04         ` martin rudalics
2018-02-03 16:10           ` Jake Goulding
2018-02-03 16:34             ` Eli Zaretskii
2018-02-03 19:43               ` Jake Goulding
2018-02-03 20:10                 ` Eli Zaretskii [this message]
2018-02-03 21:55                   ` Jake Goulding
2018-02-04 18:35                     ` Eli Zaretskii
2018-02-04 21:08                       ` Jake Goulding
2018-02-04 21:38                         ` Jake Goulding
2018-02-05 17:03                           ` Eli Zaretskii
2018-02-05 18:43                             ` Jake Goulding
2018-02-05 20:14                               ` Eli Zaretskii
2018-02-06  9:29                             ` martin rudalics
2018-02-10 10:14                               ` Eli Zaretskii
2018-02-10 10:45                                 ` martin rudalics
2018-02-10 12:11                                   ` Eli Zaretskii
2018-02-10 13:40                                     ` martin rudalics
2018-02-10 16:38                                       ` Eli Zaretskii
2018-02-11  9:36                                         ` martin rudalics
2018-02-11 15:43                                           ` Eli Zaretskii
2018-02-12  1:31                                             ` Jake Goulding
2018-02-12  1:33                                               ` Jake Goulding
2018-02-12  1:48                                                 ` Jake Goulding
2018-02-12  9:24                                                   ` martin rudalics
2019-10-30 11:06                                                     ` Lars Ingebrigtsen
2018-02-12  9:22                                                 ` martin rudalics
2018-02-12  9:22                                               ` martin rudalics
2018-02-12  9:22                                             ` martin rudalics
2018-02-12 18:04                                               ` Eli Zaretskii
2018-02-10 19:04                                 ` Jake Goulding
2018-02-02  8:27 ` martin rudalics

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=83mv0pal74.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=30320@debbugs.gnu.org \
    --cc=jake.goulding@gmail.com \
    /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).