Hello,
Bastien writes:
> In the meantime, what do you think about the solution I propose?
I think it is a sensible move.
Regards,
--
Nicolas Goaziou
Hi Nicolas,
Nicolas Goaziou writes:
>> let's finally close this thread, thanks all for your inputs.
>
> I'm still waiting for Carsten's input, as I need to know whether
> introducing the parser in core functions is a goal for Org or not.
In the meantime, what do you think about the solution I p
Hello,
Bastien writes:
> let's finally close this thread, thanks all for your inputs.
I'm still waiting for Carsten's input, as I need to know whether
introducing the parser in core functions is a goal for Org or not.
Regards,
--
Nicolas Goaziou
Hi all,
let's finally close this thread, thanks all for your inputs.
The solution I suggest is this:
1. implement multi-links opening when C-c C-o is called in a
paragraph and there is no link at point (similar behavior
than the one we have for links in headlines);
2. let `org-open-at-poi
Matt Lundin wrote:
> Nicolas is doing amazing work at making org file parsing more
> systematic, precise, and predictable. (Thank you!) And I agree with him
> that a function named org-open-link-at-point should, for the sake of
> precision and consistency, only open a link at the point.
>
> I also
Hello,
On 3 March 2014 11:09, Matt Lundin wrote:
> Bastien writes:
> >
> > For most commands, the first literal syntactic interpretation is the
> > only relevant context of interaction: e.g., it would not make sense to
> > try updating a tag outside of a headline (i.e. outside of where a tag
>
Matt Lundin writes:
> ...
> My view is that precision and usability need not be mutually
> exclusive.Might we have a bunch of precise, modular functions that
> rely on the new parser? E.g., something like
> org-open-link-at-point. This would do exactly what it says -- i.e.,
> open a link if one i
Bastien writes:
>
> For most commands, the first literal syntactic interpretation is the
> only relevant context of interaction: e.g., it would not make sense to
> try updating a tag outside of a headline (i.e. outside of where a tag
> is a tag, from the parser's view.)
>
> For some commands, anot
Hi Gustav, Josiah and Michael,
thanks *a lot* for your feedback, it triggered an idea I want to turn
into a proposal. I changed the subject of this thread to better frame
the issue at stake, and explain my proposal.
Emacs commands depend on their context: this is the modal approach we
love. For
