unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: "João Távora" <joaotavora@gmail.com>
Cc: 62029@debbugs.gnu.org, Yuan Fu <casouri@gmail.com>
Subject: bug#62029: 29.0.60; Allow users to customize eldoc buffer separator
Date: Wed, 19 Apr 2023 02:05:43 +0300	[thread overview]
Message-ID: <41f37917-134d-620b-4915-ea34d569a7f9@gutov.dev> (raw)
In-Reply-To: <CALDnm528EAU9FPayHY78s0tzJkhF1S4adPGLikpohcQ1+9Q_Ag@mail.gmail.com>

On 18/04/2023 14:17, João Távora wrote:
> On Tue, Apr 18, 2023 at 1:47 AM Dmitry Gutov <dmitry@gutov.dev> wrote:
> 
>> Here is a minor suggestion:
>>
> 
>> The negative width stops the line height from shifting, and the increase
>> in font size is definitely subjective, but 0.7 really looked too small here.
> 
> Feel free to push that, it makes sense.  But maybe halfway at 0.8?

Split that in half again and pushed 0.85 ;-) Feel free to revert or 
change, of course.

> More seriously though, this clashes with Company's overlay-based
> dropdown, and I don't know how to fix that.> Company makes Flymake's
> end-of-line overlay temporarily invisible, which is good, but
> it still takes a lot of space, so the dropdown is ridiculously
> offset to the right.

Right. Like line numbers or other display-related features.

I'm not sure how to fix that for the overlay popup frontend, but one 
good news is that people can use child frame based ones, those should be 
compatible.

For all other users (like tty ones), also consider a different mode of 
operation: when the corresponding overlay is only shown when point is on 
the error, or mouse hovers over it. That can reduce the odds of conflict 
to the minimum.

This was it would be a straight substitute for help-at-pt and eldoc, for 
flymake's purposes.





      reply	other threads:[~2023-04-18 23:05 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07  7:56 bug#62029: 29.0.60; Allow users to customize eldoc buffer separator Yuan Fu
2023-03-08  0:25 ` bug#62030: " Yuan Fu
2023-03-08 17:14 ` bug#62029: " João Távora
2023-03-08 21:28   ` Yuan Fu
2023-03-23 21:33     ` João Távora
2023-03-24  0:12       ` Yuan Fu
2023-03-24 17:44         ` João Távora
2023-03-25  3:04           ` Yuan Fu
2023-03-25  8:10             ` João Távora
2023-03-30  5:22               ` Yuan Fu
2023-03-30  8:13                 ` João Távora
2023-03-30  8:25                   ` Yuan Fu
2023-04-11  0:04                   ` Dmitry Gutov
2023-04-11 11:25                     ` João Távora
2023-04-12  1:38                       ` Dmitry Gutov
2023-04-12 11:06                         ` João Távora
2023-04-13  0:20                           ` Dmitry Gutov
2023-04-13  4:20                             ` Yuan Fu
2023-04-13  9:50                             ` João Távora
2023-04-13 10:11                               ` João Távora
2023-04-13 10:48                                 ` João Távora
2023-04-13 21:53                               ` Dmitry Gutov
2023-04-13 22:13                                 ` Dmitry Gutov
2023-04-13 23:01                                 ` João Távora
2023-04-13 23:26                                   ` Dmitry Gutov
2023-04-14  0:04                                     ` João Távora
2023-04-14 23:50                                       ` Dmitry Gutov
2023-04-15  9:41                                         ` João Távora
2023-10-23  1:39                                           ` Dmitry Gutov
2023-04-18  0:47                                       ` Dmitry Gutov
2023-04-18 11:17                                         ` João Távora
2023-04-18 23:05                                           ` Dmitry Gutov [this message]

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=41f37917-134d-620b-4915-ea34d569a7f9@gutov.dev \
    --to=dmitry@gutov.dev \
    --cc=62029@debbugs.gnu.org \
    --cc=casouri@gmail.com \
    --cc=joaotavora@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).