Hi Ihor,
yes, the patch is just a step towards consistency, but I think is is an
important one, because it
makes org-mode not generate illegal/faulty LaTeX code.
As for the photo-finish, I have been thinking the following that we can use
the 'toc' document property.
Values nil and t work as inte
Ihor Radchenko writes:
Why does the mailing list name me " via General discussions about
Org-mode."? Is something not right with my subscription to the list?
>>>
>>> I suspect that it might be something to do with sending via newsgroups.
>>
>> I'm not sending via newsgroup, Just sending
Attaching the updated org-matlab.patch
On Thu, Jan 2, 2025 at 6:55 PM John C wrote:
> Hi
>
> Thanks for the feedback. See updated org-matlab.patch. Note
> code evaluation will now error out when using an out-of-date matlab-mode
> (rather than generating a warning) because when using an older mat
Hi
Thanks for the feedback. See updated org-matlab.patch. Note code evaluation
will now error out when using an out-of-date matlab-mode (rather than
generating a warning) because when using an older matlab-mode, code block
evaluation doesn't work. We need to wait for the matlab-shell to be ready.
On Thu Jan 2, 2025 at 6:47 PM CET, Ihor Radchenko wrote:
> "onf" writes:
> [...]
> > It's important to understand that troff commands don't really use
> > nesting or a stack as one might be used to from HTML and similar
> > markup languages. That's why it's also not possible to e.g. nest
> > bold
Malcolm Purvis writes:
> Thanks for the review and happy new year..
>
>>> -| {{{kbd(S)}}} | Sort reports by the column at point |
>> Looks like you deleted this line by accident.
>
> I've restored this in the patch below.
I think you can simply squash the fix with the original patch.
>> I
Thibaut Meyer writes:
>>> Why does the mailing list name me " via General discussions about
>>> Org-mode."? Is something not right with my subscription to the list?
>>
>> I suspect that it might be something to do with sending via newsgroups.
>
> I'm not sending via newsgroup, Just sending emails
Thibaut Meyer writes:
> * lisp/ob-tangle.el: (org-babel-tangle-collect-blocks): source blocks
> without a language are not ignored anymore, if they inherit a
> src-tfile other than "yes" or "no".
> * lisp/ob-core.el: adapts the org-babel-src-block-regexp regular
> expression to make the language
"onf" writes:
>> What about \fC\f[CR]Lorem\fP\fP?
>
> (1) if both C and CR exist, sets Lorem in Courier
> (2) if only C or CR exists, sets font to Courier
> (3) if neither exists, does nothing
>
> To understand #2, let's assume that C is defined and CR is not. Then:
> \fC -> set font to C
> \
Max Nikulin writes:
> On 31/12/2024 20:32, Ihor Radchenko wrote:
>> | $10 | foo | $\alpha$ |
>
> pandoc result matches my expectation:
>
> \$10 & foo & \(\alpha\) \\
How so?
I just tried
printf '%s\n' '| =10+20 | 30 | =foo= |' | pandoc -f org -t latex
\begin{longtable}[]{@{}l@{}}
\toprule\noali
On 31/12/2024 20:32, Ihor Radchenko wrote:
| $10 | foo | $\alpha$ |
pandoc result matches my expectation:
\$10 & foo & \(\alpha\) \\
| =10+20 | 30 | =foo= |
I found significantly more convincing cases with current parser when
emphasis end marker accidentally appears in the middle of a lin
Pedro Andres Aranda Gutierrez writes:
>>(1) At the moment, some export backends do not obey this
>> specification. For example, LaTeX export excludes every unnumbered
>> headline from the table of contents.
>>
>
> But this happens because of the way LaTeX works...
Sure. But I thought that y
On 31/12/2024 04:25, Rudolf Adamkovič wrote:
Max Nikulin writes:
An extensive test suite is necessary to consider alternatives for
parsing rules.
Yes, that much is given. Without an extensive test suite, working on a
parser would be nothing but a waste of time, and the end result would
be, at
Hi Ihor,
On Wed Jan 1, 2025 at 1:30 PM CET, onf wrote:
> On Wed Jan 1, 2025 at 10:38 AM CET, Ihor Radchenko wrote:
> > >> Also, what if we leave \fC and add \f[CR]/.EX on top?
> > >> AFAIU, the worst case scenario for \fC is that it does nothing. By
> > >> leaving it there, we thus retain old work
On Thu Jan 2, 2025 at 1:38 PM CET, G. Branden Robinson wrote:
> > > (I would also delete that trailing "\n". Avoid blank lines in man(7)
> > > input.[3])
> >
> > Do I understand correctly that blank line is sometimes interpreted as
> > vertical spacing and sometimes ignored?
>
> Yes. A blank lin
Hi Ihor,
At 2024-12-31T18:15:57+, Ihor Radchenko wrote:
> "G. Branden Robinson" writes:
>
> > I understand now. I've taken some time to learn a bit more about
> > Org mode, and also that org-man.el seems to be something close to
> > the bleeding edge; in a Debian unstable chroot it was not
Hi Ihor,
At 2025-01-01T09:38:37+, Ihor Radchenko wrote:
> "onf" writes:
>
> >> Also, what if we leave \fC and add \f[CR]/.EX on top?
> >> AFAIU, the worst case scenario for \fC is that it does nothing. By
> >> leaving it there, we thus retain old working exports working while also
> >> addin
Thanks for the review and happy new year..
-| {{{kbd(S)}}} | Sort reports by the column at point |
Looks like you deleted this line by accident.
I've restored this in the patch below.
I just tried your patch on an Org file with 2 warnings and tried
to press C-x ` repeatedly. Upon moving to
18 matches
Mail list logo
