* Raw LaTeX: {} at the end @ 2019-04-08 11:30 Axel Rauschmayer [not found] ` <d1c09584-2926-489d-b873-1dfc2464d9d8-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 17+ messages in thread From: Axel Rauschmayer @ 2019-04-08 11:30 UTC (permalink / raw) To: pandoc-discuss [-- Attachment #1.1: Type: text/plain, Size: 891 bytes --] In LaTeX, you occasionally use macros like this: namespace\fshyp{}container Problem: My filter (for HTML) only receives the raw LaTeX \fshyp (without the curly braces). - Would it make sense to change this parsing behavior of Pandoc? - Work-around (which is a bit ugly): namespace`\fshyp{}`{=latex}container -- You received this message because you are subscribed to the Google Groups "pandoc-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/d1c09584-2926-489d-b873-1dfc2464d9d8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. [-- Attachment #1.2: Type: text/html, Size: 1585 bytes --] ^ permalink raw reply [flat|nested] 17+ messages in thread
[parent not found: <d1c09584-2926-489d-b873-1dfc2464d9d8-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Raw LaTeX: {} at the end [not found] ` <d1c09584-2926-489d-b873-1dfc2464d9d8-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2019-04-08 19:06 ` John MacFarlane [not found] ` <m2ftqsco60.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org> 0 siblings, 1 reply; 17+ messages in thread From: John MacFarlane @ 2019-04-08 19:06 UTC (permalink / raw) To: Axel Rauschmayer, pandoc-discuss Is this a macro with one argument, and you're passing in an empty argument? Or are you just using `{}` to separate `\fshyp` from the following word? Axel Rauschmayer <rauschma-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes: > In LaTeX, you occasionally use macros like this: > > namespace\fshyp{}container > > > Problem: My filter (for HTML) only receives the raw LaTeX \fshyp (without > the curly braces). > > - Would it make sense to change this parsing behavior of Pandoc? > - Work-around (which is a bit ugly): namespace`\fshyp{}`{=latex}container > > -- > You received this message because you are subscribed to the Google Groups "pandoc-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/d1c09584-2926-489d-b873-1dfc2464d9d8%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. ^ permalink raw reply [flat|nested] 17+ messages in thread
[parent not found: <m2ftqsco60.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>]
* Re: Raw LaTeX: {} at the end [not found] ` <m2ftqsco60.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org> @ 2019-04-08 19:24 ` Axel Rauschmayer [not found] ` <2c050519-afd0-4406-b75b-7601ae398771-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 17+ messages in thread From: Axel Rauschmayer @ 2019-04-08 19:24 UTC (permalink / raw) To: pandoc-discuss [-- Attachment #1.1: Type: text/plain, Size: 632 bytes --] The latter. But the former also seems like it could happen. -- You received this message because you are subscribed to the Google Groups "pandoc-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/2c050519-afd0-4406-b75b-7601ae398771%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. [-- Attachment #1.2: Type: text/html, Size: 1044 bytes --] ^ permalink raw reply [flat|nested] 17+ messages in thread
[parent not found: <2c050519-afd0-4406-b75b-7601ae398771-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Raw LaTeX: {} at the end [not found] ` <2c050519-afd0-4406-b75b-7601ae398771-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2019-04-09 6:42 ` BPJ [not found] ` <CADAJKhCb29ke3ODj3XYFU7USyMpiTuxUtrCs0br6xkNq59P61w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2019-04-09 14:40 ` John MacFarlane 1 sibling, 1 reply; 17+ messages in thread From: BPJ @ 2019-04-09 6:42 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 1890 bytes --] Supposing that you mean how to enter the raw LaTeX into the markdown I always just use `\foo{}bar`. It gives the expected result, i.e. the braces become part of the raw TeX inline: ````native [Para [RawInline (Format "tex") "\\foo{}",Str "bar"]] ```` The empty braces should always be harmless, or aren't they? Or do you experience/expect something else? /bpj Den mån 8 apr. 2019 21:25Axel Rauschmayer <rauschma-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> skrev: > The latter. But the former also seems like it could happen. > > -- > You received this message because you are subscribed to the Google Groups > "pandoc-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To view this discussion on the web visit > https://groups.google.com/d/msgid/pandoc-discuss/2c050519-afd0-4406-b75b-7601ae398771%40googlegroups.com > <https://groups.google.com/d/msgid/pandoc-discuss/2c050519-afd0-4406-b75b-7601ae398771%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "pandoc-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhCb29ke3ODj3XYFU7USyMpiTuxUtrCs0br6xkNq59P61w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. [-- Attachment #2: Type: text/html, Size: 3173 bytes --] ^ permalink raw reply [flat|nested] 17+ messages in thread
[parent not found: <CADAJKhCb29ke3ODj3XYFU7USyMpiTuxUtrCs0br6xkNq59P61w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: Raw LaTeX: {} at the end [not found] ` <CADAJKhCb29ke3ODj3XYFU7USyMpiTuxUtrCs0br6xkNq59P61w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2019-04-09 11:39 ` Axel Rauschmayer 0 siblings, 0 replies; 17+ messages in thread From: Axel Rauschmayer @ 2019-04-09 11:39 UTC (permalink / raw) To: pandoc-discuss [-- Attachment #1.1: Type: text/plain, Size: 988 bytes --] I’ve switched to a different approach now. But in principle, the problem is that I always target both LaTeX and HTML. With the latter, I don’t want to have the empty braces. Example: INPUT: foo\bar{}baz AST: [Para [Str "foo",RawInline (Format "tex") "\\bar",Str "{}baz"]] Here, I can’t use my own Lua filter to implement \bar{} for HTML, because that filter will miss the empty braces. -- You received this message because you are subscribed to the Google Groups "pandoc-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/5878e33c-4f91-46ee-9b78-b610b6a484f9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. [-- Attachment #1.2: Type: text/html, Size: 1632 bytes --] ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Raw LaTeX: {} at the end [not found] ` <2c050519-afd0-4406-b75b-7601ae398771-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2019-04-09 6:42 ` BPJ @ 2019-04-09 14:40 ` John MacFarlane [not found] ` <m2y34jb5tj.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org> 1 sibling, 1 reply; 17+ messages in thread From: John MacFarlane @ 2019-04-09 14:40 UTC (permalink / raw) To: Axel Rauschmayer, pandoc-discuss I think it would be reasonable to include the {} in the tex. You are welcome to open an issue about this. You can also use the raw attribute: `\foo{}`{=latex} Axel Rauschmayer <rauschma-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes: > The latter. But the former also seems like it could happen. > > -- > You received this message because you are subscribed to the Google Groups "pandoc-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/2c050519-afd0-4406-b75b-7601ae398771%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. ^ permalink raw reply [flat|nested] 17+ messages in thread
[parent not found: <m2y34jb5tj.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>]
* Re: Raw LaTeX: {} at the end [not found] ` <m2y34jb5tj.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org> @ 2019-04-09 16:28 ` BPJ [not found] ` <CADAJKhADTV-3OpzVE6O+zZ49CJOmvEzAQ_V_9aheTKJ-is0i5g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 17+ messages in thread From: BPJ @ 2019-04-09 16:28 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 2398 bytes --] For me the braces are included in the TeX. The example I posted earlier today was generated with http://pandoc.org/try/?text=%5Cfoo%7B%7Dbar&from=markdown&to=native also with the braces included in the TeX. Den tis 9 apr. 2019 16:41John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> skrev: > > I think it would be reasonable to include the {} in > the tex. You are welcome to open an issue about this. > > You can also use the raw attribute: > > `\foo{}`{=latex} > > Axel Rauschmayer <rauschma-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes: > > > The latter. But the former also seems like it could happen. > > > > -- > > You received this message because you are subscribed to the Google > Groups "pandoc-discuss" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To view this discussion on the web visit > https://groups.google.com/d/msgid/pandoc-discuss/2c050519-afd0-4406-b75b-7601ae398771%40googlegroups.com > . > > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "pandoc-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To view this discussion on the web visit > https://groups.google.com/d/msgid/pandoc-discuss/m2y34jb5tj.fsf%40johnmacfarlane.net > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "pandoc-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhADTV-3OpzVE6O%2BzZ49CJOmvEzAQ_V_9aheTKJ-is0i5g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. [-- Attachment #2: Type: text/html, Size: 4311 bytes --] ^ permalink raw reply [flat|nested] 17+ messages in thread
[parent not found: <CADAJKhADTV-3OpzVE6O+zZ49CJOmvEzAQ_V_9aheTKJ-is0i5g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: Raw LaTeX: {} at the end [not found] ` <CADAJKhADTV-3OpzVE6O+zZ49CJOmvEzAQ_V_9aheTKJ-is0i5g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2019-04-09 16:31 ` Axel Rauschmayer [not found] ` <62da4610-bd15-44ed-97c6-e554c1d20313-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 0 siblings, 1 reply; 17+ messages in thread From: Axel Rauschmayer @ 2019-04-09 16:31 UTC (permalink / raw) To: pandoc-discuss [-- Attachment #1.1: Type: text/plain, Size: 902 bytes --] > > For me the braces are included in the TeX. The example I posted earlier > today was generated with > http://pandoc.org/try/?text=%5Cfoo%7B%7Dbar&from=markdown&to=native > > also with the braces included in the TeX. > Yes! My example is different: http://pandoc.org/try/?text=foo%5Cbar%7B%7Dbaz&from=markdown&to=native -- You received this message because you are subscribed to the Google Groups "pandoc-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/62da4610-bd15-44ed-97c6-e554c1d20313%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. [-- Attachment #1.2: Type: text/html, Size: 2367 bytes --] ^ permalink raw reply [flat|nested] 17+ messages in thread
[parent not found: <62da4610-bd15-44ed-97c6-e554c1d20313-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]
* Re: Raw LaTeX: {} at the end [not found] ` <62da4610-bd15-44ed-97c6-e554c1d20313-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> @ 2019-04-09 16:46 ` BPJ [not found] ` <CADAJKhD9pD-NwT0zb7viL0zQfk-YmbexeK0Hi-vYy7K=wP8RhA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 17+ messages in thread From: BPJ @ 2019-04-09 16:46 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 1921 bytes --] I definitely consider the different behavior in these two cases a bug, and I also consider including the braces in the TeX to be the only sensible behavior. Den tis 9 apr. 2019 18:32Axel Rauschmayer <rauschma-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> skrev: > For me the braces are included in the TeX. The example I posted earlier >> today was generated with > > >> http://pandoc.org/try/?text=%5Cfoo%7B%7Dbar&from=markdown&to=native >> >> also with the braces included in the TeX. >> > > Yes! My example is different: > http://pandoc.org/try/?text=foo%5Cbar%7B%7Dbaz&from=markdown&to=native > > -- > You received this message because you are subscribed to the Google Groups > "pandoc-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To view this discussion on the web visit > https://groups.google.com/d/msgid/pandoc-discuss/62da4610-bd15-44ed-97c6-e554c1d20313%40googlegroups.com > <https://groups.google.com/d/msgid/pandoc-discuss/62da4610-bd15-44ed-97c6-e554c1d20313%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "pandoc-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhD9pD-NwT0zb7viL0zQfk-YmbexeK0Hi-vYy7K%3DwP8RhA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. [-- Attachment #2: Type: text/html, Size: 3638 bytes --] ^ permalink raw reply [flat|nested] 17+ messages in thread
[parent not found: <CADAJKhD9pD-NwT0zb7viL0zQfk-YmbexeK0Hi-vYy7K=wP8RhA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: Raw LaTeX: {} at the end [not found] ` <CADAJKhD9pD-NwT0zb7viL0zQfk-YmbexeK0Hi-vYy7K=wP8RhA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2019-04-09 17:00 ` John MacFarlane [not found] ` <yh480kef6b5d25.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org> 2019-04-09 17:06 ` John MacFarlane 1 sibling, 1 reply; 17+ messages in thread From: John MacFarlane @ 2019-04-09 17:00 UTC (permalink / raw) To: BPJ, pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw This is crazy! http://pandoc.org/try/?text=%5Cfoo%7B%7Dbar%0A%0A%5Cbar%7B%7Dbaz%0A&from=markdown&to=native The only difference between these is whether the string is foo or bar. I can't see how that could possibly cause different parsing! Anyway, someone should submit an issue with this case. ^ permalink raw reply [flat|nested] 17+ messages in thread
[parent not found: <yh480kef6b5d25.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>]
* Re: Raw LaTeX: {} at the end [not found] ` <yh480kef6b5d25.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org> @ 2019-04-09 18:11 ` Axel Rauschmayer 0 siblings, 0 replies; 17+ messages in thread From: Axel Rauschmayer @ 2019-04-09 18:11 UTC (permalink / raw) To: pandoc-discuss [-- Attachment #1.1: Type: text/plain, Size: 628 bytes --] GitHub issue: https://github.com/jgm/pandoc/issues/5439 -- You received this message because you are subscribed to the Google Groups "pandoc-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/02b271c5-8eb1-439a-9aa6-26e938026fc7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. [-- Attachment #1.2: Type: text/html, Size: 1041 bytes --] ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Raw LaTeX: {} at the end [not found] ` <CADAJKhD9pD-NwT0zb7viL0zQfk-YmbexeK0Hi-vYy7K=wP8RhA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2019-04-09 17:00 ` John MacFarlane @ 2019-04-09 17:06 ` John MacFarlane [not found] ` <yh480kbm1f5cro.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org> 1 sibling, 1 reply; 17+ messages in thread From: John MacFarlane @ 2019-04-09 17:06 UTC (permalink / raw) To: BPJ, pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw Ah, I see what is going on. \bar is already a supported inline command in the LaTeX reader. And this command doesn't take arguments. That's why the {} isn't included, but is with \foo. One could still argue that in parsing raw LaTeX one should always absorb a following {}. ^ permalink raw reply [flat|nested] 17+ messages in thread
[parent not found: <yh480kbm1f5cro.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>]
* Re: Raw LaTeX: {} at the end [not found] ` <yh480kbm1f5cro.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org> @ 2019-04-09 17:22 ` BPJ [not found] ` <CADAJKhDwq20rrRFOyjM_Z40bfH7MigC=S7vYHdk8DzfrBQTRMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2019-04-09 18:02 ` Axel Rauschmayer 1 sibling, 1 reply; 17+ messages in thread From: BPJ @ 2019-04-09 17:22 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 1295 bytes --] Yes one should because adding an empty group is a common strategy to avoid having to insert a space which will be gobbled, and with pandoc you pretty much have to do it since a following space will be parsed as a Space, but in the output TeX will gobble that space anyway unless you protect it with an empty group. Den tis 9 apr. 2019 19:06John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> skrev: > > Ah, I see what is going on. > > \bar is already a supported inline command in the LaTeX > reader. And this command doesn't take arguments. That's why > the {} isn't included, but is with \foo. > > One could still argue that in parsing raw LaTeX one > should always absorb a following {}. > > -- You received this message because you are subscribed to the Google Groups "pandoc-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhDwq20rrRFOyjM_Z40bfH7MigC%3DS7vYHdk8DzfrBQTRMg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. [-- Attachment #2: Type: text/html, Size: 2030 bytes --] ^ permalink raw reply [flat|nested] 17+ messages in thread
[parent not found: <CADAJKhDwq20rrRFOyjM_Z40bfH7MigC=S7vYHdk8DzfrBQTRMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: Raw LaTeX: {} at the end [not found] ` <CADAJKhDwq20rrRFOyjM_Z40bfH7MigC=S7vYHdk8DzfrBQTRMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2019-04-09 18:43 ` John MacFarlane [not found] ` <yh480kwok33tp5.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org> 0 siblings, 1 reply; 17+ messages in thread From: John MacFarlane @ 2019-04-09 18:43 UTC (permalink / raw) To: BPJ, pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes: > Yes one should because adding an empty group is a common strategy to avoid > having to insert a space which will be gobbled, and with pandoc you pretty > much have to do it since a following space will be parsed as a Space, but > in the output TeX will gobble that space anyway unless you protect it with > an empty group. Not so, at least not with the current version! % pandoc -t native \my tex [Para [RawInline (Format "tex") "\\my ",Str "tex"]] ^ permalink raw reply [flat|nested] 17+ messages in thread
[parent not found: <yh480kwok33tp5.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>]
* Re: Raw LaTeX: {} at the end [not found] ` <yh480kwok33tp5.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org> @ 2019-04-09 19:24 ` BPJ [not found] ` <CADAJKhBmGU5b=2Ct-Euwqhi0j0tPQroGK450+4DX-SEpkcGo_w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 17+ messages in thread From: BPJ @ 2019-04-09 19:24 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw [-- Attachment #1: Type: text/plain, Size: 1306 bytes --] Yes but *LaTeX* will eat the space eventually unless it is protected. Den tis 9 apr. 2019 20:44John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> skrev: > BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes: > > > Yes one should because adding an empty group is a common strategy to > avoid > > having to insert a space which will be gobbled, and with pandoc you > pretty > > much have to do it since a following space will be parsed as a Space, but > > in the output TeX will gobble that space anyway unless you protect it > with > > an empty group. > > > Not so, at least not with the current version! > > % pandoc -t native > \my tex > [Para [RawInline (Format "tex") "\\my ",Str "tex"]] > > -- You received this message because you are subscribed to the Google Groups "pandoc-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhBmGU5b%3D2Ct-Euwqhi0j0tPQroGK450%2B4DX-SEpkcGo_w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. [-- Attachment #2: Type: text/html, Size: 2193 bytes --] ^ permalink raw reply [flat|nested] 17+ messages in thread
[parent not found: <CADAJKhBmGU5b=2Ct-Euwqhi0j0tPQroGK450+4DX-SEpkcGo_w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: Raw LaTeX: {} at the end [not found] ` <CADAJKhBmGU5b=2Ct-Euwqhi0j0tPQroGK450+4DX-SEpkcGo_w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2019-04-10 4:01 ` John MacFarlane 0 siblings, 0 replies; 17+ messages in thread From: John MacFarlane @ 2019-04-10 4:01 UTC (permalink / raw) To: BPJ, pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes: > Yes but *LaTeX* will eat the space eventually unless it is protected. Right, that's the point. There won't be a space with aaa\foo bbb so you could just use this form instead of aaa\foo{}bbb ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Raw LaTeX: {} at the end [not found] ` <yh480kbm1f5cro.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org> 2019-04-09 17:22 ` BPJ @ 2019-04-09 18:02 ` Axel Rauschmayer 1 sibling, 0 replies; 17+ messages in thread From: Axel Rauschmayer @ 2019-04-09 18:02 UTC (permalink / raw) To: pandoc-discuss [-- Attachment #1.1: Type: text/plain, Size: 959 bytes --] Ah, amazing – I didn’t even consider that changing the command name could have an effect, but it does (I thought it was about text preceding the command): namespace\fshyp{}container [Para [Str "namespace",RawInline (Format "tex") "\\fshyp",Str "{}container"]] namespace\aaa{}container [Para [Str "namespace",RawInline (Format "tex") "\\aaa{}",Str "container"]] -- You received this message because you are subscribed to the Google Groups "pandoc-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/2ad2480d-91cc-4627-b903-e9ed744aa82e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. [-- Attachment #1.2: Type: text/html, Size: 1730 bytes --] ^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2019-04-10 4:01 UTC | newest] Thread overview: 17+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2019-04-08 11:30 Raw LaTeX: {} at the end Axel Rauschmayer [not found] ` <d1c09584-2926-489d-b873-1dfc2464d9d8-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2019-04-08 19:06 ` John MacFarlane [not found] ` <m2ftqsco60.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org> 2019-04-08 19:24 ` Axel Rauschmayer [not found] ` <2c050519-afd0-4406-b75b-7601ae398771-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2019-04-09 6:42 ` BPJ [not found] ` <CADAJKhCb29ke3ODj3XYFU7USyMpiTuxUtrCs0br6xkNq59P61w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2019-04-09 11:39 ` Axel Rauschmayer 2019-04-09 14:40 ` John MacFarlane [not found] ` <m2y34jb5tj.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org> 2019-04-09 16:28 ` BPJ [not found] ` <CADAJKhADTV-3OpzVE6O+zZ49CJOmvEzAQ_V_9aheTKJ-is0i5g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2019-04-09 16:31 ` Axel Rauschmayer [not found] ` <62da4610-bd15-44ed-97c6-e554c1d20313-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2019-04-09 16:46 ` BPJ [not found] ` <CADAJKhD9pD-NwT0zb7viL0zQfk-YmbexeK0Hi-vYy7K=wP8RhA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2019-04-09 17:00 ` John MacFarlane [not found] ` <yh480kef6b5d25.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org> 2019-04-09 18:11 ` Axel Rauschmayer 2019-04-09 17:06 ` John MacFarlane [not found] ` <yh480kbm1f5cro.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org> 2019-04-09 17:22 ` BPJ [not found] ` <CADAJKhDwq20rrRFOyjM_Z40bfH7MigC=S7vYHdk8DzfrBQTRMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2019-04-09 18:43 ` John MacFarlane [not found] ` <yh480kwok33tp5.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org> 2019-04-09 19:24 ` BPJ [not found] ` <CADAJKhBmGU5b=2Ct-Euwqhi0j0tPQroGK450+4DX-SEpkcGo_w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2019-04-10 4:01 ` John MacFarlane 2019-04-09 18:02 ` Axel Rauschmayer
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).