Hi Mark,
2014ko abuztuak 2an, Mark Edgington-ek idatzi zuen:
Hi Bastien,
I've attached a patch for ox-extra which doesn't yet include the
option for choosing specific tag names (the 'ignore' tag is currently
hard-coded). Feel free to modify / commit it.
Regards,
Mark
Thanks for
Hi Bastien,
I've attached a patch for ox-extra which doesn't yet include the
option for choosing specific tag names (the 'ignore' tag is currently
hard-coded). Feel free to modify / commit it.
Regards,
Mark
On Tue, Jul 29, 2014 at 10:31 AM, Bastien b...@gnu.org wrote:
Hi Nicolas,
Nicolas
Hi Nicolas,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Filters are _not_ meant to be in core since they are hardly a generic
solution for a class of problem. They are entry points for user-level
hacking. Generic patches should operate at the parse tree level, not
using regexps.
Eric's
Bastien b...@gnu.org writes:
Hi Mark, Aaron, Eric and Nicolas,
Eric Schulte schulte.e...@gmail.com writes:
Please feel free to add this to ox-extras.
I suggest renaming ox-extra.el to ox-filters-extra.el and to have
org-mode/lisp/ox-filters.el for filters that are important enough
to be
Hi Bastien,
On Sun, Jul 27, 2014 at 1:21 PM, Bastien b...@gnu.org wrote:
I suggest renaming ox-extra.el to ox-filters-extra.el and to have
org-mode/lisp/ox-filters.el for filters that are important enough
to be in core.
Your suggestion sounds sensible, but of course I'm biased, as I've
Hi Mark, Aaron, Eric and Nicolas,
Eric Schulte schulte.e...@gmail.com writes:
Please feel free to add this to ox-extras.
I suggest renaming ox-extra.el to ox-filters-extra.el and to have
org-mode/lisp/ox-filters.el for filters that are important enough
to be in core.
I think Eric's filter is
Hi Rasmus,
Rasmus rasmus at gmx.us writes:
Bastien bzg at gnu.org writes:
I think Eric's filter is important enough to be in core, together
with an option to let users decide what tag should be used instead
of ignore (with ignore as a default).
How about ignoreheading as this is
Hello,
Bastien b...@gnu.org writes:
I suggest renaming ox-extra.el to ox-filters-extra.el and to have
org-mode/lisp/ox-filters.el for filters that are important enough
to be in core.
I think Eric's filter is important enough to be in core, together
with an option to let users decide what
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Hello,
Bastien b...@gnu.org writes:
I suggest renaming ox-extra.el to ox-filters-extra.el and to have
org-mode/lisp/ox-filters.el for filters that are important enough
to be in core.
I think Eric's filter is important enough to be in core,
Aaron Ecay aarone...@gmail.com writes:
Hi Eric,
Thanks for your work on this code. Partially inspired by this discussion,
I’ve just created contrib/lisp/ox-extras.el, which I hope will become a
home for useful export hook functions like this one. Would you like to
add your code there (or
Hi Eric,
Thanks for your work on this code. Partially inspired by this discussion,
I’ve just created contrib/lisp/ox-extras.el, which I hope will become a
home for useful export hook functions like this one. Would you like to
add your code there (or would you mind if I did so)?
Thanks,
--
Hello,
Eric Schulte schulte.e...@gmail.com writes:
In my opinion the manual interleaving of noexport and export tags is
overly cumbersome and is non-obvious.
It is as non-obvious as the task it achieves.
The obscure nature of this solution is evidenced by multiple
discussions and
Nicolas Goaziou mail at nicolasgoaziou.fr writes:
Moreover, that task is highly specific; I'm not convinced we should have
a dedicated keyword for each of them. I'd rather have a simple solution
for selective export problems, even if, as a generic solution, it may
look clumsier.
Hi Nicolas,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Hello,
Eric Schulte schulte.e...@gmail.com writes:
In my opinion the manual interleaving of noexport and export tags is
overly cumbersome and is non-obvious.
It is as non-obvious as the task it achieves.
The obscure nature of this solution
Hi,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Hello,
Eric Schulte schulte.e...@gmail.com writes:
Why TODO types rather than a tag? IMO using a TODO type would conflate
task management and document structuring. What do you think about the
attached patch which should add this
Hello,
Eric Schulte schulte.e...@gmail.com writes:
Why TODO types rather than a tag? IMO using a TODO type would conflate
task management and document structuring. What do you think about the
attached patch which should add this functionality to the core.
Thank you. Unfortunately, in many
Nicolas Goaziou mail at nicolasgoaziou.fr writes:
Actually, the problem is deeper than that. This :inline: tag is just
a convoluted way to ask for a positive answer to another FAQ: « Can
I close an outline section without starting a new section? »
Hi Nicolas,
Thanks for your thoughts.
2014ko ekainak 14an, Nicolas Goaziou-ek idatzi zuen:
OTOH, the situation could be improved wrt :export: and :noexport: tags.
We could allow nesting :export: tags within :noexport: tags with the
following rule: the :export: headline with the lowest level
Hello,
Mark Edgington edgi...@gmail.com writes:
If I understand your example correctly, it seems like you are assuming that
the :inline: tag should promote a section's contents to the level *above*
the level of the section having the :inline: tag.
I'm always assuming the worst.
To me this
Hi Mark,
2014ko ekainak 14an, Mark Edgington-ek idatzi zuen:
[...]
It is true that this could sometimes be confusing. For example:
* A
text1
** B
text2
* C :inline:
text3
** D
text 4
would get treated like:
* A
text1
** B
text2
text3
* D
Hello,
Aaron Ecay aarone...@gmail.com writes:
I’m confused. In the text, you say “promoted to the root level of the
tree”, which I expect to mean promotion to a top-level headline. In the
example, though, H4 is promoted to second-level. Do you mean “promoted
to the level of the highest
Hi Nicolas,
2014ko ekainak 14an, Nicolas Goaziou-ek idatzi zuen:
Hello,
Aaron Ecay aarone...@gmail.com writes:
I’m confused. In the text, you say “promoted to the root level of the
tree”, which I expect to mean promotion to a top-level headline. In the
example, though, H4 is promoted
Ken Mankoff mank...@gmail.com writes:
Hi Eric, On 2014-06-12 at 20:46, Eric Schulte wrote:
Can you suggest a more intuitive/appropriate tag name? I'm not
personally partial to inline, it was just the first thing that
occurred to me. Previous implementations of similar behavior used
the
Eric Schulte schulte.e...@gmail.com writes:
I also ran across this need. What I had in mind was that certain todo
types would be treated as inline.
For instance, if P was a member of this hypothetical
org-inline-todo-keywords, then
* P a paragraph
some contents
would be rendered as
Thorsten Jolitz tjol...@gmail.com writes:
Ken Mankoff mank...@gmail.com writes:
Another common (for me) example is to have a heading called * Appendix
in a paper, and then the LaTeX \appendix command. The Org heading is
just for me. It should not be exported. All headings below the \appendix
Rasmus ras...@gmx.us writes:
Thorsten Jolitz tjol...@gmail.com writes:
Ken Mankoff mank...@gmail.com writes:
Another common (for me) example is to have a heading called * Appendix
in a paper, and then the LaTeX \appendix command. The Org heading is
just for me. It should not be exported.
Mark Edgington edgi...@gmail.com writes:
In using org-mode, there is one problem that has always irked me (and
is apparently also closely related to the FAQ How do I ignore a
headline?). When I am writing something, I sometimes want to group
things by concept or by work to be done, or any
Thorsten Jolitz tjolitz at gmail.com writes:
In a tree structure, when ignoring the parent node, it seems only
logical that the siblings are ignored too.
You seem to use the wrong tool for the task (headlines), this looks like
a perfect use case for TAGS, i.e. define your (concept)
Ken Mankoff mank...@gmail.com writes:
Another common (for me) example is to have a heading called * Appendix
in a paper, and then the LaTeX \appendix command. The Org heading is
just for me. It should not be exported. All headings below the \appendix
command are Org sub-sections but should be
Mark Edgington edgi...@gmail.com writes:
In using org-mode, there is one problem that has always irked me (and
is apparently also closely related to the FAQ How do I ignore a
headline?). When I am writing something, I sometimes want to group
things by concept or by work to be done, or any
+1 to the OP.
On 2014-06-12 at 13:32, Thorsten Jolitz wrote:
In a tree structure, when ignoring the parent node, it seems only
logical that the siblings are ignored too.
I'm found myself in all of the following situations:
1. I want the heading and everything below not-exported
2. I
On 2014-06-12 at 14:11, Thorsten Jolitz wrote:
Ken Mankoff mank...@gmail.com writes:
Another common (for me) example is to have a heading called *
Appendix in a paper, and then the LaTeX \appendix command. The Org
heading is just for me. It should not be exported. All headings below
the
Hi Eric, hi all,
2014ko ekainak 12an, Eric Schulte-ek idatzi zuen:
I just ran across this need myself, and updated an old solution to work
with the new exporter. See the thread and my solution at the following.
http://lists.gnu.org/archive/html/emacs-orgmode/2014-06/msg00238.html
It’s
2014-06-12 20:54 GMT+02:00 Aaron Ecay aarone...@gmail.com:
Hi Eric, hi all,
2014ko ekainak 12an, Eric Schulte-ek idatzi zuen:
I just ran across this need myself, and updated an old solution to work
with the new exporter. See the thread and my solution at the following.
2014-06-12 21:21 GMT+02:00 Nicolas Girard girard.nico...@gmail.com:
2014-06-12 20:54 GMT+02:00 Aaron Ecay aarone...@gmail.com:
Hi Eric, hi all,
I also ran across this need. What I had in mind was that certain todo
types would be treated as inline.
For instance, if P was a member of this
On 2014-06-12 at 15:21, Nicolas Girard wrote:
I also ran across this need. What I had in mind was that certain todo
types would be treated as inline.
...
Such a feature is more generic and would be useful in other contexts ;
and the LaTeX-related issues discussed in this thread would be
2014-06-12 21:26 GMT+02:00 Ken Mankoff mank...@gmail.com:
On 2014-06-12 at 15:21, Nicolas Girard wrote:
I vote for the following tags:
+ :noexport: Does not export item, content, and children.
+ :ignoreheading: Does not export heading. Exports content and children.
+ :ignorecontent: Does
I also ran across this need. What I had in mind was that certain todo
types would be treated as inline.
For instance, if P was a member of this hypothetical
org-inline-todo-keywords, then
* P a paragraph
some contents
would be rendered as
some contents
by the exporter, no matter
2014-06-12 22:13 GMT+02:00 Eric Schulte schulte.e...@gmail.com:
Why TODO types rather than a tag? IMO using a TODO type would conflate
task management and document structuring.
Agreed.
What do you think about the
attached patch which should add this functionality to the core.
Seems fine
Nicolas Girard girard.nico...@gmail.com writes:
2014-06-12 22:13 GMT+02:00 Eric Schulte schulte.e...@gmail.com:
Why TODO types rather than a tag? IMO using a TODO type would conflate
task management and document structuring.
Agreed.
What do you think about the
attached patch which
On 2014-06-12 at 16:13, Eric Schulte wrote:
What do you think about the attached patch which should add this
functionality to the core.
Why inline?
Org already has inline TODO items which is a different thing.
I don't think the word inline signifies that a heading will or won't
be exported
Ken Mankoff mank...@gmail.com writes:
On 2014-06-12 at 16:13, Eric Schulte wrote:
What do you think about the attached patch which should add this
functionality to the core.
Why inline?
Org already has inline TODO items which is a different thing.
I don't think the word inline
if i were a newcomer i'd wonder how these affected babel, agenda, etc.
maybe noexport, noexportheading, noexportcontent, exportpromotechildren?
On 6/12/14, Ken Mankoff mank...@gmail.com wrote:
+ :noexport: Does not export item, content, and children.
+ :ignoreheading: Does not export heading.
Mark Edgington edgi...@gmail.com writes:
In using org-mode, there is one problem that has always irked me (and
is apparently also closely related to the FAQ How do I ignore a
headline?). When I am writing something, I sometimes want to group
things by concept or by work to be done, or any
Hi Eric, On 2014-06-12 at 20:46, Eric Schulte wrote:
Can you suggest a more intuitive/appropriate tag name? I'm not
personally partial to inline, it was just the first thing that
occurred to me. Previous implementations of similar behavior
used the tag prelim.
I posted the following
Eric Schulte schulte.eric at gmail.com writes:
Ken Mankoff mankoff at gmail.com writes:
I don't think the word inline signifies that a heading will or won't
be exported and/or its children promoted.
Can you suggest a more intuitive/appropriate tag name?
Would it be possible /
Eric Abrahamsen eric at ericabrahamsen.net writes:
It looks like a groundswell for remove-andor-promote tags for headlines,
but for the sake of argument let me propose the use of blocks. It seems
to me that something like a generic block (a block that does nothing
but delete its begin/end
Mark Edgington edgi...@gmail.com writes:
Eric Abrahamsen eric at ericabrahamsen.net writes:
It looks like a groundswell for remove-andor-promote tags for headlines,
but for the sake of argument let me propose the use of blocks. It seems
to me that something like a generic block (a block
48 matches
Mail list logo
