Re: [O] Radio targets

Hi, OK, thank you. I am using emacs with spacemacs and it is still using the melpa version of orgmode as I am unable to get it to load the git branch of orgmode. I will try it out once I make the switch. On Sun, Apr 16, 2017 at 2:54 AM, Nicolas Goaziou wrote: > Hello, >

Re: [O] Radio targets

Hello, R C writes: > Please see attached. The org file is just: > > * <<>> heading > The discussion in *abc* highlights the issue. Fixed. Thank you. Regards, -- Nicolas Goaziou0x80A93738

Re: [O] Radio targets

Hello, R C writes: > Hi, > Please see attached. The org file is just: > > * <<>> heading > The discussion in *abc* highlights the issue. Thank you. Fixed. Regards, -- Nicolas Goaziou

Re: [O] Radio targets

Hi, Please see attached. The org file is just: * <<>> heading The discussion in *abc* highlights the issue. On Tue, Apr 11, 2017 at 5:28 AM, Nicolas Goaziou wrote: > Hello, > > R C writes: > > > I set up radio targets such as <<>> in a heading,

Re: [O] Radio targets

Hello, R C writes: > I set up radio targets such as <<>> in a heading, which makes all > occurrences of the word analysis to be links to the heading. However this > seems to override the boldface settings such *Analysis*, so that the > asterisks show up in the exported text.

[O] Radio targets

I set up radio targets such as <<>> in a heading, which makes all occurrences of the word analysis to be links to the heading. However this seems to override the boldface settings such *Analysis*, so that the asterisks show up in the exported text. Is there a way to get around this? Thanks.

Re: [O] radio targets, a bug?

Hi Thomas, thomas kalbe thomas.ka...@googlemail.com writes: (after that comes a number of weird symbols that I cannot even copy into the email...) What version of Org are you using? M-x org-version RET Thanks, -- Bastien

[O] radio targets, a bug?

Hi All, html-export for the following minimal example breaks: === Keyword1 keyword2 Keyword1 keyword2 === Error Message: org-export-activate-smart-quotes: Wrong number of arguments: #[(q type) ÆÇ\ƒ (after that comes a number of

[O] Radio Targets in Tables

Hi, I have the following two tables in a .org file: TABLE A | PM | Notebook | |-+| | TAD | [[./13939-SEC.org][13939-SEC]] | | KB | [[./13488-PAG.org][13488-PAG]] | TABLE B | Employee| Initials |

Re: [O] Radio Targets in Tables

Hello, R.T. redto...@yahoo.com writes: I have the following two tables in a .org file: TABLE A | PM | Notebook | |-+| | TAD | [[./13939-SEC.org][13939-SEC]] | | KB | [[./13488-PAG.org][13488-PAG]] | TABLE B | Employee

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Hello, Bastien b...@gnu.org 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

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Nicolas Goaziou n.goaz...@gmail.com writes: OK, let's try it. Time will tell. Installed in 1c1936fbb1f0c42e5c7e1d3c903626aa5993a357. Thanks, -- Bastien

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Hello, Bastien b...@gnu.org 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

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Bastien b...@gnu.org 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

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com 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 target will prove annoying.

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Hello, Bastien b...@gnu.org writes: Nicolas Goaziou n.goaz...@gmail.com 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

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com 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

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Hello, Bastien b...@gnu.org writes: Bastien b...@gnu.org 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

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com 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

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Bastien b...@gnu.org 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

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com 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

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Or perhaps to survey what is already out there. What are people already doing/trying to do? On 21 March 2014 18:28, Bastien b...@altern.org wrote: Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com writes: It would probably make my life less miserable. But do radio target users need

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Noah Slater nsla...@tumbolia.org 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

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Hi Nicolas, Bastien b...@gnu.org 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

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Hello, Bastien b...@gnu.org 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

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Hi Nicolas, thanks for looking into this. Nicolas Goaziou n.goaz...@gmail.com writes: Actually, even though it works if you test it on cases like: Foo foo it isn't right on more complex cases: with \alpha with \alpha True. It is not right on simpler example too, with just spaces:

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Bastien b...@gnu.org 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, Hello \alpha world Let's say

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Bastien b...@gnu.org 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

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Nicolas Goaziou n.goaz...@gmail.com writes: p a id=hello-worldHello World/a /p p Letrsquo;s say a href=#hello-worldHello World/a to test./p 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

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Bastien b...@gnu.org writes: Nicolas Goaziou n.goaz...@gmail.com writes: p a id=hello-worldHello World/a /p p Letrsquo;s say a href=#hello-worldHello World/a to test./p It looks good to me. The target is the radio link: Hello World. The link description in the second paragraph is

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Nicolas Goaziou n.goaz...@gmail.com 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 hello world

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Bastien b...@gnu.org writes: Bastien b...@gnu.org 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,

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com 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

Re: [O] Radio targets with mixed capitalisation do not work in HTML export

Hi Noah, Noah Slater nsla...@tumbolia.org writes: Experiencing a bug with radio targets and html export. IF set a radio target like Foo 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

[O] Radio targets with mixed capitalisation do not work in HTML export

Experiencing a bug with radio targets and html export. IF set a radio target like Foo 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.

[O] Radio targets in comment lines

Org 8 seems to have changed the way radio links in comment lines work. # target No longer creates a link - 'C-c C-c can do nothing useful at this location' #+test target Works within org for some reason, but then the line will be exported... I was curious if this was intentional, because I

Re: [O] Radio targets in comment lines

Hello, Steen Hoyer j.s.ho...@wustl.edu writes: Org 8 seems to have changed the way radio links in comment lines work. # target No longer creates a link - 'C-c C-c can do nothing useful at this location' #+test target Works within org for some reason, but then the line will be

Re: [O] Radio targets in comment lines

Thank you Nicolas! I will think about a patch for the FAQ. I don't quite understand one of your comments: There is no point in making radio targets invisible. I think that invisible radio targets are precisely what I want - that's why I made so many of them in comments under the old system.

Re: [O] Radio targets in comment lines

Steen Hoyer j.s.ho...@wustl.edu writes: Thank you Nicolas! I will think about a patch for the FAQ. I don't quite understand one of your comments: There is no point in making radio targets invisible. I think that invisible radio targets are precisely what I want - that's why I made so