Hi all,
I'm preparing a tutorial on writing Org-mode exporters. To this end,
I'm writing a (simplistic) Oddmuse/WikiCreole exporter. Rather
obviously, I'm modeling it on existing exporters (mainly ox-latex),
which seem to share a lot of structure (function names and docstrings in
particular). I
Marcin Borkowski writes:
> I reuse parts of GPL'd code (as I mentioned, quite generic ones, but
> still). Is it fine, or should I expect a visit from EFF lawyers or
> something?
My guess would be no. You should ask the FSF lawyers.
Rasmus
--
What will be next?
Hi all,
as I mentioned, I'm writing a simple exporter. However, I stumbled on
something apparently simple. How to get the current list level within
org-whatever-item transcoder?
TIA,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Thomas S. Dye writes:
> Add a clause to indicate some languages don't support multiple Babel
> sessions.
Thanks. Pushed!
--
Dobbelt-A
Hello,
Rasmus writes:
>> I have a few other questions:
>> - how does one change the variant when doing a subtree export? By
>> setting EXPORT_LATEX_VARIANT?
>
> It seems to work at least to the point that the right engine is written to
> the file:
>
> #+LATEX_VARIANT: xelatex
> * pdflatex
> :P
On 2015-07-27, at 10:16, Rasmus wrote:
> Marcin Borkowski writes:
>
>> I reuse parts of GPL'd code (as I mentioned, quite generic ones, but
>> still). Is it fine, or should I expect a visit from EFF lawyers or
>> something?
>
> My guess would be no. You should ask the FSF lawyers.
You mean l
Sebastien Vauban
writes:
> FWIW, it seems that people who played with different LaTeX engines used
> the "LATEX_CMD" property, as adviced on Worg [1]. Doesn't matter if we
> change that, but just a reminder of some already common usage.
I didn't know that worg page. Just to understand, you are
On Monday, 27 Jul 2015 at 00:06, Christopher W. Ryan wrote:
> Using org-mode 8.2.4-1 on Linux Mint.
>
> Below is a minimal working example of my problem. The trouble is that
> the Berlin theme is not applied--it remains the default theme.
Do you need to export a sub-tree? I have no experience in
On Sunday, 26 Jul 2015 at 15:04, Xiha wrote:
> 2) I have #+OPTIONS: H:9 num:9 because explicit level structure is
> important for this document. I would like to have more control over
For LaTeX export, this will not work (AFAIK) as LaTeX only supports 4 or
so levels of headings.
> how this is exp
Marcin Borkowski writes:
> On 2015-07-27, at 10:16, Rasmus wrote:
>
>> Marcin Borkowski writes:
>>
>>> I reuse parts of GPL'd code (as I mentioned, quite generic ones, but
>>> still). Is it fine, or should I expect a visit from EFF lawyers or
>>> something?
>>
>> My guess would be no. You sho
On Monday, 27 Jul 2015 at 10:06, Marcin Borkowski wrote:
> Hi all,
>
> I'm preparing a tutorial on writing Org-mode exporters. To this end,
> I'm writing a (simplistic) Oddmuse/WikiCreole exporter. Rather
> obviously, I'm modeling it on existing exporters (mainly ox-latex),
> which seem to share
Vikas Rawal writes:
> Thanks all. I was not familiar with this way of defining local variables. Just
> checked the relevant part of the manual. Very useful.
And, finally, one solution exposed on Worg:
http://orgmode.org/worg/org-faq.html#using-xelatex-for-pdf-export
Best regards,
Seb
--
Seb
On 2015-07-27, at 10:17, Marcin Borkowski wrote:
> Hi all,
>
> as I mentioned, I'm writing a simple exporter. However, I stumbled on
> something apparently simple. How to get the current list level within
> org-whatever-item transcoder?
By inspecting values of org-whatever-item's arguments, I
On 2015-07-27, at 10:46, Marcin Borkowski wrote:
> On 2015-07-27, at 10:17, Marcin Borkowski wrote:
>
>> Hi all,
>>
>> as I mentioned, I'm writing a simple exporter. However, I stumbled on
>> something apparently simple. How to get the current list level within
>> org-whatever-item transcoder
On 2015-07-27, at 10:42, Eric S Fraga wrote:
> On Monday, 27 Jul 2015 at 10:06, Marcin Borkowski wrote:
>> Hi all,
>>
>> I'm preparing a tutorial on writing Org-mode exporters. To this end,
>> I'm writing a (simplistic) Oddmuse/WikiCreole exporter. Rather
>> obviously, I'm modeling it on exist
On 2015-07-27, at 10:35, Rasmus wrote:
> Marcin Borkowski writes:
>
>> On 2015-07-27, at 10:16, Rasmus wrote:
>>
>>> Marcin Borkowski writes:
>>>
I reuse parts of GPL'd code (as I mentioned, quite generic ones, but
still). Is it fine, or should I expect a visit from EFF lawyers or
Hello,
Rainer M Krug writes:
> Eric S Fraga writes:
>> On Friday, 24 Jul 2015 at 15:07, Rainer M Krug wrote:
>>> In an org document, I want to change the text colour of two words
>>> {\color{red} red line } to red in a sentence and the rest should be
>>> normal colour.
>>>
>>> I am missing somet
Fabrice Niessen writes:
> I've begun writing such generic macros for basic and advanced formatting
> (see [1]), though they are currently limited to the HTML backend:
LaTeX has textcolor via (x)xcolor (AFAIR). odt it probably pretty easy to
get from LO trials.
Rasmus
--
This space is left in
Rasmus writes:
> Sebastien Vauban writes:
>
>> FWIW, it seems that people who played with different LaTeX engines used
>> the "LATEX_CMD" property, as adviced on Worg [1]. Doesn't matter if we
>> change that, but just a reminder of some already common usage.
>
> I didn't know that worg page. Ju
Hi,
Sebastien Vauban
writes:
>> (I'm hesitant to allow arbitrary scripts).
>
> I agree. Just stick to the basic need, which is to be able to easily
> change of LaTeX engine.
I'd however also like to allow some flags, e.g. -shell-escape/write18 for
minted. I cannot think of other useful flags.
On Monday, 27 Jul 2015 at 10:59, Marcin Borkowski wrote:
[...]
> See how stupid this whole copyright law swamp is?
>
> What if I reuse just the basic structure of sentences in the docstrings,
> like in "Subject + verb + preposition + object"? Do I have to use GPL
> then, too? ;-)
>
> And what if
On Monday, 27 Jul 2015 at 11:05, Marcin Borkowski wrote:
[...]
> Frankly speaking, I'm rather astonished at your and Eric's answers.
> I treated my question as a formality, and expected answers like "Of
> course you can do it, don't be silly."
Oh, sorry! I thought you actually did want to get s
On 2015-07-27, at 11:46, Eric S Fraga wrote:
> On Monday, 27 Jul 2015 at 11:05, Marcin Borkowski wrote:
>
> [...]
>
>> Frankly speaking, I'm rather astonished at your and Eric's answers.
>> I treated my question as a formality, and expected answers like "Of
>> course you can do it, don't be sill
On 2015-07-27, at 11:31, Eric S Fraga wrote:
> On Monday, 27 Jul 2015 at 10:59, Marcin Borkowski wrote:
>
> [...]
>
>> See how stupid this whole copyright law swamp is?
>>
>> What if I reuse just the basic structure of sentences in the docstrings,
>> like in "Subject + verb + preposition + objec
Hi all,
after a short discussion in a recent thread, I have a serious technical
question.
Assume that (for some reason) I want to write an Org-mode exporter which
won't be GPL'd. (Use-case: having written a few custom exporters, I'm
writing a tutorial on them, and I consider publishing a *tutori
Marcin Borkowski writes:
> I'm preparing a tutorial on writing Org-mode exporters. To this end,
> I'm writing a (simplistic) Oddmuse/WikiCreole exporter. Rather
> obviously, I'm modeling it on existing exporters (mainly ox-latex),
> which seem to share a lot of structure (function names and doc
On 27/07/15 13:52, Marcin Borkowski wrote:
> I disagree. Licensing a tutorial with GPL is a stupid thing to do.
> A tutorial may contain code which people naturally mimic (or even
> copy). Such things should definitely be in PD.
As yourself pointed out in one of your emails, in many legal
ordina
Marcin Borkowski writes:
> Hi all,
>
> after a short discussion in a recent thread, I have a serious technical
> question.
>
> Assume that (for some reason) I want to write an Org-mode exporter which
> won't be GPL'd. (Use-case: having written a few custom exporters, I'm
> writing a tutorial on
Oleh Krehel writes:
> If anywhere in your code there's (require 'org), you have to release
> your code under GPL.
Are you sure about that? By this logic, *any* .el file should be GPL as
they use (defun ·), implicitly loaded from byte-run.
Rasmus
--
Lasciate ogni speranza o voi che entrate: s
Rasmus writes:
> Oleh Krehel writes:
>
>> If anywhere in your code there's (require 'org), you have to release
>> your code under GPL.
>
> Are you sure about that? By this logic, *any* .el file should be GPL as
> they use (defun ·), implicitly loaded from byte-run.
I'm pretty sure: you're call
Hello Marcin,
On 27/07/15 14:10, Marcin Borkowski wrote:
> Assume that (for some reason) I want to write an Org-mode exporter which
> won't be GPL'd. (Use-case: having written a few custom exporters, I'm
> writing a tutorial on them, and I consider publishing a *tutorial* with
> GPL'd code a Bad
Daniele Nicolodi writes:
> On 27/07/15 13:52, Marcin Borkowski wrote:
>> I disagree. Licensing a tutorial with GPL is a stupid thing to do.
>> A tutorial may contain code which people naturally mimic (or even
>> copy). Such things should definitely be in PD.
[many excellent comments. As a n
On 27/07/15 14:25, Oleh Krehel wrote:
> Rasmus writes:
>
>> Oleh Krehel writes:
>>
>>> If anywhere in your code there's (require 'org), you have to release
>>> your code under GPL.
>>
>> Are you sure about that? By this logic, *any* .el file should be GPL as
>> they use (defun ·), implicitly lo
On 27/07/15 14:42, Greg Troxel wrote:
>
> Daniele Nicolodi writes:
>
>> On 27/07/15 13:52, Marcin Borkowski wrote:
>>> I disagree. Licensing a tutorial with GPL is a stupid thing to do.
>>> A tutorial may contain code which people naturally mimic (or even
>>> copy). Such things should definite
Oleh Krehel writes:
> Marcin Borkowski writes:
>
>> Hi all,
>>
>> after a short discussion in a recent thread, I have a serious technical
>> question.
>>
>> Assume that (for some reason) I want to write an Org-mode exporter which
>> won't be GPL'd. (Use-case: having written a few custom exporte
Hi Dmitry,
org-mode has the following format for links:
[[::][]]
What should I do, if contains ']' symbol? Like this:
$form['input']
Not sure it helps in your case, but this
* Heading containing [brackets]
* Other heading
Here is a link to [[Heading containing *%5B*brackets*%5D
Marcin Borkowski writes:
> after a short discussion in a recent thread, I have a serious technical
> question.
>
> Assume that (for some reason) I want to write an Org-mode exporter which
> won't be GPL'd. (Use-case: having written a few custom exporters, I'm
I will assume that you mean "write
Rainer M Krug writes:
> These packages all depend on R itself.
>
> So isn't this the same as in emacs / elisp? Isn't an exporter / .el file
> the same as a package in R, something which enhances the original
> product using a provided interface (the functions) but does not change
> anything in t
On 27.07.2015 15:09, Greg Troxel wrote:
>
> Rainer M Krug writes:
>
>> These packages all depend on R itself.
>>
>> So isn't this the same as in emacs / elisp? Isn't an exporter / .el file
>> the same as a package in R, something which enhances the original
>> product using a provided interface
Hi Erik,
Erik Hetzner writes:
> I previously hooked up org with recoll with pretty good results.
> ...
> http://www.lesbonscomptes.com/recoll/
Thanks for the link. I tried it, and it actually works great on my
system (unlike swish-e). And I did no configuration of mimeinfo, I only
told it to in
Andreas Hilboll writes:
> On 27.07.2015 15:09, Greg Troxel wrote:
>>
>> Rainer M Krug writes:
>>
>>> These packages all depend on R itself.
>>>
>>> So isn't this the same as in emacs / elisp? Isn't an exporter / .el file
>>> the same as a package in R, something which enhances the original
>>>
Thanks Rasmus and Eric!
1) subtitle
The git version has a #+subtitle keyword. See the git version of the
manual for supported backends (most).
Where the git install instructions say "you should edit local.mk to
point to the appropriate install location", how do I find out where this
is? Sor
On 07/27/2015 08:10 AM, Marcin Borkowski wrote:
Please refrain from comments about my stupidity or stupidity of the
so-called IP law. And please understand that if I'm sounding a bit
angry in this email, it's because I'm *very* angry about this whole
lawyer mafia restricting my freedom (again).
On 2015-07-27, at 14:16, Oleh Krehel wrote:
> Marcin Borkowski writes:
>
>> Hi all,
>>
>> after a short discussion in a recent thread, I have a serious technical
>> question.
>>
>> Assume that (for some reason) I want to write an Org-mode exporter which
>> won't be GPL'd. (Use-case: having wri
On 2015-07-27, at 15:09, Greg Troxel wrote:
> Rainer M Krug writes:
>
>> These packages all depend on R itself.
>>
>> So isn't this the same as in emacs / elisp? Isn't an exporter / .el file
>> the same as a package in R, something which enhances the original
>> product using a provided interfa
There is also a helm-recoll package available. I came across recoll a
few weeks ago when I saw that package! It also basically worked as
advertised and I am just looking forward to some free time to figure out
how to get the super focused search I worked out for swish-e.
Has anyone tried using ema
On 2015-07-27, at 15:05, Greg Troxel wrote:
> Marcin Borkowski writes:
>
>> after a short discussion in a recent thread, I have a serious technical
>> question.
>>
>> Assume that (for some reason) I want to write an Org-mode exporter which
>> won't be GPL'd. (Use-case: having written a few cus
On Monday, 27 Jul 2015 at 15:55, Xiha wrote:
> Thanks Rasmus and Eric!
>
> 1) subtitle
>> The git version has a #+subtitle keyword. See the git version of the
>> manual for supported backends (most).
>
> Where the git install instructions say "you should edit local.mk to
> point to the appropriate
On Monday, 27 Jul 2015 at 14:10, Marcin Borkowski wrote:
[...]
> And I see no reason to impose GPL on them.))
[...]
> And please understand that if I'm sounding a bit angry in this email,
> it's because I'm *very* angry about this whole lawyer mafia
> restricting my freedom (again). (Note: I'm
On 2015-07-27, at 17:13, Eric S Fraga wrote:
> On Monday, 27 Jul 2015 at 14:10, Marcin Borkowski wrote:
>
> [...]
>
>> And I see no reason to impose GPL on them.))
>
> [...]
>
>> And please understand that if I'm sounding a bit angry in this email,
>> it's because I'm *very* angry about this who
Hi.
I'm playing a little bit with R code blocks in babel and calling them
in different parts of my document (e.g. showing output in the main
part and the code in the appendix).
With most code blocks (e.g. setting some variables or outputting a
LaTeX table with xtable) this works as expected (than
Marcin Borkowski writes:
> And what if I explicitly want people to be able to use my code in
> a proprietary software?
Then you're out of luck. Just like thousands (millions) of programmers
are out of luck when they want to examine the code of a closed source
proprietary software.
If I asked so
On 2015-07-27, at 15:58, Scott Randby wrote:
> On 07/27/2015 08:10 AM, Marcin Borkowski wrote:
>>
>> Please refrain from comments about my stupidity or stupidity of the
>> so-called IP law. And please understand that if I'm sounding a bit
>> angry in this email, it's because I'm *very* angry ab
Hi Oleh,
On Mon, 27 Jul 2015 06:19:35 -0700,
Oleh Krehel wrote:
>
>
> Hi Erik,
>
> Erik Hetzner writes:
> > I previously hooked up org with recoll with pretty good results.
> > ...
> > http://www.lesbonscomptes.com/recoll/
>
> Thanks for the link. I tried it, and it actually works great on m
On Monday, 27 Jul 2015 at 18:01, Marcin Borkowski wrote:
[...]
> And what if I explicitly want people to be able to use my code in
> a proprietary software? Or if I just want to use the "Unlicense"? Or
> if I don't want to use GPL on principle? (And if I still consider Emacs
You are perfectly
On 2015-07-27, at 14:39, Daniele Nicolodi wrote:
> Hello Marcin,
>
> On 27/07/15 14:10, Marcin Borkowski wrote:
>> Assume that (for some reason) I want to write an Org-mode exporter which
>> won't be GPL'd. (Use-case: having written a few custom exporters, I'm
>> writing a tutorial on them, and
On 2015-07-27, at 18:54, Eric S Fraga wrote:
> On Monday, 27 Jul 2015 at 18:01, Marcin Borkowski wrote:
>
> [...]
>
>> And what if I explicitly want people to be able to use my code in
>> a proprietary software? Or if I just want to use the "Unlicense"? Or
>> if I don't want to use GPL on prin
Marcin Borkowski writes:
> I'm preparing a tutorial on writing Org-mode exporters. To this end,
> I'm writing a (simplistic) Oddmuse/WikiCreole exporter. Rather
> obviously, I'm modeling it on existing exporters (mainly ox-latex),
> which seem to share a lot of structure (function names and docst
On 2015-07-27, at 18:12, Oleh Krehel wrote:
> Marcin Borkowski writes:
>
>> And what if I explicitly want people to be able to use my code in
>> a proprietary software?
>
> Then you're out of luck. Just like thousands (millions) of programmers
> are out of luck when they want to examine the cod
On 2015-07-27, at 14:17, Daniele Nicolodi wrote:
> On 27/07/15 13:52, Marcin Borkowski wrote:
>> I disagree. Licensing a tutorial with GPL is a stupid thing to do.
>> A tutorial may contain code which people naturally mimic (or even
>> copy). Such things should definitely be in PD.
>
> As your
On 2015-07-27, at 14:42, Greg Troxel wrote:
> Daniele Nicolodi writes:
>
>> On 27/07/15 13:52, Marcin Borkowski wrote:
>>> I disagree. Licensing a tutorial with GPL is a stupid thing to do.
>>> A tutorial may contain code which people naturally mimic (or even
>>> copy). Such things should def
On 2015-07-27, at 14:52, Daniele Nicolodi wrote:
> On 27/07/15 14:42, Greg Troxel wrote:
>>
>> Daniele Nicolodi writes:
>>
>>> On 27/07/15 13:52, Marcin Borkowski wrote:
I disagree. Licensing a tutorial with GPL is a stupid thing to do.
A tutorial may contain code which people natu
On 2015-07-27, at 14:50, Daniele Nicolodi wrote:
> I'm not sure that using an interpreter for running some code classifies
> as linking, but I don't know of any "official" statement on the subject.
>
> On the other hand, Elisp is an extension language for a GPL program,
> thus it may be argued t
Hi Marcin,
Marcin Borkowski writes:
> as I mentioned, I'm writing a simple exporter. However, I stumbled on
> something apparently simple. How to get the current list level within
> org-whatever-item transcoder?
I ran into this problem once; the solution I found was to just walk up
the AST vi
Marcin Borkowski writes:
> On 2015-07-27, at 14:39, Daniele Nicolodi wrote:
>
>> Hello Marcin,
>>
>> On 27/07/15 14:10, Marcin Borkowski wrote:
>>> Assume that (for some reason) I want to write an Org-mode exporter which
>>> won't be GPL'd. (Use-case: having written a few custom exporters, I'm
On 27/07/15 19:42, Marcin Borkowski wrote:
> That I've already learned. OTOH, one of the reasons to use PD might be
> that I explicitly state that I object the legal system I live in. (Mind
> you: I'm not an anarchist, and I'm very far from that. But this system
> is almost unbearable.)
This st
On 2015-07-27, at 20:02, Nick Dokos wrote:
> Marcin Borkowski writes:
>
>> On 2015-07-27, at 14:39, Daniele Nicolodi wrote:
>>
>>> Hello Marcin,
>>>
>>> On 27/07/15 14:10, Marcin Borkowski wrote:
Assume that (for some reason) I want to write an Org-mode exporter which
won't be GPL'd.
On 2015-07-27, at 20:02, Daniele Nicolodi wrote:
> On 27/07/15 19:42, Marcin Borkowski wrote:
>> That I've already learned. OTOH, one of the reasons to use PD might be
>> that I explicitly state that I object the legal system I live in. (Mind
>> you: I'm not an anarchist, and I'm very far from
Hi Marcin and all,
Marcin Borkowski writes:
> after a short discussion in a recent thread, I have a serious technical
> question.
>
> Assume that (for some reason) I want to write an Org-mode exporter which
> won't be GPL'd. (Use-case: having written a few custom exporters, I'm
> writing a tut
Oleh Krehel writes:
> Marcin Borkowski writes:
>
>> And what if I explicitly want people to be able to use my code in
>> a proprietary software?
>
> Then you're out of luck. Just like thousands (millions) of programmers
> are out of luck when they want to examine the code of a closed source
> p
On 27/07/15 20:20, Marcin Borkowski wrote:
>
> On 2015-07-27, at 20:02, Daniele Nicolodi wrote:
>
>> On 27/07/15 19:42, Marcin Borkowski wrote:
>>> That I've already learned. OTOH, one of the reasons to use PD might be
>>> that I explicitly state that I object the legal system I live in. (Mind
On Monday, 27 Jul 2015 at 19:04, Marcin Borkowski wrote:
[...]
> Nope. As stated by someone here (Oleh, I guess), if I (require 'org),
> or possibly even just write Elisp, and want to distribute it, it has to
> be GPL.
I do not think this is true. I would like to see a proper reference
where i
On 27/07/15 18:59, Marcin Borkowski wrote:
> On 2015-07-27, at 14:39, Daniele Nicolodi wrote:
>> Therefore, the only extensions to org-mode that can exist (and be
>> distributed, if you write code and keep it for yourself you are not
>> affected by the licensing terms) must be GPL.
>>
>> Thus, it
On 2015-07-27, at 20:30, Daniele Nicolodi wrote:
> On 27/07/15 20:20, Marcin Borkowski wrote:
>>
>> On 2015-07-27, at 20:02, Daniele Nicolodi wrote:
>>
>>> On 27/07/15 19:42, Marcin Borkowski wrote:
That I've already learned. OTOH, one of the reasons to use PD might be
that I expli
Hi Stefan,
Stefan Nobis writes:
> Hi.
>
> I'm playing a little bit with R code blocks in babel and calling them
> in different parts of my document (e.g. showing output in the main
> part and the code in the appendix).
>
> With most code blocks (e.g. setting some variables or outputting a
> LaTeX
Hi Pascal,
alternatively you could have installed ditaa and point ob-ditaa to it:
#+BEGIN_SRC elisp
(setq org-ditaa-jar-path "/usr/bin/ditaa")
#+END_SRC
Not an answer to your actual question, though.
Regards,
Bernhard Pröll
On Sat, 18. Jul 12:34, Pascal Lorenz wrote:
Hi!
When I tried to re
I create the RSS feed for my blog with a file that #+include:'s the
various blog posts; this way, when I export it to RSS using ox-rss.el,
the full text of each blog post is in the feed. The feed is generated
from a file called "/rss.org", and the blog posts themselves are
located in "/blog/*.o
on repeated task i change state twice in agenda. i ret to go to the
task. i do undo only once, but both changes get undone.
thanks.
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
Ramsay's disease DOES progress. MANY people have died from it. And
ANYBODY can get it.
Denmark: fr
78 matches
Mail list logo
