Hi Suvayu,
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
It already exists:
http://orgmode.org/worg/exporters/filter-markup.html
Maybe this can be improved?
This is the documentation for export filters, with some example.
But it is not clear that this page welcome new contributed
Hello Bastien,
Bastien wrote:
Sebastien Vauban writes:
Shouldn't, then, some filters be available by default in core Org?
I don't think so: my understanding is that default filters would
then be implemented without relying on filters -- so filters are
really optional by nature. Nicolas
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
writes:
The thing is that, IMHO, there are 2 types of filters required:
- filters for my own additions to Org syntax, that I don't need (or
want) to share with anybody
- filters for missing Org syntax which seems a need
On Sat, Jan 04, 2014 at 11:40:10AM +0100, Bastien wrote:
Hi Andreas,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
It is a very small thing and I am very much happy with using a filter based
approach here.
One thing really worth improving is the tutorials around filters on
Hi Andreas,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
It is a very small thing and I am very much happy with using a filter based
approach here.
One thing really worth improving is the tutorials around filters on
Worg. Or maybe: let's create a place similar to org-hacks.org
Bastien b...@gnu.org writes:
Hi Andreas,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
It is a very small thing and I am very much happy with using a filter based
approach here.
One thing really worth improving is the tutorials around filters on
Worg. Or maybe: let's create a
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
I am very sorry -- would have been a nice way to contribute.
No problem, I just wanted to verbalize this wish so that someone
with more time at hand can take the challenge :)
--
Bastien
Andreas Leha wrote:
Could you expand on what you mean by less portable? I'm interested in
portability from a reproducible research perspective and want to avoid
habits that don't port well to other researchers' systems.
I did not want to include these words in the first place. The words
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
writes:
Shouldn't, then, some filters be available by default in core Org?
I don't think so: my understanding is that default filters would
then be implemented without relying on filters -- so filters are
really optional by
Nicolas Goaziou n.goaz...@gmail.com writes:
So in short: If page breaks are not in org directly many people will
end up with inferior and/or less portable org files.
For the record, after thinking about it, I'd rather stay away from
invisible characters in Org syntax, would it be page
Bastien b...@gnu.org writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
So in short: If page breaks are not in org directly many people will
end up with inferior and/or less portable org files.
For the record, after thinking about it, I'd rather stay away from
invisible characters in Org
Aloha Andreas,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Bastien b...@gnu.org writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
So in short: If page breaks are not in org directly many people will
end up with inferior and/or less portable org files.
For the record, after
Hi Tom,
t...@tsdye.com (Thomas S. Dye) writes:
Aloha Andreas,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Bastien b...@gnu.org writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
So in short: If page breaks are not in org directly many people will
end up with inferior
Hello,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
So in short: If page breaks are not in org directly many people will
end up with inferior and/or less portable org files.
For the record, after thinking about it, I'd rather stay away from
invisible characters in Org syntax,
Hi Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
So in short: If page breaks are not in org directly many people will
end up with inferior and/or less portable org files.
For the record, after thinking about it, I'd
Hello,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Just for me to understand:
The recommended way now
Note that the recommended way hasn't really changed. There was no
recommended way before, nor there is one now.
is to have a filter and write (say) \mypersonalnewline in my
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Just for me to understand:
The recommended way now
Note that the recommended way hasn't really changed. There was no
recommended way before, nor there is one now.
;-)
is to have
You could have used a #+PAGEBREAK and handled it as part of say an
advice to org-BACKEND-keyword in whatever BACKEND you are using.
Hello,
Rüdiger Sonderfeld ruedi...@c-plusplus.de writes:
On Friday 22 November 2013 11:24:17 Nicolas Goaziou wrote:
Anyway, I don't think this is a good idea to introduce a new syntax just
to avoid a one-liner (or a hook, see below). Also, this would only make
sense in few export back-ends.
On 11/24/13 16:31 PM, Nicolas Goaziou wrote:
Hello,
Rüdiger Sonderfeld ruedi...@c-plusplus.de writes:
On Friday 22 November 2013 11:24:17 Nicolas Goaziou wrote:
Anyway, I don't think this is a good idea to introduce a new syntax just
to avoid a one-liner (or a hook, see below). Also, this
Eric Abrahamsen e...@ericabrahamsen.net writes:
On 11/24/13 16:31 PM, Nicolas Goaziou wrote:
Hello,
Rüdiger Sonderfeld ruedi...@c-plusplus.de writes:
On Friday 22 November 2013 11:24:17 Nicolas Goaziou wrote:
Anyway, I don't think this is a good idea to introduce a new syntax just
to
Nicolas Goaziou writes:
So, is this feature a must-have?
No, it's not. (Just another user's ten cents.)
Or would a filter template in Worg more appropriate in this case?
That, or showing how to make a {{{pagebreak}}} macro expanding to export
snippets. (And explaining how regular page
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
Eric Abrahamsen e...@ericabrahamsen.net writes:
Here's a fairly simple first stab, with page breaks made into an
element, and a sample handling in the LaTeX backend. I've hardcoded ^L
and the page-delimiter regexp that finds it, not sure
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
Eric Abrahamsen e...@ericabrahamsen.net writes:
Here's a fairly simple first stab, with page breaks made into an
element, and a sample handling in the LaTeX backend. I've hardcoded ^L
and the page-delimiter regexp that finds it, not sure
Hello,
Eric Abrahamsen e...@ericabrahamsen.net writes:
Here's a fairly simple first stab, with page breaks made into an
element, and a sample handling in the LaTeX backend. I've hardcoded ^L
and the page-delimiter regexp that finds it, not sure it's worth
providing an org-page-delimiter
On Friday 22 November 2013 11:24:17 Nicolas Goaziou wrote:
Anyway, I don't think this is a good idea to introduce a new syntax just
to avoid a one-liner (or a hook, see below). Also, this would only make
sense in few export back-ends.
But is it really a new syntax or just support for an
Eric Abrahamsen e...@ericabrahamsen.net writes:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
On Thu, Nov 21, 2013 at 08:11:50AM +0700, Eric Abrahamsen wrote:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
On Wed, Nov 20, 2013 at 03:20:02PM -0600, Russell Adams wrote:
On Wed, Nov 20,
27 matches
Mail list logo
