Nicolas Goaziou writes:
> OK, let's try it. Time will tell.
>
> Installed in 1c1936fbb1f0c42e5c7e1d3c903626aa5993a357.
Thanks,
--
Bastien
Hello,
Bastien writes:
> That's quite a premature and unstable intuition, but I think it's
> worth trying if your intuition goes in the same direction. Otherwise
> let's just prevent apostrophes.
OK, let's try it. Time will tell.
Installed in 1c1936fbb1f0c42e5c7e1d3c903626aa5993a357.
Regard
Hi Nicolas,
Nicolas Goaziou writes:
> However, I'm not sure this is something desirable, but the apostrophe
> problem is mildly annoying.
My intuition is that midword matching will soon be used as a neat
trick, while preventing "target's" to match "<<>>" will prove
annoying. Also, one can easi
Bastien writes:
> It looks perfect. I tested* the HTML and LaTeX backend and they do
> exactly what's expected. Thanks a lot for putting this together!
Applied.
--
Nicolas Goaziou
Hello,
Bastien writes:
> It looks perfect. I tested* the HTML and LaTeX backend and they do
> exactly what's expected. Thanks a lot for putting this together!
There is still a limitation (which was already present before the
patch), though. The regexp cannot match a radio link next to an
apos
Hi Nicolas,
Nicolas Goaziou writes:
> Here are 3 patches (for maint) fixing radio-target behaviour.
It looks perfect. I tested* the HTML and LaTeX backend and they do
exactly what's expected. Thanks a lot for putting this together!
* With quite a complex radio link like the one in the attach
Hello,
Bastien writes:
> Nicolas Goaziou writes:
>
>> For example, `org-make-target-link-regexp' generates a regexp enclosed
>> within "\\<...\\>". Unfortunately, that will not match a radio link
>> starting with an entity, e.g., <<<\alpha-test>>> \alpha-test. It is
>> probably due to the fact
Noah Slater writes:
> Or perhaps to survey what is already out there. What are people
> already doing/trying to do?
I opened a different thread to make the poll more prominent.
--
Bastien
Or perhaps to survey what is already out there. What are people already
doing/trying to do?
On 21 March 2014 18:28, Bastien wrote:
> Hi Nicolas,
>
> Nicolas Goaziou writes:
>
> > It would probably make my life less miserable. But do radio target users
> > need entities within?
>
> IMHO the bes
Hi Nicolas,
Nicolas Goaziou writes:
> It would probably make my life less miserable. But do radio target users
> need entities within?
IMHO the best way to know is to open a new thread with [POLL]
and a very clear subject like
"[POLL] Do you need special entities in radio target?"
2 cents,
Bastien writes:
> FWIW, I'd be fine to only allow plain text in radio targets, instead
> of the full syntax. Your take.
It would probably make my life less miserable. But do radio target users
need entities within?
Regards,
--
Nicolas Goaziou
Hi Nicolas,
Nicolas Goaziou writes:
> For example, `org-make-target-link-regexp' generates a regexp enclosed
> within "\\<...\\>". Unfortunately, that will not match a radio link
> starting with an entity, e.g., <<<\alpha-test>>> \alpha-test. It is
> probably due to the fact that radio targets w
Hello,
Bastien writes:
> Bastien writes:
>
>> Can you make the change (ie. radio-link is a link with a description,
>> the description being its parsed path)? If so, do you want me to make
>> the change in the backends or do you want to take care of this too?
>
> I see you reverted related com
Hi Nicolas,
Bastien writes:
> Can you make the change (ie. radio-link is a link with a description,
> the description being its parsed path)? If so, do you want me to make
> the change in the backends or do you want to take care of this too?
I see you reverted related commits -- are you on thi
Hi Nicolas,
Nicolas Goaziou writes:
> path is always a string. Description is always parsed (and transcoded
> already). In the most simple cases, they are equals.
I found out I have to parse the path because "hello \alpha" would not
be exported correctly otherwise. (But I agree this is a corne
Bastien writes:
> Bastien writes:
>
>> If we do this, I don't see the need to enforce case sensitivity.
>
> I attach a patch that illustrates the fix I propose on top on my
> previous commit.
I somehow missed this message.
> With this,
>
> ==
Nicolas Goaziou writes:
> I see the capitalization problem, but I still don't understand why you
> think target and description are inverted.
Well, they are.
Okay, again:
<<>>
hello world
Bastien writes:
> Nicolas Goaziou writes:
>
>>
>> Hello World
>>
>>
>>
>> Let’s say Hello World to test.
>>
>> It looks good to me.
>
> The target is the radio link: "Hello World".
>
> The link description in the second paragraph is "hello world".
>
> So the output is not good:
>
> 1) Hello W
Nicolas Goaziou writes:
>
> Hello World
>
>
>
> Let’s say Hello World to test.
>
> It looks good to me.
The target is the radio link: "Hello World".
The link description in the second paragraph is "hello world".
So the output is not good:
1) Hello World should be
Hello World
^
Bastien writes:
> I don't get the logic: the output text has two parts: the target of
> the link, the description of the link. It the example above, the
> Target is "Hello World", and should be rewritten "Hello-World" to
> escape spaces. The description is "hello world" and should not be
> rewr
Bastien writes:
> If we do this, I don't see the need to enforce case sensitivity.
I attach a patch that illustrates the fix I propose on top on my
previous commit.
With this,
<<>>
Let's say hello \alpha world to test.
=
Hi Nicolas,
thanks for looking into this.
Nicolas Goaziou writes:
> Actually, even though it works if you test it on cases like:
>
> <<>> foo
>
> it isn't right on more complex cases:
>
> <<>> with \alpha
True.
It is not right on simpler example too, with just spaces:
==
Hello,
Bastien writes:
> Nicolas, I modified the logic for radio link export in ox-html.el,
> ox-latex.el and ox-beamer.el. I also modified the use of the target
> instead of the path in ox-ascii.el. Can you review this change
> (http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=d2e7b1b) and
Hi Noah,
Noah Slater writes:
> Experiencing a bug with radio targets and html export.
>
> IF set a radio target like <<> then the text foo in the body
> will be linked to #foo, but the radio target has an anchor id of Foo,
> so the link doesn't work.
>
> I expected the foo text to be linked to #
Experiencing a bug with radio targets and html export.
IF set a radio target like <<> then the text foo in the body will be
linked to #foo, but the radio target has an anchor id of Foo, so the link
doesn't work.
I expected the foo text to be linked to #Foo instead.
25 matches
Mail list logo
