From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: alexanderm@web.de, 27427@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#27427: 26.0.50; Native line numbers lead to display error in company-mode popup
Date: Thu, 29 Jun 2017 19:29:58 +0300 [thread overview]
Message-ID: <83d19mrc3d.fsf@gnu.org> (raw)
In-Reply-To: <5954A995.9@gmx.at> (message from martin rudalics on Thu, 29 Jun 2017 09:17:41 +0200)
> Date: Thu, 29 Jun 2017 09:17:41 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: dgutov@yandex.ru, alexanderm@web.de, 27427@debbugs.gnu.org
>
> So the answer to your question is: We can supply any restrictions the
> TTY display code would need although I'd prefer to call this a "special
> kind of frame" and not a "special kind of window".
I prefer "window" for the simple reason that doing so will most
probably wreak the least havoc on TTY display, in particular because
it won't invalidate the assumption that only one frame is visible at
any given time. Also, frames can have decorations, even on a TTY,
which we are better without in this case. And finally, you most
probably remember that TTY redisplay is frame-based, so having just
one of them would fit better.
Should be a nice project. Any takers?
next prev parent reply other threads:[~2017-06-29 16:29 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 16:50 bug#27427: 26.0.50; Native line numbers lead to display error in company-mode popup Alexander Miller
2017-06-19 17:08 ` Eli Zaretskii
[not found] ` <6b307502-53db-e92d-1050-3cf0132537cb@web.de>
2017-06-19 19:23 ` Eli Zaretskii
2017-06-19 19:53 ` Alexander Miller
2017-06-19 21:03 ` Dmitry Gutov
2017-06-20 15:04 ` Eli Zaretskii
2017-06-21 2:18 ` Dmitry Gutov
2017-06-21 2:40 ` Eli Zaretskii
2017-06-21 13:04 ` Dmitry Gutov
2017-06-21 15:51 ` Alexander Miller
2017-06-21 18:15 ` Eli Zaretskii
2017-06-21 22:41 ` Dmitry Gutov
2017-06-22 14:55 ` Eli Zaretskii
2017-06-22 23:17 ` Dmitry Gutov
2017-06-23 9:10 ` Eli Zaretskii
2017-06-23 23:26 ` Dmitry Gutov
2017-06-24 7:47 ` Eli Zaretskii
2017-06-24 17:28 ` Eli Zaretskii
2017-06-24 20:43 ` Dmitry Gutov
2017-06-25 13:51 ` Dmitry Gutov
2017-06-25 14:32 ` Eli Zaretskii
2017-06-25 14:36 ` Dmitry Gutov
2017-06-25 14:13 ` Eli Zaretskii
2017-06-25 14:46 ` Dmitry Gutov
2017-06-25 15:05 ` Eli Zaretskii
2017-06-25 16:35 ` Eli Zaretskii
2017-06-25 17:57 ` Eli Zaretskii
2017-06-25 22:56 ` Dmitry Gutov
2017-06-26 8:23 ` martin rudalics
2017-06-26 15:07 ` Eli Zaretskii
2017-06-27 7:06 ` martin rudalics
2017-06-27 14:48 ` Eli Zaretskii
2017-06-26 15:22 ` Eli Zaretskii
2017-06-26 15:28 ` Dmitry Gutov
2017-06-26 15:50 ` Eli Zaretskii
2017-06-26 17:12 ` Dmitry Gutov
2017-06-26 21:30 ` Johan Bockgård
2017-06-27 16:47 ` Eli Zaretskii
2017-07-13 23:04 ` Dmitry Gutov
2017-07-14 6:11 ` Eli Zaretskii
2017-07-14 6:24 ` Dmitry Gutov
2017-07-14 7:04 ` Eli Zaretskii
2017-07-15 17:38 ` Dmitry Gutov
2017-07-15 17:49 ` Eli Zaretskii
2017-06-25 14:31 ` Dmitry Gutov
2017-06-25 14:54 ` Eli Zaretskii
2017-06-25 15:25 ` Dmitry Gutov
2017-06-25 16:12 ` martin rudalics
2017-06-25 18:21 ` Eli Zaretskii
2017-06-25 15:59 ` martin rudalics
2017-06-25 16:24 ` Dmitry Gutov
2017-06-25 17:10 ` martin rudalics
2017-06-25 18:36 ` Eli Zaretskii
2017-06-25 18:51 ` Eli Zaretskii
2017-06-26 8:21 ` martin rudalics
2017-06-26 8:18 ` martin rudalics
2017-06-25 18:24 ` Eli Zaretskii
2017-06-26 7:15 ` martin rudalics
2017-06-26 8:18 ` martin rudalics
2017-06-26 12:07 ` Dmitry Gutov
2017-06-26 15:05 ` Eli Zaretskii
2017-06-27 7:06 ` martin rudalics
2017-06-27 14:48 ` Eli Zaretskii
2017-06-27 15:27 ` martin rudalics
2017-06-27 16:27 ` Eli Zaretskii
2017-06-28 8:45 ` martin rudalics
2017-06-28 16:48 ` Eli Zaretskii
2017-06-28 18:35 ` martin rudalics
2017-06-28 18:56 ` Eli Zaretskii
2017-06-29 7:17 ` martin rudalics
2017-06-29 16:29 ` Eli Zaretskii [this message]
2017-06-30 8:27 ` martin rudalics
2017-06-30 9:33 ` Eli Zaretskii
2017-07-01 10:31 ` martin rudalics
2017-07-01 11:59 ` Eli Zaretskii
2017-07-01 13:22 ` martin rudalics
2017-07-01 13:33 ` Eli Zaretskii
2017-07-01 15:20 ` martin rudalics
2017-07-01 15:41 ` Eli Zaretskii
2017-07-02 7:54 ` martin rudalics
2017-07-02 14:10 ` Eli Zaretskii
2017-07-02 14:45 ` Dmitry Gutov
2017-07-02 15:18 ` Eli Zaretskii
2017-07-03 0:22 ` Dmitry Gutov
2017-07-03 2:29 ` Eli Zaretskii
2017-07-06 7:08 ` martin rudalics
2017-07-06 13:06 ` Dmitry Gutov
2017-07-07 6:52 ` martin rudalics
2017-07-06 7:08 ` martin rudalics
2017-07-06 15:21 ` Eli Zaretskii
2017-07-07 6:52 ` martin rudalics
2017-06-29 1:34 ` Dmitry Gutov
2017-06-29 16:20 ` Eli Zaretskii
2017-06-29 17:55 ` Dmitry Gutov
2017-06-25 19:00 ` Eli Zaretskii
2017-06-26 8:21 ` martin rudalics
2017-06-26 15:06 ` 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=83d19mrc3d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=27427@debbugs.gnu.org \
--cc=alexanderm@web.de \
--cc=dgutov@yandex.ru \
--cc=rudalics@gmx.at \
/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).