Bastien b...@gnu.org writes:
Hi Bastien,
Thorsten Jolitz tjol...@gmail.com writes:
This is quite low level and I haven't done anything on this level yet,
but it might be a way to stick with performant constant regexp strings,
but make them more general.
That's an idea -- but the one I
Hi Thorsten,
Thorsten Jolitz tjol...@gmail.com writes:
One problem is that more and more Org functions seems to get redefined
in terms of the new parser functionality, and obviously then can't be
used anymore outside org-mode.
That's not a problem if we follow the path I suggest: since the
Bastien b...@gnu.org writes:
Hi Bastien,
Thorsten Jolitz tjol...@gmail.com writes:
One problem is that more and more Org functions seems to get redefined
in terms of the new parser functionality, and obviously then can't be
used anymore outside org-mode.
That's not a problem if we follow
Hi Thorsten,
Thorsten Jolitz tjol...@gmail.com writes:
I'm still not sure if this path isn't just the outorg path: copy a
subtree or a whole buffer into a temp-buffer, uncomment the comment
sections, enclose the source-code in source-blocks, and put the buffer
in Org-mode - only that the tmp
Bastien b...@gnu.org writes:
Hi Bastien,
Thorsten Jolitz tjol...@gmail.com writes:
What will be copied to the temp-buffer? Only the comment-section at
point? The subtree at point? The (outcommented) element at point? Won't
some Org functions fail without the subtree/buffer context? What if
Hi Thorsten,
Thorsten Jolitz tjol...@gmail.com writes:
So maybe I should stop insisting on an org-minor-mode, because outshine
and outorg together already do the trick?
Indeed! (Do you have a screencast demonstrating this? It's all a bit
abstract when put in words.)
I just thought it
Bastien b...@gnu.org writes:
Hi Bastien,
Thorsten Jolitz tjol...@gmail.com writes:
So maybe I should stop insisting on an org-minor-mode, because outshine
and outorg together already do the trick?
Indeed! (Do you have a screencast demonstrating this? It's all a bit
abstract when put in
Bastien b...@gnu.org writes:
Hi Bastien,
Thorsten Jolitz tjol...@gmail.com writes:
Thats currently possible with outorg.el, M-# M-# on a outshine subtree
or buffer is just the reverse of C-c ' on a source-block - it offers the
subtree of buffer in a temporary *outorg-edit-buffer* in full
Hi Thorsten,
Thorsten Jolitz tjol...@gmail.com writes:
This is quite low level and I haven't done anything on this level yet,
but it might be a way to stick with performant constant regexp strings,
but make them more general.
That's an idea -- but the one I wanted to explore is this: instead
Hi Thorsten,
Thorsten Jolitz tjol...@gmail.com writes:
I for one need to have a clearer picture of what such a minor mode
would really do, without getting prematurily lost in the details of
possible implementations.
Its just a better and smarter outshine-mode (major-mode agnostic Org
Bastien b...@gnu.org writes:
Hi Bastien,
Thorsten Jolitz tjol...@gmail.com writes:
I for one need to have a clearer picture of what such a minor mode
would really do, without getting prematurily lost in the details of
possible implementations.
Its just a better and smarter outshine-mode
Hi Thorsten
Thorsten Jolitz tjol...@gmail.com writes:
Thats currently possible with outorg.el, M-# M-# on a outshine subtree
or buffer is just the reverse of C-c ' on a source-block - it offers the
subtree of buffer in a temporary *outorg-edit-buffer* in full Org-mode
with the
Bastien b...@gnu.org writes:
Hi Bastien,
Thorsten Jolitz tjol...@gmail.com writes:
So I would rather have a clear picture of the 'political situation' wrt
to org-minor-mode and some technical discussion first. But anyway, I
will not have time to work on this again before June.
I for one
Hi Ilya,
Ilya Shlyakhter ilya...@gmail.com writes:
What would be the downside of abstracting away the headline syntax in
the Org code?
I expect some slow down on core functions -- but I'm not sure.
--
Bastien
Hi Thorsten,
Thorsten Jolitz tjol...@gmail.com writes:
So I would rather have a clear picture of the 'political situation' wrt
to org-minor-mode and some technical discussion first. But anyway, I
will not have time to work on this again before June.
I for one need to have a clearer picture
Ilya Shlyakhter ilya_...@alum.mit.edu writes:
What about using advice on regexp functions to transform the regexps
(when invoked in org-minor-mode buffers) so that $ is replaced with ;
$ etc?
We should absolutely avoid advice in code.
--
Bastien
Bastien b...@gnu.org writes:
We should absolutely avoid advice in code.
Fully agree. (I was thinking of using an flet-like construct to
temporarily rebind functions for the duration of calls, rather than
permanent advice -- see elu-flet in
https://github.com/notestaff/elu/blob/master/elu.el --
Ilya Shlyakhter ilya_...@alum.mit.edu writes:
Hi Ilya,
On 4/10/2014 3:19 PM, Nicolas Goaziou wrote:
I don't see why you would need the full power of Org-mode (whatever
that means) in mere comments.
There are actually many uses, especially if it becomes possible to
treat language elements
Ilya Shlyakhter ilya_...@alum.mit.edu writes:
On 4/19/2014 8:57 AM, Bastien wrote:
Hi Thorsten,
Thorsten Jolitz tjol...@gmail.com writes:
In summary, its about:
1. generalize the regexp constants and vars (allow for comment-syntax,
when org-minor-mode)
2. deal with hardcoded
On 4/19/2014 8:57 AM, Bastien wrote:
Hi Thorsten,
Thorsten Jolitz tjol...@gmail.com writes:
In summary, its about:
1. generalize the regexp constants and vars (allow for comment-syntax,
when org-minor-mode)
2. deal with hardcoded regexp-snippets in functions (my proposoal:
replace ^
On 4/10/2014 3:19 PM, Nicolas Goaziou wrote:
I don't see why you would need the full power of Org-mode (whatever
that means) in mere comments.
There are actually many uses, especially if it becomes possible to treat
language elements (functions, classes etc) as outline elements
(cf.
Bastien b...@gnu.org writes:
Hi Bastien,
Thorsten Jolitz tjol...@gmail.com writes:
The real value and innovation of a true
org-minor-mode would be to introduce Org's intelligent headlines and all
the related functionality into the world of outcommented text in
programming modes.
Yes. We
Samuel Wales samolog...@gmail.com writes:
Hi Samuel,
another option is to create annotation mechanisms that are so
compelling that you don't need org in non-org files.
your lists and tasks would stay in your org agenda files, but your
external files would be able to show (via overlays) and
Hi Thorsten,
Thorsten Jolitz tjol...@gmail.com writes:
In summary, its about:
1. generalize the regexp constants and vars (allow for comment-syntax,
when org-minor-mode)
2. deal with hardcoded regexp-snippets in functions (my proposoal:
replace ^ with org-BOL, $ with org-EOL, \\* with
Thorsten Jolitz tjol...@gmail.com writes:
In the case of regexps its of course not considered bad practice to
write ^foo$ many times in a program, so nobody is to blame here, but
the issue is the same as writing (message What a wonderful world) many
times in a program and then entering a
Thorsten Jolitz tjol...@gmail.com writes:
That means that Org headlines are much more 'intelligent' than outline
headlines (they know about todos, priorities, tags, timestamps,
properties, planning, clocking, being archived etc.) and one could
have that kind of intelligent headlines in other
Bastien b...@gnu.org writes:
Thorsten Jolitz tjol...@gmail.com writes:
That means that Org headlines are much more 'intelligent' than outline
headlines (they know about todos, priorities, tags, timestamps,
properties, planning, clocking, being archived etc.) and one could
have that kind of
Hi Thorsten,
Thorsten Jolitz tjol...@gmail.com writes:
The real value and innovation of a true
org-minor-mode would be to introduce Org's intelligent headlines and all
the related functionality into the world of outcommented text in
programming modes.
Yes. We could have
another option is to create annotation mechanisms that are so
compelling that you don't need org in non-org files.
your lists and tasks would stay in your org agenda files, but your
external files would be able to show (via overlays) and link to the
annotations in org. in turn, your annotations
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
Thorsten Jolitz tjol...@gmail.com writes:
What do you think - is there any chance that Org-mode switches from
static hardcoded regexp strings (all over the place) to dynamic
regexps calculated at runtime (using libraries like drx.el or
Bastien b...@gnu.org writes:
Hi Thorsten,
Nicolas Goaziou n.goaz...@gmail.com writes:
Thorsten Jolitz tjol...@gmail.com writes:
What do you think - is there any chance that Org-mode switches from
static hardcoded regexp strings (all over the place) to dynamic
regexps calculated at
Richard Lawrence richard.lawre...@berkeley.edu writes:
Hi Richard,
Bastien b...@gnu.org writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
Thorsten Jolitz tjol...@gmail.com writes:
What do you think - is there any chance that Org-mode switches from
static hardcoded regexp strings (all
Hi Thorsten,
Nicolas Goaziou n.goaz...@gmail.com writes:
Thorsten Jolitz tjol...@gmail.com writes:
What do you think - is there any chance that Org-mode switches from
static hardcoded regexp strings (all over the place) to dynamic
regexps calculated at runtime (using libraries like drx.el
Hi Thorsten,
Bastien b...@gnu.org writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
Thorsten Jolitz tjol...@gmail.com writes:
What do you think - is there any chance that Org-mode switches from
static hardcoded regexp strings (all over the place) to dynamic
regexps calculated at runtime
Hello,
Thorsten Jolitz tjol...@gmail.com writes:
What do you think - is there any chance that Org-mode switches from
static hardcoded regexp strings (all over the place) to dynamic
regexps calculated at runtime (using libraries like drx.el or rx.el)?
I hope not. The syntax should stabilize,
35 matches
Mail list logo
