emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bruno Cardoso <cardoso.bc@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] lisp/org-eldoc.el: Eldoc does not work in org source blocks
Date: Mon, 29 May 2023 13:24:23 -0300	[thread overview]
Message-ID: <87r0qzp0lk.fsf@gmail.com> (raw)
In-Reply-To: <87v8gbtwha.fsf@localhost>


Sure, fair enough. I am aware this is just a workaround, not an actual solution. Thanks!

Bruno.


On 2023-05-29, 07:42 +0000, Ihor Radchenko <yantar92@posteo.net> wrote:

> Bruno Cardoso <cardoso.bc@gmail.com> writes:
>
>> The Eldoc interface `eldoc-print-current-symbol-info' works everywhere just fine for me (Emacs
>> 28.2), but it does not work inside org source blocks for elisp code. Yet, reverting to the
>> obsolete `elisp-eldoc-documentation-function' in org-eldoc's
>> `org-eldoc-documentation-function' works (see below). I tested it both in my own config and
>> "emacs -Q" with same results.
>
> Note that org-eldoc is not a part of Org. We only provide a minimal
> maintenance until someone takes over it. See
> https://orgmode.org/worg/org-orphanage.html
>
> Your change to obsolete function is questionable. So, this change is at
> least non-trivial. Unfortunately, this falls beyond the level of
> maintenance we can offer here.
>
> -- 
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at <https://orgmode.org/>.
> Support Org development at <https://liberapay.com/org-mode>,
> or support my work at <https://liberapay.com/yantar92>


      reply	other threads:[~2023-05-29 16:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29  0:35 [BUG] lisp/org-eldoc.el: Eldoc does not work in org source blocks Bruno Cardoso
2023-05-29  7:42 ` Ihor Radchenko
2023-05-29 16:24   ` Bruno Cardoso [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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r0qzp0lk.fsf@gmail.com \
    --to=cardoso.bc@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \
    /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/org-mode.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).