emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rustom Mody <rustompmody@gmail.com>
To: emacs-orgmode@gnu.org
Cc: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: continuing about orgalist org-element interaction
Date: Wed, 19 Jun 2024 21:37:36 +0530	[thread overview]
Message-ID: <CAJ+TeocAL29TGp07pkQjAMn9MsJ-NOyYUJzKohdY+aTNGo-nFA@mail.gmail.com> (raw)

I guess in a way the other thread (Sub: orgalist send bug) is done and
orgalist in the new version is usable enough for me that I can live
with the warning.

But I was troubled with the possibility of lots of load path shadows
so I spent some time cleaning up. [In any case since emacs had got
upgraded recently, things like use-package are now in emacs so they
had to be removed. So it's good I did that]

But I felt like still poking around seeing if I could see what's the issue.

I figured its these 5 lines at the start of org-element-at-point

(unless (derived-mode-p 'org-mode)
         (display-warning
          '(org-element org-element-parser)
          (format-message
           "`org-element-at-point' cannot be used in non-Org buffer %S (%s)"
         (current-buffer) major-mode)))

Now the current buffer (in my case) is text-mode, obviously not org
mode so why that check??

Commenting out those lines the error message has gone. (And of course
its still working)

[I also checked that the corresponding send from ORGTBL does NOT
invoke org-element-at-point]

Now obviously I dont understand enough about the innards of org to
make any suggestion to remove as Ive currently tried.
But still there is the question (really for Nicolas)
What is the meaning of ensuring that its org mode and warning
otherwise when orgalist (like orgtbl) are meant specifically for non
org buffers?

Thanks
Rusi


             reply	other threads:[~2024-06-19 16:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 16:07 Rustom Mody [this message]
2024-06-19 16:43 ` continuing about orgalist org-element interaction 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:
  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=CAJ+TeocAL29TGp07pkQjAMn9MsJ-NOyYUJzKohdY+aTNGo-nFA@mail.gmail.com \
    --to=rustompmody@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).