From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: [RFC] Sloppy `org-element-context'?
Date: Fri, 28 Mar 2014 10:26:24 +0100 [thread overview]
Message-ID: <87ppl6r7wf.fsf@gmail.com> (raw)
In-Reply-To: <87r45njpgp.fsf@pank.eu> (rasmus@gmx.us's message of "Thu, 27 Mar 2014 22:34:14 +0100")
Hello,
Rasmus <rasmus@gmx.us> writes:
> Would it make sense to make it optional?
I thought about it. But adding an optional argument to determine if
`org-element-context' should be strict or sloppy doesn't help in
practice, since one will probably often wonder if he needs to switch to
sloppy mode or not.
Also, `org-element-context' is not needed for parsing a buffer (with
`org-element-parse-buffer'). Thus, strict behaviour is not mandatory.
> I haven't seen this discussion. I looked briefly at the suggested
> patch; I don't understand why it would be necessary or desirable. But
> I will not rule out that I have yet to consider the correct case!
For example, one may write
:PROPERTIES:
:SOME_LINK: [[my-link:destination]]
:END:
and expect C-c C-o to open the link in the properties drawer. I can see
the practical use, but not at the syntax level, which defines it as
a plain string. Indeed, this can get worse:
:PROPERTIES:
:REMEMBER: <2014-03-28 Fri>
:END:
introduces a timestamp hidden to the user but not to the agenda.
> As a hacker (not quite a developer!), I do at time desire more
> flexibility with org-context to temporarily evaluating an element
> under alternative assumptions of its properties. A recent example
> evaluate $x^{z}$ as-if it isn't a latex-fragment.
I think this would go too far. Considering $x^{z}$ as anything else than
a latex fragment is not a good idea. What is the next step? Should the
snippet $a =b \qquad c= d$ be seen as strike-through?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-03-28 9:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 15:28 Nicolas Goaziou
2014-03-27 21:34 ` Rasmus
2014-03-28 9:26 ` Nicolas Goaziou [this message]
2014-04-19 8:47 ` Bastien
2014-04-19 9:15 ` Nicolas Richard
2014-04-19 9:30 ` Bastien
2014-04-23 20:35 ` Nicolas Goaziou
2014-04-29 21:20 ` Nicolas Goaziou
2014-05-06 9:25 ` Bastien
2014-05-26 15:50 ` Bastien
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=87ppl6r7wf.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
--subject='Re: [RFC] Sloppy `org-element-context'\''?' \
/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
Code repositories for project(s) associated with this 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).