From: Carlos Pita <carlosjosepita@gmail.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: 31921@debbugs.gnu.org
Subject: bug#31921: 26.1.50; Add a convenient way to get flymake error at point
Date: Sat, 23 Jun 2018 14:53:55 -0300 [thread overview]
Message-ID: <CAELgYhdCkg=GPJY4CDijJunGXfB=CXoQSXMTxUcCUeJgnM5QYg@mail.gmail.com> (raw)
In-Reply-To: <8736xenw7i.fsf@gmail.com>
>> So feel free to close this, but please add something wrt this in the
>> docstring or the info manual.
>
> In that case, it's better not to close it. I've already read this
> complaint/request elsewhere.
I don't know if `C-h .` was intended by design or is the result of
serendipity but it feels like the right solution to me, not as a
workaround or hack. It literally reads as "help at point" and shows
the content of a standard property meant for that. I think it just
needs to be documented. So consider this report a request for
documentation in any case.
> So, if others are reading this, what do you think of making eldoc
> display the diagnostic at point instead of (along with?) whatever it was
> already displaying in the echo area?
Many major modes already use eldoc to show information about the
symbol at point and the echo area is rather disputed by eldoc,
company, etc. I would avoid automatically messaging the error at point
to prevent excessive message switching. But it could be a
customization toggle.
next prev parent reply other threads:[~2018-06-23 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 5:45 bug#31921: 26.1.50; Add a convenient way to get flymake error at point Carlos Pita
2018-06-21 5:54 ` Carlos Pita
2018-06-23 1:11 ` João Távora
2018-06-23 17:53 ` Carlos Pita [this message]
2018-06-25 11:33 ` João Távora
2018-06-25 12:56 ` Dmitry Gutov
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='CAELgYhdCkg=GPJY4CDijJunGXfB=CXoQSXMTxUcCUeJgnM5QYg@mail.gmail.com' \
--to=carlosjosepita@gmail.com \
--cc=31921@debbugs.gnu.org \
--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 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.