Akira Kyle writes:
>> I've just checked and Akira's is a registered FSF contributor
>> since
>> last may.
>
> Unfortunately I was informed that I am only allowed to make
> "small" contributions. I wasn't given any explicit metric of what
> qualifies as a "small" contribution, but was informed
Akira Kyle writes:
> It's been five years since I initially wrote this patch and two years
> since I started my assignment processes
More precisely: I'll double-check with the FSF legal team that having
your name in the FSF copyright registers means that you can contribute
to Emacs and
Hi Akira,
Akira Kyle writes:
> I have been informed that this document my university has
> provided is queued with the FSF legal team for eventual review.
Thanks for your answer.
I suggest we take this off-list and try to sort it out with the FSF
legal team directly.
--
Bastien Guerry
On Sat, Aug 05, 2023 at 07:29 PM, Bastien Guerry
wrote:
Ihor Radchenko writes:
Akira, may I know if you managed to clear the FSF paperwork?
I've just checked and Akira's is a registered FSF contributor
since
last may.
Unfortunately I was informed that I am only allowed to make
Ihor Radchenko writes:
> Akira, may I know if you managed to clear the FSF paperwork?
I've just checked and Akira's is a registered FSF contributor since
last may.
--
Bastien Guerry
Bastien Guerry writes:
>>> The last message I received from them was over a month ago and my
>>> last follow up email to them was ten days ago.
>>
>> Bastien, may you follow up with Craig about the status?
>
> I don't see the FSF copyright assignment status for
> ak...@akirakyle.com - please CC
Ihor Radchenko writes:
> Akira Kyle writes:
>
>>> Do note that FSF should reply within 5 working days.
>>> If not, please follow up and wait another 5 working days.
>>> They should reply by then, but if still not, let us know - we
>>> will be
>>> able to push them further.
>>
>> The last
Akira Kyle writes:
>> Do note that FSF should reply within 5 working days.
>> If not, please follow up and wait another 5 working days.
>> They should reply by then, but if still not, let us know - we
>> will be
>> able to push them further.
>
> The last message I received from them was over a
On Sat, Mar 25, 2023 at 06:13 PM, Ihor Radchenko
wrote:
Do note that FSF should reply within 5 working days.
If not, please follow up and wait another 5 working days.
They should reply by then, but if still not, let us know - we
will be
able to push them further.
The last message I
Akira Kyle writes:
> Unfortunately, I'm still waiting for my fsf copyright assignment
> paperwork to go through, and I think I'm already at my maximum
> allowed copyright-exempt contributions for emacs.
Do note that FSF should reply within 5 working days.
If not, please follow up and wait
On Mon, Nov 14, 2022 at 05:52 AM, Ihor Radchenko
wrote:
Have you had a chance to look into my comments?
Sorry for the really slow replies, I do intend to follow up on
this at some point.
Unfortunately, I'm still waiting for my fsf copyright assignment
paperwork to go through, and I
Ihor Radchenko writes:
> Akira Kyle writes:
>
>> I've been using the attached patch for the last few years and I've meaning
>> to send it here/start a discussion about ob-latex.el since I used it pretty
>> much daily to write tikz figures in org mode. So I'm glad to see this
>> discussion
Akira Kyle writes:
> I've been using the attached patch for the last few years and I've meaning to
> send it here/start a discussion about ob-latex.el since I used it pretty much
> daily to write tikz figures in org mode. So I'm glad to see this discussion
> has been started!
>
> I've found
I've been using the attached patch for the last few years and I've meaning to
send it here/start a discussion about ob-latex.el since I used it pretty much
daily to write tikz figures in org mode. So I'm glad to see this discussion has
been started!
I've found it to be incredibly productive
reza writes:
First of all, thanks a lot for digging into ob-latex!
This file has not been touched seriously since 7 years ago and the last
major change is 8 years ago (510e70379).
> When having a look at the code inside ob-latex.el I also encountered a
> few stuff which made me wondering:
>
>
Hi, I had this very same question to produce svg from latex src blocks.
First, consider this example :
#+HEADER: :file test1.png
#+HEADER: :exports results
#+HEADER: :results output silent graphics file
#+HEADER: :fit yes :noweb yes :headers '("\\usepackage{tikz}"
By setting
(setq org-babel-latex-preamble (lambda (_)
"\\documentclass[preview]{standalone}\n")
the tikz file svg generation does run fine. Obviously the part
\\def\\pgfsysdriver{pgfsys-tex4ht.def}
inside `org-babel-latex-preamble` does not play well with the svg
generation.
When
> I do not think that ob-latex code has much to add into ox-latex.
> What I was referring to is the giant `cond' form in
> org-babel-execute:latex, which produces different LaTeX templates
> depending on the output file extension.
>
> The ob-latex templates should probably remain specific to
reza writes:
>> It is a part of the same infrastructure, but the LaTeX templates for
>> html/pdf/svg/tiks export are different for some reason. There is even a
>> TODO comment in the code saying that things should better be unified. Alas.
>>
>> Patches improving the situation are always
> It is a part of the same infrastructure, but the LaTeX templates for
> html/pdf/svg/tiks export are different for some reason. There is even a
> TODO comment in the code saying that things should better be unified. Alas.
>
> Patches improving the situation are always welcome.
Where would I
> why is this handled differently, should it at least use part of the same
infrastructure?
It is a part of the same infrastructure, but the LaTeX templates for
html/pdf/svg/tiks export are different for some reason. There is even a
TODO comment in the code saying that things should better be
> AFAIU, the news entry is about LaTeX export (ox-latex.el). Here, we are
> talking about LaTeX babel backend, which is a different implementation
> (ob-latex.el).
>
> In any case, I can reproduce on the latest main.
why is this handled differently, should it at least use part of the same
reza writes:
>> svg generation takes a completely different code branch compared to pdf
>> in ox-latex.el. I am not sure why. Hopefully, someone more familiar with
>> ox-latex and LaTeX in general can chime in.
>
> Just found this in the source [1], maybe it is already fixed?
>
> svg generation takes a completely different code branch compared to pdf
> in ox-latex.el. I am not sure why. Hopefully, someone more familiar with
> ox-latex and LaTeX in general can chime in.
Just found this in the source [1], maybe it is already fixed?
[1]
reza writes:
> when running the following code
>
> #+header: :file "absolute-distance.pdf"
> #+header: :results file drawer :exports results :fit yes :border 0cm
> #+header: :headers '("\\usepackage{tikz}")
> #+begin_src latex
>\usetikzlibrary{positioning}
>\begin{tikzpicture}
>
25 matches
Mail list logo
