* lisp/ob-tangle.el: (org-babel-tangle-collect-blocks): source blocks
without a language are not 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 part of a source block optiona
Ihor Radchenko writes:
> It is not just about \(...\).
Of course, and I agree that a more general mechanism is needed to solve
all precedence problems, be it in tables, or (better) in general. But,
as I said before, even if we had such a mechanism, it should not be
necessary to use it for \(...
Rudolf Adamkovič writes:
>> ... | \(first cell | mid | last\) |
>
> But how many Org tables exist in the world that have a row with an
> un-closed \( in one cell and an un-closed \) in a subsequent cell?
It is not just about \(...\). Consider other verbatim Org markup like
| $10 | foo | $\alpha
Ihor Radchenko writes:
> These edge cases come in pairs:
>
> printf '%s\n' '| \(first cell | mid | last\) |' | pandoc -f org -t latex
> \begin{longtable}[]{@{}l@{}}
> \toprule\noalign{}
> \endhead
> \bottomrule\noalign{}
> \endlastfoot
> \(first cell | mid | last\) \\
> \end{longtable}
But how m
I just discovered org-habit, but I don't fully understand how to
configure the appearance of habits in the Agenda view. Let's start
with my current setup (org 9.7.11 and Emacs 31.0.50 on Linux)
(setq org-habit-preceding-days 1)
(setq org-habit-following-days 1)
(setq org-habit-show-habits-only-for
"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 provided by the
> version of GNU Emacs (29.4) nor the "elpa-org" packag
On Tue Dec 31, 2024 at 7:15 PM CET, Ihor Radchenko wrote:
> >> And this discussion was about using \fC to represent "code" (also,
> >> "fixed width" and tables). We use \fC historically, and it is not very
> >> clear what could be a replacement that does not break Man export
> >> compared to previo
Attached is a patch that fixes adding an unnumbered section to the TOC with
test cases. You will need to add the Title you want to appear in the ToC in
:ALT_TITLE: I'm looking at a new property to copy the section title.
Something like
:ALT_TITLE_COPY: t
But I'm open to suggestions.
Happy New Year
Rudolf Adamkovič writes:
>> It is not just about \(...\).
>
> Of course, and I agree that a more general mechanism is needed to solve
> all precedence problems, be it in tables, or (better) in general. But,
> as I said before, even if we had such a mechanism, it should not be
> necessary to use
Rudolf Adamkovič writes:
>>> (image-type "...-59b9176e65c9.svg") => svg
>>
>> Why do you think that the output file is always an image? It may not
>> be. It can be anything.
>
> I do not think that. I specifically addressed the non-image case: the
> file would retain the `out' extension.
Reas
[Ingo: see bottom of message for a possible mandoc(1) bug in footnote 2]
Hi Ihor,
At 2024-12-22T15:41:57+, Ihor Radchenko wrote:
> "G. Branden Robinson" writes:
>
> >> Jeremy suggests that "C" may be an old alias for Courier, and if
> >> that's the case it should be changed to "\f[CR]". Wo
On Tue Dec 31, 2024 at 7:42 PM CET, onf wrote:
> Branden will likely provide you with a more detailed description, but
> in short, displays are text that is set off from the rest. Example from
> groff(7):
> [...]
> Checking the manpage's source shows that this is done precisely using
> the EX/EE ma
Valerio Siniscalco writes:
> This warning appears every time that the following commands are executed:
>
> - (org-anki-sync-all) from 'org-anki'
> (https://github.com/eyeinsky/org-anki)
> - (org-caldav-sync) from 'org-caldav'
> (https://github.com/dengste/org-caldav)
>
> The commands work pro
13 matches
Mail list logo
