From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: org-element-context in table.el behavior
Date: Thu, 02 Jan 2020 11:03:46 -0500 [thread overview]
Message-ID: <m2d0c1x2u5.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <8736cxykt6.fsf@nicolasgoaziou.fr>
Ok, thanks for confirming!
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello,
>
> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
>> I have run into a surprise with org-element-context on a link in a table.el
>> cell. It is best illustrated here:
>>
>> +---+------------+
>> | # | name |
>> +---+------------+
>> | 1 | [[./test.org]] |
>> +---+------------+
>>
>> #+BEGIN_SRC emacs-lisp :results code
>> (save-excursion
>> (re-search-backward (concat "test." "org"))
>> (org-element-context))
>> #+END_SRC
>>
>>
>> #+RESULTS:
>
>> #+begin_src emacs-lisp
>> (table
>> (:begin 1463 :end 1563 :type table\.el :tblfm nil :contents-begin nil
>> :contents-end nil :value "+---+------------+\n| # | name
>> |\n+---+------------+\n| 1 | [[./test.org]] |\n+---+------------+\n"
>> :post-blank 1 :post-affiliated 1463 :parent nil))
>> #+end_src
>>
>
> [...]
>
>> Is this expected behavior, or a bug?
>
> This is expected: table.el tables, as their name suggest, are opaque to
> Org mode. In particular, it doesn't know how to parse them. It just
> feeds table.el with them at export time.
>
> Regards,
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
prev parent reply other threads:[~2020-01-02 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 12:18 org-element-context in table.el behavior John Kitchin
2020-01-02 14:50 ` Nicolas Goaziou
2020-01-02 16:03 ` John Kitchin [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=m2d0c1x2u5.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--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).