Rasmus writes:
> Pushed with your recommendations. Thanks.
Thank you.
Regards,
Nicolas Goaziou writes:
>> Here's an updated patch.
>
> Thank you. Some comments follow.
Pushed with your recommendations. Thanks.
--
May the Force be with you
Rasmus writes:
> Here's an updated patch.
Thank you. Some comments follow.
> +(defconst org-latex-math-environments-re
> + (concat (regexp-opt
> +'("equation" "eqnarray" "math" "displaymath"
> + "align" "gather" "multline" "flalign" "alignat"
> + "xalignat" "xxalign
Nicolas Goaziou writes:
>> Yeah, I though of that, but that require us to maintain a list of latex
>> math environments, which may or may not be annoying.
>
> Well, if an environment is not recognized as a math one, it still gets
> a label. So, that's not a big deal to miss some of them.
>
>> If
Rasmus writes:
> Yeah, I though of that, but that require us to maintain a list of latex
> math environments, which may or may not be annoying.
Well, if an environment is not recognized as a math one, it still gets
a label. So, that's not a big deal to miss some of them.
> If we add such a vari
Nicolas Goaziou writes:
> Rasmus writes:
>
>> Can we have conditional dependence on texmathp?
>
> I guess it doesn't hurt. You need to declare it as an external function
> in order to silence byte-compiler, tho.
You are right. Thanks.
>> If so, maybe something like the attached, though the la
Rasmus writes:
> Can we have conditional dependence on texmathp?
I guess it doesn't hurt. You need to declare it as an external function
in order to silence byte-compiler, tho.
> If so, maybe something like the attached, though the latex-environment
> part is ugly.
Another option is to simply
Nicolas Goaziou writes:
> Rasmus writes:
>
>> Nicolas Goaziou writes:
>>
>>> However, "tab:orgtable1" or "sec:orgheadline1" are fine, IMO, since
>>> "org" part can keep the label out of userland.
>>
>> That's fine with me as well.
>
> Fair enough. Do you want to take care of extending `org-late
Rasmus writes:
> Nicolas Goaziou writes:
>
>> However, "tab:orgtable1" or "sec:orgheadline1" are fine, IMO, since
>> "org" part can keep the label out of userland.
>
> That's fine with me as well.
Fair enough. Do you want to take care of extending `org-latex--label'
appropriately?
Regards,
Nicolas Goaziou writes:
> However, "tab:orgtable1" or "sec:orgheadline1" are fine, IMO, since
> "org" part can keep the label out of userland.
That's fine with me as well.
—Rasmus
--
Evidence suggests Snowden used a powerful tool called monospaced fonts
Rasmus writes:
> No, like orgheadline1 → sec:headline1 and orgtable1 → tab:table1. It
> seems a bit repetitive.
I think this is no good.
"tab:table1" is something a user can use for its own LaTeX code, e.g. in
a latex block or environment. In this case, it might interfere with
Org's "tab:table
Nicolas Goaziou writes:
> Rasmus writes:
>
>> So we could replace ^org with a mapping, e.g. "headline" → "sec:" and
>> "table" → "tab:". Then there's the added safety of TYPE-NUMBER and the
>> expected prefix.
>
> Do you mean "orgheadline1" becomes "orgsec:1" and "orgtable1" becomes
> "orgtab:1
Rasmus writes:
> So we could replace ^org with a mapping, e.g. "headline" → "sec:" and
> "table" → "tab:". Then there's the added safety of TYPE-NUMBER and the
> expected prefix.
Do you mean "orgheadline1" becomes "orgsec:1" and "orgtable1" becomes
"orgtab:1"? In this case, I don't mind, as lon
Nicolas Goaziou writes:
> Rasmus writes:
>
>> That's what I meant. Or rather a wrapper like org-latex--label. A
>> mapping like the one that was reverted for ox-latex only. Or are there
>> pitfalls in that approach?
>
> It will not give you predictability either since you cannot guess "4" in
Rasmus writes:
> That's what I meant. Or rather a wrapper like org-latex--label. A
> mapping like the one that was reverted for ox-latex only. Or are there
> pitfalls in that approach?
It will not give you predictability either since you cannot guess "4" in
"sec:4". Also, it is dangerous sinc
Nicolas Goaziou writes:
>> I realize. /I/ think we should do better.
>
> The only way to do better I can think of is to let "ox-latex.el"
> implements its own labelling scheme, without relying on
> `org-export-get-reference', which is not mandatory anyway.
That's what I meant. Or rather a wra
Rasmus writes:
> I think it's very important that ox-latex outputs are also consumable. I
> don't want to create another LyX. Of course we are very far from this
> point.
[...]
> I realize. /I/ think we should do better.
The only way to do better I can think of is to let "ox-latex.el"
imple
Hi,
Nicolas Goaziou writes:
>> I hope you had a nice time "offline".
>
> Yes I had, thank you.
Cool!
>> I think the label naming is worse now, and I think it's important to
>> produce good quality labels akin to what you would expect from e.g.
>> AUCTeX.
>
> The goal is completely different. A
Rasmus writes:
> I hope you had a nice time "offline".
Yes I had, thank you.
> I think the label naming is worse now, and I think it's important to
> produce good quality labels akin to what you would expect from e.g.
> AUCTeX.
The goal is completely different. AUCTeX generates good quality la
On Sun, Apr 19, 2015 at 03:56:22PM +0200, Nicolas Goaziou wrote:
> Suvayu Ali writes:
>
> > Ah, that was my report, that option did not work for me completely.
> > See: http://thread.gmane.org/gmane.emacs.orgmode/96887/focus=96888.
> >
> > To summarise quickly, with the above option set to t all
Hi Nicolas,
I hope you had a nice time "offline".
Nicolas Goaziou writes:
> This is why I suggest to rever commit cf7d64f. It also introduces
> a non-alphanumeric character ":", even though `org-export-get-reference'
> uses only alphanumeric ones by portability concern (it is even specified
> i
Suvayu Ali writes:
> Ah, that was my report, that option did not work for me completely.
> See: http://thread.gmane.org/gmane.emacs.orgmode/96887/focus=96888.
>
> To summarise quickly, with the above option set to t all
> references/links behave as I expect, except the ones where the target is
>
Hi Nicolas,
On Sun, Apr 19, 2015 at 03:40:07PM +0200, Nicolas Goaziou wrote:
> Suvayu Ali writes:
>
> > Okay I see it now, in your last email I got a bit confused, but now I
> > follow. With your solution I use both label and reference using LaTeX,
> > bypassing Org. Of course this leaves me w
Suvayu Ali writes:
> Okay I see it now, in your last email I got a bit confused, but now I
> follow. With your solution I use both label and reference using LaTeX,
> bypassing Org. Of course this leaves me with links not working inside
> Org. I was eventually going to use filters to transform
Hi Nicolas,
On Sun, Apr 19, 2015 at 02:57:09PM +0200, Nicolas Goaziou wrote:
> Suvayu Ali writes:
>
> > Sorry, I don't think I quite understand. AFAIU, targets like
> > <> have to be unique even inside the Org buffer for links
> > like this to work: [[interesting][very cool]], regardless of exp
Hello,
Suvayu Ali writes:
> Sorry, I don't think I quite understand. AFAIU, targets like
> <> have to be unique even inside the Org buffer for links
> like this to work: [[interesting][very cool]], regardless of export. So
> then why rename them during export?
There's no guarantee that, e.g.,
Hi Nicolas,
On Sat, Apr 18, 2015 at 11:53:01PM +0200, Nicolas Goaziou wrote:
> Hello,
>
> Rasmus writes:
>
> > Suvayu Ali writes:
> >
> >> Hi Rasmus,
> >>
> >> On Thu, Apr 16, 2015 at 12:57:46AM +0200, Rasmus wrote:
> >>>
> >>> Could you try the attached patches and see if they solve your iss
Hello,
Rasmus writes:
> Suvayu Ali writes:
>
>> Hi Rasmus,
>>
>> On Thu, Apr 16, 2015 at 12:57:46AM +0200, Rasmus wrote:
>>>
>>> Could you try the attached patches and see if they solve your issues?
>>
>> Seems to work nicely. I'll keep using them rest of the week.
>
> Pushed.
>
> I removed s
Suvayu Ali writes:
> Hi Rasmus,
>
> On Thu, Apr 16, 2015 at 12:57:46AM +0200, Rasmus wrote:
>>
>> Could you try the attached patches and see if they solve your issues?
>
> Seems to work nicely. I'll keep using them rest of the week.
Pushed.
I removed support for radio targets as I don't reall
Hi Rasmus,
On Thu, Apr 16, 2015 at 12:57:46AM +0200, Rasmus wrote:
>
> Could you try the attached patches and see if they solve your issues?
Seems to work nicely. I'll keep using them rest of the week.
Thanks, :)
--
Suvayu
Open source is the future. It sets us free.
Hi,
Could you try the attached patches and see if they solve your issues?
Thanks,
Rasmus
--
C is for Cookie
>From 8951c689a7812d6557ba65888e549013814e5f8a Mon Sep 17 00:00:00 2001
From: Rasmus
Date: Wed, 15 Apr 2015 21:50:53 +0200
Subject: [PATCH 2/2] ox: Change label naming scheme
* ox.el (o
Rasmus writes:
> Hi,
>
> Suvayu Ali writes:
>
>>> references, so \secref{sec:foo}, \figref{fig:bar}, \tabref{sec:baz} (it
>>> even takes care of language, or punctuation as needed!). Now if the
>>> target text changes from sec:foo to orgtarget1, of course the link
>>> breaks.
>>
>> The commit 4b
Hi,
Suvayu Ali writes:
>> references, so \secref{sec:foo}, \figref{fig:bar}, \tabref{sec:baz} (it
>> even takes care of language, or punctuation as needed!). Now if the
>> target text changes from sec:foo to orgtarget1, of course the link
>> breaks.
>
> The commit 4bbc054 introduces a variable
Hi,
I found a partial answer.
On Tue, Apr 14, 2015 at 11:25:30AM +0200, Suvayu Ali wrote:
>
> I am exporting Org files to LaTeX. I noticed something strange
> happening. The text of all my target text gets changed to `orgtargetn'
> where n is some number. This breaks a lot of my LaTeX specifi
Hello everyone,
I am exporting Org files to LaTeX. I noticed something strange
happening. The text of all my target text gets changed to `orgtargetn'
where n is some number. This breaks a lot of my LaTeX specific links.
For example, I use the varioref package to get entity specific
references,
35 matches
Mail list logo
