From: Jake Goulding <jake.goulding@gmail.com>
To: 30320@debbugs.gnu.org
Subject: bug#30320: 26.0.91; Crash when using lsp-ui-doc-mode
Date: Sat, 3 Feb 2018 14:43:50 -0500 [thread overview]
Message-ID: <CAEDNNqDodquNwdTHhyfjPiC1ScTWUeeCMKbxYCQWfJAK_ZaSDA@mail.gmail.com> (raw)
In-Reply-To: <83y3ka9gmg.fsf@gnu.org>
I apologize, but as I mentioned:
> I don't know exactly what the "frame" is in this context.
While I've been /using/ Emacs for ~15 years, that doesn't mean I've
actually become proficient in the myriad of terminology surrounding it
or the subtle differences between Emacs terms and the broader world
(and let's not get started on my near-total lack of Emacs Lisp
ability).
Checking the manual to figure out what a frame is [1], I don't even
believe I've ever attempted to create a frame. I did not provide any
commands to do so this time, either. Perhaps one of the modes in
question has created one?
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
I see nothing that appears to be 3 rows tall. I did not change
anything to be `text-mode`. In case I've misunderstood what a "frame"
is, I also looked at the result of `ibuffer`, I don't see anything in
text-mode.
main.rs 51 Rust /private/tmp/spa/src/main.rs
* *scratch* 476 Lisp Interaction
*% *Messages* 270 Messages
*% *Completions* 976 Completion List
*lsp-rust stderr* 0 Fundamental (lsp-rust stderr open)
[1]: https://www.gnu.org/software/emacs/manual/html_node/emacs/Frames.html
next prev parent reply other threads:[~2018-02-03 19:43 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 [this message]
2018-02-03 20:10 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEDNNqDodquNwdTHhyfjPiC1ScTWUeeCMKbxYCQWfJAK_ZaSDA@mail.gmail.com \
--to=jake.goulding@gmail.com \
--cc=30320@debbugs.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.
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.