emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Alejandro Pérez Carballo" <apcarballo@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Prompted to submit (unsure what happened) [9.5.2 (9.5.2-g072523 @ /Users/apc/.emacs.d/straight/build/org/)]
Date: Thu, 24 Feb 2022 14:48:28 -0800	[thread overview]
Message-ID: <B2087B46-0ACD-48FA-9F47-D05820AA2A0B@gmail.com> (raw)
In-Reply-To: <CFDA3F6A-8EAD-4883-BB6A-C583134A47F5@gmail.com>

One more question: wouldn't replacing `org-in-src-block-p' with a function that calls `org-in-src-block-p' only when in org-mode and returns `nil' elsewhere suffice to make something that's like `org-in-src-block-p' but that will work outside org-mode? E.g.: 

(defun my/org-in-src-block-p (&optional arg)
  (if (derived-mode-p 'org-mode)

I'm using this for now as a replacement and it seems to do the trick, at least for my present purposes. 



> On Feb 24, 2022, at 11:27 AM, Alejandro Pérez Carballo <apcarballo@gmail.com> wrote:
> I found the source of the problem. I was trying to disable `electric-quote-mode' when in a src block, and found this snippet somewhere: 
> ```
> (add-hook 'electric-quote-inhibit-functions #'org-in-src-block-p)
> ```
> Any thoughts on alternative ways of achieving similar behavior? Presumably I'd need to find a way to make `electric-quote-inhibit-functions` vary depending on whether I am in org-mode. But I'm very much an Elisp illiterate, so I'd appreciate any suggestions here. 
> Best, 
> Alejandro
>> On Feb 24, 2022, at 5:39 AM, Ihor Radchenko <yantar92@gmail.com> wrote:
>> Alejandro Pérez Carballo <apcarballo@gmail.com> writes:
>>> Sorry about the unclear report. I was indeed _not_ in an org buffer. I do not think I was using minibuffer completion, but I cannot remember. I now just got a similar error message, this time when working on an Elisp buffer. The error message says: 
>>> Warning (org-element-cache): org-element--cache: Org parser error in setup-biblio.el::5918. Resetting.
>>> The error was: (error "rx ‘**’ range error")
>>> Backtrace:
>>> "  backtrace-to-string(nil)
>>> org-element-at-point()
>>> org-in-src-block-p()
>>> run-hook-with-args-until-success(org-in-src-block-p)
>>> electric-quote-post-self-insert-function()
>>> self-insert-command(1 34)
>>> funcall-interactively(self-insert-command 1 34)
>>> call-interactively(self-insert-command nil nil)
>>> command-execute(self-insert-command)
>>> "
>> Thanks for the backtrace! It is very clear that something in 
>> electric-quote-mode-hook (or maybe in electric-quote-inhibit-functions)
>> is calling org-in-src-block-p.
>> org-in-src-block-p does not work outside Org mode. It used to (at least,
>> it did not throw an error), but it is not the case anymore and it was
>> never guaranteed that Org functions can reliably work outside Org mode.
>> I do not see explicit customisation adding org-in-src-block-p in your
>> config from the first email. I presume that some third-party package is
>> adding org-in-src-block-p to electric-quote-mode. I would first try to
>> check the values of electric-quote-inhibit-functions and
>> electric-quote-mode-hook and check if they contain org-* staff. Then, I
>> would bisect the config to find out which package is doing it. What you
>> are seeing is a bug in that package and should be reported.
>> Best,
>> Ihor

  reply	other threads:[~2022-02-24 22:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22 20:55 [BUG] Prompted to submit (unsure what happened) [9.5.2 (9.5.2-g072523 @ /Users/apc/.emacs.d/straight/build/org/)] Alejandro Pérez Carballo
2022-02-23  5:06 ` Ihor Radchenko
2022-02-24  1:52   ` Alejandro Pérez Carballo
2022-02-24 13:39     ` Ihor Radchenko
2022-02-24 19:27       ` Alejandro Pérez Carballo
2022-02-24 22:48         ` Alejandro Pérez Carballo [this message]
2022-02-26  7:23           ` Ihor Radchenko

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:

  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=B2087B46-0ACD-48FA-9F47-D05820AA2A0B@gmail.com \
    --to=apcarballo@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \


* 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


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).